| 0x0 | 操作成功完成。 |
The operation completed successfully. |
| 0x1 | 函数不正确。 |
Incorrect function. |
| 0x2 | 系统找不到指定的文件。 |
The system cannot find the file specified. |
| 0x3 | 系统找不到指定的路径。 |
The system cannot find the path specified. |
| 0x4 | 系统无法打开文件。 |
The system cannot open the file. |
| 0x5 | 拒绝访问。 |
Access is denied. |
| 0x6 | 句柄无效。 |
The handle is invalid. |
| 0x7 | 存储控制块被损坏。 |
The storage control blocks were destroyed. |
| 0x8 | 存储不足，无法处理此命令。 |
Not enough storage is available to process this command. |
| 0x9 | 存储控制块地址无效。 |
The storage control block address is invalid. |
| 0xA | 环境不正确。 |
The environment is incorrect. |
| 0xB | 试图加载格式不正确的程序。 |
An attempt was made to load a program with an incorrect format. |
| 0xC | 访问码无效。 |
The access code is invalid. |
| 0xD | 数据无效。 |
The data is invalid. |
| 0xE | 存储不足，无法完成此操作。 |
Not enough storage is available to complete this operation. |
| 0xF | 系统找不到指定的驱动器。 |
The system cannot find the drive specified. |
| 0x10 | 无法删除目录。 |
The directory cannot be removed. |
| 0x11 | 系统无法将文件移到不同的磁盘驱动器。 |
The system cannot move the file to a different disk drive. |
| 0x12 | 没有更多文件。 |
There are no more files. |
| 0x13 | 介质受写入保护。 |
The media is write protected. |
| 0x14 | 系统找不到指定的设备。 |
The system cannot find the device specified. |
| 0x15 | 设备未就绪。 |
The device is not ready. |
| 0x16 | 设备不识别此命令。 |
The device does not recognize the command. |
| 0x17 | 数据错误(循环冗余检查)。 |
Data error (cyclic redundancy check). |
| 0x18 | 程序发出命令，但命令长度不正确。 |
The program issued a command but the command length is incorrect. |
| 0x19 | 驱动器找不到磁盘上特定区域或磁道。 |
The drive cannot locate a specific area or track on the disk. |
| 0x1A | 无法访问指定的磁盘或软盘。 |
The specified disk or diskette cannot be accessed. |
| 0x1B | 驱动器找不到请求的扇区。 |
The drive cannot find the sector requested. |
| 0x1C | 打印机缺纸。 |
The printer is out of paper. |
| 0x1D | 系统无法写入指定的设备。 |
The system cannot write to the specified device. |
| 0x1E | 系统无法从指定的设备上读取。 |
The system cannot read from the specified device. |
| 0x1F | 连到系统上的设备没有发挥作用。 |
A device attached to the system is not functioning. |
| 0x20 | 另一个程序正在使用此文件，进程无法访问。 |
The process cannot access the file because it is being used by another process. |
| 0x21 | 另一个程序已锁定文件的一部分，进程无法访问。 |
The process cannot access the file because another process has locked a portion of the file. |
| 0x22 | 驱动器中的软盘不对。将 %2 插入(卷序列号: %3)驱动器 %1。 |
The wrong diskette is in the drive.Insert %2 (Volume Serial Number: %3) into drive %1. |
| 0x24 | 用来共享的打开文件过多。 |
Too many files opened for sharing. |
| 0x26 | 已到文件结尾。 |
Reached the end of the file. |
| 0x27 | 磁盘已满。 |
The disk is full. |
| 0x32 | 不支持该请求。 |
The request is not supported. |
| 0x33 | Windows 无法找到网络路径。请确认网络路径正确并且目标计算机不忙或已关闭。如果 Windows 仍然无法找到网络路径，请与网络管理员联系。 |
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. |
| 0x34 | 由于网络上有重名，没有连接。如果加入域，请转到“控制面板”中的“系统”更改计算机名，然后重试。如果加入工作组，请选择其他工作组名。 |
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. |
| 0x35 | 找不到网络路径。 |
The network path was not found. |
| 0x36 | 网络很忙。 |
The network is busy. |
| 0x37 | 指定的网络资源或设备不再可用。 |
The specified network resource or device is no longer available. |
| 0x38 | 已达到网络 BIOS 命令限制。 |
The network BIOS command limit has been reached. |
| 0x39 | 网络适配器硬件出错。 |
A network adapter hardware error occurred. |
| 0x3A | 指定的服务器无法运行请求的操作。 |
The specified server cannot perform the requested operation. |
| 0x3B | 出现了意外的网络错误。 |
An unexpected network error occurred. |
| 0x3C | 远程适配器不兼容。 |
The remote adapter is not compatible. |
| 0x3D | 打印机队列已满。 |
The printer queue is full. |
| 0x3E | 服务器上没有储存等待打印的文件的空间。 |
Space to store the file waiting to be printed is not available on the server. |
| 0x3F | 已删除等候打印的文件。 |
Your file waiting to be printed was deleted. |
| 0x40 | 指定的网络名不再可用。 |
The specified network name is no longer available. |
| 0x41 | 拒绝网络访问。 |
Network access is denied. |
| 0x42 | 网络资源类型不对。 |
The network resource type is not correct. |
| 0x43 | 找不到网络名。 |
The network name cannot be found. |
| 0x44 | 超出本地计算机网络适配器卡的名称限制。 |
The name limit for the local computer network adapter card was exceeded. |
| 0x45 | 超出了网络 BIOS 会话限制。 |
The network BIOS session limit was exceeded. |
| 0x46 | 远程服务器已暂停，或正在启动过程中。 |
The remote server has been paused or is in the process of being started. |
| 0x47 | 已达到计算机的连接数最大值，无法再同此远程计算机连接。 |
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. |
| 0x48 | 已暂停指定的打印机或磁盘设备。 |
The specified printer or disk device has been paused. |
| 0x50 | 文件存在。 |
The file exists. |
| 0x52 | 无法创建目录或文件。 |
The directory or file cannot be created. |
| 0x53 | INT 24 上的故障。 |
Fail on INT 24. |
| 0x54 | 无法取得处理此请求的存储。 |
Storage to process this request is not available. |
| 0x55 | 本地设备名已在使用中。 |
The local device name is already in use. |
| 0x56 | 指定的网络密码不正确。 |
The specified network password is not correct. |
| 0x57 | 参数错误。 |
The parameter is incorrect. |
| 0x58 | 网络上发生写入错误。 |
A write fault occurred on the network. |
| 0x59 | 系统无法在此时启动另一个进程。 |
The system cannot start another process at this time. |
| 0x64 | 无法创建另一个系统信号灯。 |
Cannot create another system semaphore. |
| 0x65 | 另一个进程拥有独占的信号灯。 |
The exclusive semaphore is owned by another process. |
| 0x66 | 已设置信号灯，无法关闭。 |
The semaphore is set and cannot be closed. |
| 0x67 | 无法再设置信号灯。 |
The semaphore cannot be set again. |
| 0x68 | 无法在中断时请求独占的信号灯。 |
Cannot request exclusive semaphores at interrupt time. |
| 0x69 | 此信号灯的前一个所有权已结束。 |
The previous ownership of this semaphore has ended. |
| 0x6A | 在驱动器 %1 上插入软盘。 |
Insert the diskette for drive %1. |
| 0x6B | 由于没有插入另一个软盘，程序停止。 |
The program stopped because an alternate diskette was not inserted. |
| 0x6C | 磁盘在使用中，或被另一个进程锁定。 |
The disk is in use or locked by another process. |
| 0x6D | 管道已结束。 |
The pipe has been ended. |
| 0x6E | 系统无法打开指定的设备或文件。 |
The system cannot open the device or file specified. |
| 0x6F | 文件名太长。 |
The file name is too long. |
| 0x70 | 磁盘空间不足。 |
There is not enough space on the disk. |
| 0x71 | 没有更多的内部文件标识符。 |
No more internal file identifiers available. |
| 0x72 | 目标内部文件标识符不正确。 |
The target internal file identifier is incorrect. |
| 0x75 | 应用程序发出的 IOCTL 调用不正确。 |
The IOCTL call made by the application program is not correct. |
| 0x76 | 验证写入的切换参数值不正确。 |
The verify-on-write switch parameter value is not correct. |
| 0x77 | 系统不支持请求的命令。 |
The system does not support the command requested. |
| 0x78 | 这个系统不支持该功能。 |
This function is not supported on this system. |
| 0x79 | 信号灯超时时间已到 |
The semaphore timeout period has expired. |
| 0x7A | 传递给系统调用的数据区域太小。 |
The data area passed to a system call is too small. |
| 0x7B | 文件名、目录名或卷标语法不正确。 |
The filename, directory name, or volume label syntax is incorrect. |
| 0x7C | 系统调用级别不正确。 |
The system call level is not correct. |
| 0x7D | 磁盘没有卷标。 |
The disk has no volume label. |
| 0x7E | 找不到指定的模块。 |
The specified module could not be found. |
| 0x7F | 找不到指定的程序。 |
The specified procedure could not be found. |
| 0x80 | 没有等候的子进程。 |
There are no child processes to wait for. |
| 0x81 | %1 应用程序无法在 Win32 模式中运行。 |
The %1 application cannot be run in Win32 mode. |
| 0x82 | 试图使用操作(而非原始磁盘 I/O)的已打开磁盘分区的文件句柄。 |
Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O. |
| 0x83 | 试图将文件指针移到文件开头之前。 |
An attempt was made to move the file pointer before the beginning of the file. |
| 0x84 | 无法在指定的设备或文件上设置文件指针。 |
The file pointer cannot be set on the specified device or file. |
| 0x85 | 包含先前加入驱动器的驱动器无法使用 JOIN 或 SUBST 命令。 |
A JOIN or SUBST command cannot be used for a drive that contains previously joined drives. |
| 0x86 | 试图在已被合并的驱动器上使用 JOIN 或 SUBST 命令。 |
An attempt was made to use a JOIN or SUBST command on a drive that has already been joined. |
| 0x88 | 系统试图解除未合并驱动器的 JOIN。 |
The system tried to delete the JOIN of a drive that is not joined. |
| 0x89 | 系统试图解除未替代驱动器的 SUBST。 |
The system tried to delete the substitution of a drive that is not substituted. |
| 0x8A | 系统试图将驱动器合并到合并驱动器上的目录。 |
The system tried to join a drive to a directory on a joined drive. |
| 0x8B | 系统试图将驱动器替代为替代驱动器上的目录。 |
The system tried to substitute a drive to a directory on a substituted drive. |
| 0x8C | 系统试图将驱动器合并到替代驱动器上的目录。 |
The system tried to join a drive to a directory on a substituted drive. |
| 0x8D | 系统试图替代驱动器为合并驱动器上的目录。 |
The system tried to SUBST a drive to a directory on a joined drive. |
| 0x8E | 系统无法在此时运行 JOIN 或 SUBST。 |
The system cannot perform a JOIN or SUBST at this time. |
| 0x8F | 系统无法将驱动器合并到或替代为相同驱动器上的目录。 |
The system cannot join or substitute a drive to or for a directory on the same drive. |
| 0x90 | 目录不是根目录下的子目录。 |
The directory is not a subdirectory of the root directory. |
| 0x91 | 目录不是空的。 |
The directory is not empty. |
| 0x92 | 指定的路径已在替代中使用。 |
The path specified is being used in a substitute. |
| 0x93 | 资源不足，无法处理此命令。 |
Not enough resources are available to process this command. |
| 0x94 | 指定的路径无法在此时使用。 |
The path specified cannot be used at this time. |
| 0x95 | 企图将驱动器合并或替代为驱动器上目录是上一个替代的目标的驱动器。 |
An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute. |
| 0x96 | 系统跟踪信息未在 CONFIG.SYS 文件中指定，或不允许跟踪。 |
System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed. |
| 0x97 | 为 DosMuxSemWait 指定的信号灯事件数量不正确。 |
The number of specified semaphore events for DosMuxSemWait is not correct. |
| 0x98 | DosMuxSemWait 没有执行；已设置过多的信号灯。 |
DosMuxSemWait did not execute; too many semaphores are already set. |
| 0x99 | DosMuxSemWait 列表不正确。 |
The DosMuxSemWait list is not correct. |
| 0x9A | 输入的卷标超过目标文件系统的字符长度限制。 |
The volume label you entered exceeds the label character limit of the target file system. |
| 0x9B | 无法创建另一个线程。 |
Cannot create another thread. |
| 0x9C | 接收人进程拒绝此信号。 |
The recipient process has refused the signal. |
| 0x9D | 段已被放弃且无法锁定。 |
The segment is already discarded and cannot be locked. |
| 0x9E | 段已解除锁定。 |
The segment is already unlocked. |
| 0x9F | 线程 ID 的地址不正确。 |
The address for the thread ID is not correct. |
| 0xA0 | 至少有一个参数不正确。 |
One or more arguments are not correct. |
| 0xA1 | 指定的路径无效。 |
The specified path is invalid. |
| 0xA2 | 信号已暂停。 |
A signal is already pending. |
| 0xA4 | 无法在系统中创建更多的线程。 |
No more threads can be created in the system. |
| 0xA7 | 无法锁定文件区域。 |
Unable to lock a region of a file. |
| 0xAA | 请求的资源在使用中。 |
The requested resource is in use. |
| 0xAB | 设备的命令支持检测正在进行中。 |
Device's command support detection is in progress. |
| 0xAD | 对于提供取消区域进行锁定的请求已完成。 |
A lock request was not outstanding for the supplied cancel region. |
| 0xAE | 文件系统不支持锁定类型的最小单元更改。 |
The file system does not support atomic changes to the lock type. |
| 0xB4 | 系统检测出错误的段号。 |
The system detected a segment number that was not correct. |
| 0xB6 | 操作系统无法运行 %1。 |
The operating system cannot run %1. |
| 0xB7 | 当文件已存在时，无法创建该文件。 |
Cannot create a file when that file already exists. |
| 0xBA | 传递的标志不正确。 |
The flag passed is not correct. |
| 0xBB | 找不到指定的系统信号灯名称。 |
The specified system semaphore name was not found. |
| 0xBF | 无法在 Win32 模式下运行 %1。 |
Cannot run %1 in Win32 mode. |
| 0xC1 | %1 不是有效的 Win32 应用程序。 |
%1 is not a valid Win32 application. |
| 0xC4 | 操作系统无法运行此应用程序。 |
The operating system cannot run this application program. |
| 0xC5 | 操作系统当前的配置不能运行此应用程序。 |
The operating system is not presently configured to run this application. |
| 0xC8 | 代码段不可大于或等于 64K。 |
The code segment cannot be greater than or equal to 64K. |
| 0xCB | 操作系统找不到已输入的环境选项。 |
The system could not find the environment option that was entered. |
| 0xCD | 命令子树中的进程没有信号处理程序。 |
No process in the command subtree has a signal handler. |
| 0xCE | 文件名或扩展名太长。 |
The filename or extension is too long. |
| 0xCF | 第 2 环堆栈已被占用。 |
The ring 2 stack is in use. |
| 0xD0 | 没有正确输入文件名通配符 * 或 ?，或指定过多的文件名通配符。 |
The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified. |
| 0xD1 | 正在发送的信号不正确。 |
The signal being posted is not correct. |
| 0xD2 | 无法设置信号处理程序。 |
The signal handler cannot be set. |
| 0xD4 | 段已锁定且无法重新分配。 |
The segment is locked and cannot be reallocated. |
| 0xD6 | 连到该程序或动态链接模块的动态链接模块太多。 |
Too many dynamic-link modules are attached to this program or dynamic-link module. |
| 0xD7 | 无法嵌套调用 LoadModule。 |
Cannot nest calls to LoadModule. |
| 0xD8 | 该版本的 %1 与你运行的 Windows 版本不兼容。请查看计算机的系统信息，然后联系软件发布者。 |
This 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. |
| 0xD9 | 图像文件 %1 已签名，无法修改。 |
The image file %1 is signed, unable to modify. |
| 0xDA | 图像文件 %1 已强签名，无法修改。 |
The image file %1 is strong signed, unable to modify. |
| 0xDC | 签出或锁定此文件，以便另一用户编辑。 |
This file is checked out or locked for editing by another user. |
| 0xDD | 保存更改之前必须签出文件。 |
The file must be checked out before saving changes. |
| 0xDE | 正在保存或检索的文件类型已阻止。 |
The file type being saved or retrieved has been blocked. |
| 0xDF | 文件大小超出允许的限制，无法保存。 |
The file size exceeds the limit allowed and cannot be saved. |
| 0xE0 | 拒绝访问。在此位置打开文件之前，必须先将网站添加到受信任的站点列表中，浏览到网站，并选择自动登录的选项。 |
Access 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. |
| 0xE1 | 无法成功完成操作，因为文件包含病毒或潜在的垃圾软件。 |
Operation did not complete successfully because the file contains a virus or potentially unwanted software. |
| 0xE2 | 此文件包含病毒或潜在的垃圾软件，无法打开。由于病毒或潜在的垃圾软件的本质，此文件已从该位置删除。 |
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. |
| 0xE5 | 管道是本地的。 |
The pipe is local. |
| 0xE6 | 管道状态无效。 |
The pipe state is invalid. |
| 0xE7 | 所有的管道范例都在使用中。 |
All pipe instances are busy. |
| 0xE8 | 管道正在被关闭。 |
The pipe is being closed. |
| 0xE9 | 管道的另一端上无任何进程。 |
No process is on the other end of the pipe. |
| 0xEA | 有更多数据可用。 |
More data is available. |
| 0xEB | 所请求的操作没有响应。已执行错误样式清除。 |
The action requested resulted in no work being done. Error-style clean-up has been performed. |
| 0xF0 | 已取消会话。 |
The session was canceled. |
| 0xFE | 指定的扩展属性名无效。 |
The specified extended attribute name was invalid. |
| 0xFF | 扩展属性不一致。 |
The extended attributes are inconsistent. |
| 0x102 | 等待的操作过时。 |
The wait operation timed out. |
| 0x103 | 没有可用的数据了。 |
No more data is available. |
| 0x10A | 无法使用复制功能。 |
The copy functions cannot be used. |
| 0x10B | 目录名称无效。 |
The directory name is invalid. |
| 0x113 | 扩展属性在缓冲区中不适用。 |
The extended attributes did not fit in the buffer. |
| 0x114 | 装在文件系统上的扩展属性文件已损坏。 |
The extended attribute file on the mounted file system is corrupt. |
| 0x115 | 扩展属性表格文件已满。 |
The extended attribute table file is full. |
| 0x116 | 指定的扩展属性句柄无效。 |
The specified extended attribute handle is invalid. |
| 0x11A | 装入的文件系统不支持扩展属性。 |
The mounted file system does not support extended attributes. |
| 0x120 | 企图释放并非呼叫方所拥有的多用户终端运行程序。 |
Attempt to release mutex not owned by caller. |
| 0x12A | 发向信号灯的请求过多。 |
Too many posts were made to a semaphore. |
| 0x12B | 仅完成部分的 ReadProcessMemory 或 WriteProcessMemory 请求。 |
Only part of a ReadProcessMemory or WriteProcessMemory request was completed. |
| 0x12C | 操作锁定请求被拒绝。 |
The oplock request is denied. |
| 0x12D | 系统接收了一个无效的操作锁定确认。 |
An invalid oplock acknowledgment was received by the system. |
| 0x12E | 此卷太碎，不能完成这个操作。 |
The volume is too fragmented to complete this operation. |
| 0x12F | 不能打开文件，因为它正在被删除。 |
The file cannot be opened because it is in the process of being deleted. |
| 0x130 | 由于全局注册表设置，在此卷上不能更改短名称设置。 |
Short name settings may not be changed on this volume due to the global registry setting. |
| 0x131 | 未在此卷上启用短名称。 |
Short names are not enabled on this volume. |
| 0x132 | 给定卷的安全流处于不一致状态。请在此卷上运行 CHKDSK。 |
The security stream for the given volume is in an inconsistent state.Please run CHKDSK on the volume. |
| 0x133 | 由于字节范围无效，无法处理请求的文件锁定操作。 |
A requested file lock operation cannot be processed due to an invalid byte range. |
| 0x134 | 支持此映像类型所需的子系统不存在。 |
The subsystem needed to support the image type is not present. |
| 0x135 | 指定的文件已经具有与之关联的通知 GUID。 |
The specified file already has a notification GUID associated with it. |
| 0x136 | 检测到无效的异常处理程序例程。 |
An invalid exception handler routine has been detected. |
| 0x137 | 已经为该令牌指定了重复权限。 |
Duplicate privileges were specified for the token. |
| 0x138 | 无法处理指定操作的范围。 |
No ranges for the specified operation were able to be processed. |
| 0x139 | 不允许对文件系统内部文件进行操作。 |
Operation is not allowed on a file system internal file. |
| 0x13A | 此磁盘的物理资源已用尽。 |
The physical resources of this disk have been exhausted. |
| 0x13B | 表示数据的令牌无效。 |
The token representing the data is invalid. |
| 0x13C | 设备不支持命令功能。 |
The device does not support the command feature. |
| 0x13D | 系统无法在消息文件中为 %2 找到消息号为 0x%1 的消息文本。 |
The system cannot find message text for message number 0x%1 in the message file for %2. |
| 0x13E | 找不到指定范围。 |
The scope specified was not found. |
| 0x13F | 目标计算机上未定义指定的中心访问策略。 |
The Central Access Policy specified is not defined on the target machine. |
| 0x140 | 从 Active Directory 获取的中心访问策略无效。 |
The Central Access Policy obtained from Active Directory is invalid. |
| 0x141 | 无法连接至设备。 |
The device is unreachable. |
| 0x142 | 目标设备资源不足，无法完成操作。 |
The target device has insufficient resources to complete the operation. |
| 0x143 | 发生了数据完整性校验和错误。文件流中的数据已损坏。 |
A data integrity checksum error occurred. Data in the file stream is corrupt. |
| 0x144 | 已尝试在同一操作中修改 KERNEL 和正常扩展属性 (EA)。 |
An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation. |
| 0x146 | 设备不支持文件级 TRIM。 |
Device does not support file-level TRIM. |
| 0x147 | 该命令指定了与设备粒度/对齐不相符的数据偏移。 |
The command specified a data offset that does not align to the device's granularity/alignment. |
| 0x148 | 该命令指定了参数列表中的无效字段。 |
The command specified an invalid field in its parameter list. |
| 0x149 | 当前正在对设备进行操作。 |
An operation is currently in progress with the device. |
| 0x14A | 已尝试通过无效的路径将该命令发送至目标设备。 |
An attempt was made to send down the command via an invalid path to the target device. |
| 0x14B | 该命令指定的描述符数目超出了设备支持的最大值。 |
The command specified a number of descriptors that exceeded the maximum supported by the device. |
| 0x14C | 指定文件上已禁用推移操作。 |
Scrub is disabled on the specified file. |
| 0x14D | 存储设备未提供冗余。 |
The storage device does not provide redundancy. |
| 0x14E | 不支持对常驻文件执行操作。 |
An operation is not supported on a resident file. |
| 0x14F | 不支持对压缩的文件执行操作。 |
An operation is not supported on a compressed file. |
| 0x150 | 不支持对目录执行操作。 |
An operation is not supported on a directory. |
| 0x151 | 无法读取请求数据的指定副本。 |
The specified copy of the requested data could not be read. |
| 0x152 | 无法将指定的数据写入到任何副本中。 |
The specified data could not be written to any of the copies. |
| 0x153 | 此设备上的一个或多个数据副本可能不同步。在完成数据完整性扫描后，才能执行写入操作。 |
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. |
| 0x154 | 提供的内核信息版本无效。 |
The supplied kernel information version is invalid. |
| 0x155 | 提供的 PEP 信息版本无效。 |
The supplied PEP information version is invalid. |
| 0x156 | 任何提供程序都没有从外部支持此对象。 |
This object is not externally backed by any provider. |
| 0x157 | 无法识别该外部支持提供程序。 |
The external backing provider is not recognized. |
| 0x158 | 压缩此对象不会节省空间。 |
Compressing this object would not save space. |
| 0x159 | 由于存储拓扑 ID 不匹配，请求失败。 |
The request failed due to a storage topology ID mismatch. |
| 0x15A | 操作被家长控制阻止。 |
The operation was blocked by parental controls. |
| 0x15B | 正在引用的文件系统块已达到最大引用计数，无法进一步引用。 |
A file system block being referenced has already reached the maximum reference count and can't be referenced any further. |
| 0x15C | 请求的操作失败，因为文件流已标记为不允许写入。 |
The requested operation failed because the file stream is marked to disallow writes. |
| 0x15D | 请求的操作失败，返回体系结构特定的故障代码。 |
The requested operation failed with an architecture-specific failure code. |
| 0x15E | 由于需要重新启动系统，因此未执行任何操作。 |
No action was taken as a system reboot is required. |
| 0x15F | 关机操作失败。 |
The shutdown operation failed. |
| 0x160 | 重新启动操作失败。 |
The restart operation failed. |
| 0x161 | 已达到会话的最大数目。 |
The maximum number of sessions has been reached. |
| 0x162 | Windows 信息保护策略不允许访问此网络资源。 |
Windows Information Protection policy does not allow access to this network resource. |
| 0x163 | 设备提示名称缓冲区太小，无法接收剩余名称。 |
The device hint name buffer is too small to receive the remaining name. |
| 0x164 | 请求的操作已被 Windows 信息保护策略阻止。有关详细信息，请联系系统管理员。 |
The requested operation was blocked by Windows Information Protection policy. For more information, contact your system administrator. |
| 0x165 | 无法执行请求的操作，因为设备的硬件或软件配置不符合“Windows 信息保护 - 加锁保护”策略。请确认是否已创建用户 PIN。有关详细信息，请联系系统管理员。 |
The requested operation cannot be performed because hardware or software configuration of the device does not comply with Windows Information Protection under Lock policy. Please, verify that user PIN has been created. For more information, contact your system administrator. |
| 0x166 | 云文件提供程序未知。 |
The Cloud File provider is unknown. |
| 0x167 | 该设备处于维护模式。 |
The device is in maintenance mode. |
| 0x168 | DAX 卷不支持此操作。 |
This operation is not supported on a DAX volume. |
| 0x169 | 此卷具有活动 DAX 映射。 |
The volume has active DAX mappings. |
| 0x16A | 云文件提供程序未运行。 |
The Cloud File provider is not running. |
| 0x16B | 云文件元数据已损坏且不可读取。 |
The Cloud File metadata is corrupt and unreadable. |
| 0x16C | 由于云文件元数据太大，无法完成该操作。 |
The operation could not be completed because the Cloud File metadata is too large. |
| 0x16D | 由于云文件属性 Blob 太大，无法完成该操作。 |
The operation could not be completed because the Cloud File property blob is too large. |
| 0x16E | 云文件属性 Blob 可能已损坏。磁盘上的校验和与计算得出的校验和不匹配。 |
The Cloud File property blob is possibly corrupt. The on-disk checksum does not match the computed checksum. |
| 0x16F | 已阻止创建进程。 |
The process creation has been blocked. |
| 0x170 | 此存储设备已丢失数据或持久性。 |
The storage device has lost data or persistence. |
| 0x171 | 支持文件系统虚拟化的提供程序暂时不可用。 |
The provider that supports file system virtualization is temporarily unavailable. |
| 0x172 | 文件系统虚拟化的元数据已损坏且无法读取。 |
The metadata for file system virtualization is corrupt and unreadable. |
| 0x173 | 支持文件系统虚拟化的提供程序太忙，无法完成此操作。 |
The provider that supports file system virtualization is too busy to complete this operation. |
| 0x174 | 支持文件系统虚拟化的提供程序未知。 |
The provider that supports file system virtualization is unknown. |
| 0x175 | GDI 句柄可能已被应用程序泄漏。 |
GDI handles were potentially leaked by the application. |
| 0x176 | 由于超出了云文件属性 Blob 的最大数目，无法完成该操作。 |
The operation could not be completed because the maximum number of Cloud File property blobs would be exceeded. |
| 0x177 | 因为不支持云文件元数据版本，无法完成该操作。 |
The operation could not be completed because the Cloud File metadata version is not supported. |
| 0x178 | 因为该文件不是云文件，此操作无法完成。 |
The operation could not be completed because the file is not a Cloud File. |
| 0x179 | 因为云文件未同步，此操作不能完成。 |
The operation could not be completed because the Cloud File is not in sync. |
| 0x190 | 该线程已处于后台处理模式。 |
The thread is already in background processing mode. |
| 0x191 | 该线程不处于后台处理模式。 |
The thread is not in background processing mode. |
| 0x192 | 该进程已处于后台处理模式。 |
The process is already in background processing mode. |
| 0x193 | 该进程不处于后台处理模式。 |
The process is not in background processing mode. |
| 0x1C2 | 既不在设备上启用开发人员解锁模式，也不启用端加载模式。 |
Neither developer unlocked mode nor side loading mode is enabled on the device. |
| 0x1C3 | 在升级或重新预配过程中无法更改应用程序类型。 |
Can not change application type during upgrade or re-provision. |
| 0x1C4 | 未预配应用程序。 |
The application has not been provisioned. |
| 0x1C5 | 无法为此应用程序授权请求的功能。 |
The requested capability can not be authorized for this application. |
| 0x1C6 | 设备上没有功能授权策略。 |
There is no capability authorization policy on the device. |
| 0x1C7 | 功能授权数据库已损坏。 |
The capability authorization database has been corrupted. |
| 0x1E0 | 等待此设备完成 PnP 查询删除请求时，由于设备堆栈中可能存在的挂起，导致操作超时。系统可能需要重新启动才能完成请求。 |
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in its device stack. The system may need to be rebooted to complete the request. |
| 0x1E1 | 等待此设备完成 PnP 查询删除请求时，由于相关设备的设备堆栈中可能存在的挂起，导致操作超时。系统可能需要重新启动才能完成请求。 |
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of a related device. The system may need to be rebooted to complete the operation. |
| 0x1E2 | 等待此设备完成 PnP 查询删除请求时，由于不相关设备的设备堆栈中可能存在的挂起，导致操作超时。系统可能需要重新启动才能完成请求。 |
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of an unrelated device. The system may need to be rebooted to complete the operation. |
| 0x1E3 | 设备硬件出现致命错误，导致请求失败。 |
The request failed due to a fatal device hardware error. |
| 0x1E7 | 试图访问无效的地址。 |
Attempt to access invalid address. |
| 0x1F4 | 无法加载用户配置文件。 |
User profile cannot be loaded. |
| 0x216 | 算术结果超过 32 位。 |
Arithmetic result exceeded 32 bits. |
| 0x217 | 管道的另一端有一进程。 |
There is a process on other end of the pipe. |
| 0x218 | 等候打开管道另一端的进程。 |
Waiting for a process to open the other end of the pipe. |
| 0x219 | 应用程序验证程序在当前进程中发现错误。 |
Application verifier has found an error in the current process. |
| 0x21A | ABIOS 子系统中出现错误。 |
An error occurred in the ABIOS subsystem. |
| 0x21B | WX86 子系统中出现警告。 |
A warning occurred in the WX86 subsystem. |
| 0x21C | WX86 子系统中出现错误。 |
An error occurred in the WX86 subsystem. |
| 0x21D | 试图取消或设置与 APC 相关的计时器，主题线程不是原始设置的与 APC 例行程序相关的计时器的线程。 |
An 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. |
| 0x21E | 解除异常代码。 |
Unwind exception code. |
| 0x21F | 在解除操作期间遇到一个无效或不正确配置的堆栈。 |
An invalid or unaligned stack was encountered during an unwind operation. |
| 0x220 | 在解除操作期间遇到一个无效的解除目标。 |
An invalid unwind target was encountered during an unwind operation. |
| 0x221 | 指定给 NtCreatePort 的无效对象属性或指定给 NtConnectPort 的无效端口属性。 |
Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort |
| 0x222 | 发送给 NtRequestPort 或 NtRequestWaitReplyPort 的消息长度大于端口允许的最大长度。 |
Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port. |
| 0x223 | 试图降低配额限制，使低于当前的使用率。 |
An attempt was made to lower a quota limit below the current usage. |
| 0x224 | 试图连接到已附加到其他设备的设备。 |
An attempt was made to attach to a device that was already attached to another device. |
| 0x225 | 试图在未分配的地址上执行指令，且主机系统不支持未分配的命令引用。 |
An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references. |
| 0x226 | 未启动配置文件。 |
Profiling not started. |
| 0x227 | 未停止配置文件。 |
Profiling not stopped. |
| 0x228 | 传送的 ACL 不包含最低要求的信息。 |
The passed ACL did not contain the minimum required information. |
| 0x229 | 使用中的配置文件对象的数量已到达最大值且无法再启动任何对象。 |
The number of active profiling objects is at the maximum and no more may be started. |
| 0x22A | 用于指出如果不阻止以等待 I/O，操作将无法继续进行。 |
Used to indicate that an operation cannot continue without blocking for I/O. |
| 0x22B | 表示一线程试图依默认值终止其本身(以 NULL 调用 NtTerminateThread)且该线程为当前过程中的最后一个线程。 |
Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process. |
| 0x22C | 如返回一个未在标准 FsRtl 筛选程序中定义的 MM 错误，该错误将会转换为已在筛选程序中定义的下述错误之一。在这种情况下，信息会丢失；但筛选器能正确地处理该异常情形。 |
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. |
| 0x22F | 在释放操作期间遇到格式不正确的功能表。 |
A malformed function table was encountered during an unwind operation. |
| 0x230 | 表示试图保护文件系统上的文件或目录且无法将安全描述符中的某一 SID 转换为可在该文件系统中保存的 GUID。这会导致保护失败，进而使文件创建失败。 |
Indicates 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. |
| 0x231 | 试图通过设置 LDT 的大小以增长它，或者其大小不是选择器的一个偶数。 |
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. |
| 0x233 | LDT 信息的启动值不是选择器大小的整数倍。 |
Indicates that the starting value for the LDT information was not an integral multiple of the selector size. |
| 0x234 | 试图设置 Ldt 描述符时用户提供了无效的描述符。 |
Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors. |
| 0x235 | 表示执行请求操作的进程中有过多的线程。例如，只可在进程没有或仅有一个线程时分配主令牌。 |
Indicates 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. |
| 0x236 | 试图在特定的进程中运行线程，但所指定的线程不在指定的进程中。 |
An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified. |
| 0x237 | 超过页面文件配额。 |
Page file quota was exceeded. |
| 0x238 | 因在域中运行的其他 Netlogon 服务与指定的角色冲突而无法启动 Netlogon 服务。 |
The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role. |
| 0x239 | Windows Server 上的 SAM 数据库无法与域控制器上的备份同步。两者必须完全同步。 |
The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required. |
| 0x23A | NtCreateFile API 失败。此项错误无法返回至应用程序，它是 Windows LAN Manager 重定向程序在内部错误映射例行程序中所使用的路由选择。 |
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. |
| 0x23B | {特权失败}无法更改过程的 I/O 权限。 |
{Privilege Failed}The I/O permissions for the process could not be changed. |
| 0x23C | {使用 CTRL+C 退出应用程序}使用 CTRL+C 终止应用程序。 |
{Application Exit by CTRL+C}The application terminated as a result of a CTRL+C. |
| 0x23D | {无法取得系统文件}必须的系统文件 %hs 损坏或丢失。 |
{Missing System File}The required system file %hs is bad or missing. |
| 0x23E | {应用程序错误}应用程序发生异常 %s (0x%08lx)，位置为 0x%08lx。 |
{Application Error}The exception %s (0x%08lx) occurred in the application at location 0x%08lx. |
| 0x23F | {应用程序错误}应用程序无法正常启动(0x%lx)。请单击“确定”关闭应用程序。 |
{Application Error}The application was unable to start correctly (0x%lx). Click OK to close the application. |
| 0x240 | {无法创建页面文件}创建分页文件 %hs 失败(%lx)。而请求的文件大小为 %ld。 |
{Unable to Create Paging File}The creation of the paging file %hs failed (%lx). The requested size was %ld. |
| 0x241 | Windows 无法验证此文件的数字签名。某软件或硬件最近有所更改，可能安装了签名错误或损毁的文件，或者安装的文件可能是来路不明的恶意软件。 |
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. |
| 0x242 | {未指定页面文件}未在系统配置中指定分页文件。 |
{No Paging File Specified}No paging file was specified in the system configuration. |
| 0x243 | {异常}实模式应用程序发出浮点运算指令而浮点运算硬件不存在。 |
{EXCEPTION}A real-mode application issued a floating-point instruction and floating-point hardware is not present. |
| 0x244 | 使用线程的特定客户端/服务器事件对对象运行事件对同步操作，但无任何事件对对象与该线程关联。 |
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. |
| 0x245 | Windows Server 的配置不正确。 |
A Windows Server has an incorrect configuration. |
| 0x246 | 出现无效字符。多字节字符集必须包含一前导字节且无结尾字节。Unicode 字符集则包含字符 0xFFFF 及 0xFFFE。 |
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. |
| 0x247 | 此 Unicode 字符没有在系统安装的 Unicode 字符集中定义。 |
The Unicode character is not defined in the Unicode character set installed on the system. |
| 0x248 | 不能在软盘上创建页面文件。 |
The paging file cannot be created on a floppy diskette. |
| 0x249 | 系统 BIOS 无法将系统中断连接到设备或该设备所连接的总线上。 |
The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected. |
| 0x24A | 该操作只能在主域控制器执行。 |
This operation is only allowed for the Primary Domain Controller of the domain. |
| 0x24B | 试图获得一个突变体，以致超过了其最大计数。 |
An attempt was made to acquire a mutant such that its maximum count would have been exceeded. |
| 0x24C | 磁盘卷已经因为一个必须要但尚未加载的文件系统驱动程序而被访问。 |
A volume has been accessed for which a file system driver is required that has not yet been loaded. |
| 0x24D | {注册表文件失败}注册表无法加载配置单元(文件):%hs或它的日志或替代数据。可能已经损坏、不存在或是无法写入。 |
{Registry File Failure}The registry cannot load the hive (file):%hsor its log or alternate.It is corrupt, absent, or not writable. |
| 0x24E | {DebugActiveProcess 中的意外失败}处理一个 DebugActiveProcess API 请求时发生意外失败。可以选择“确定”终止过程，或“取消”忽略错误。 |
{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. |
| 0x24F | {致命系统错误}%hs 系统进程在 0x%08x (0x%08x 0x%08x)状态不可预期地终止。系统已关闭。 |
{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. |
| 0x250 | {无法接受数据}TDI 客户端无法在指示的时间内处理接收的数据。 |
{Data Not Accepted}The TDI client could not handle the data received during an indication. |
| 0x251 | NTVDM 遇到一个硬错误。 |
NTVDM encountered a hard error. |
| 0x252 | {取消超时值}驱动程序 %hs 无法在指定的时间内完成一个已取消的 I/O 请求。 |
{Cancel Timeout}The driver %hs failed to complete a cancelled I/O request in the allotted time. |
| 0x253 | {应答消息不匹配}试图应答 LPC 消息，但消息中客户端 ID 指定的线程没有在消息上等待。 |
{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. |
| 0x254 | {延缓写入失败}Windows 无法为 %hs 文件保存所有数据。数据已经丢失。这个错误可能是由于你的计算机硬件或网络连接的失败而造成的。请尝试把这份文件保存到别处。 |
{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. |
| 0x255 | 发送给在客户端/服务器共享内存窗口中的服务器参数无效。共享内存窗口中放入过多的数据。 |
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. |
| 0x256 | 此流不是小流。 |
The stream is not a tiny stream. |
| 0x257 | 本请求必须由堆栈溢出代码处理。 |
The request must be handled by the stack overflow code. |
| 0x258 | 内部 OFS 状态代码表明分配操作的处理方式。其操作方式为在删除所包含的 onode 之后重试或将区域流转换为一个大的流。 |
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. |
| 0x259 | 在卷上找到一个 ID 匹配的对象，但它超过了该操作所用句柄的作用域。 |
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. |
| 0x25A | 必须增加 bucket 数组。请运行后再重试事务处理。 |
The bucket array must be grown. Retry transaction after doing so. |
| 0x25B | 用户/内核排列缓冲区溢出。 |
The user/kernel marshalling buffer has overflowed. |
| 0x25C | 提供的变量结构包含无效数据。 |
The supplied variant structure contains invalid data. |
| 0x25D | 指定的缓冲区中包含类型错误的数据。 |
The specified buffer contains ill-formed data. |
| 0x25E | {审核失败}未能生成安全审核。 |
{Audit Failed}An attempt to generate a security audit failed. |
| 0x25F | 当前的过程未设置计时器分辨率。 |
The timer resolution was not previously set by the current process. |
| 0x260 | 帐户信息不足，无法登录。 |
There is insufficient account information to log you on. |
| 0x261 | {无效的 DLL 入口点}动态链接库 %hs 并未正确地写入。堆栈指针处于不一致的状态。入口点必须声明为 WINAPI 或 STDCALL。如果放弃加载 DLL，请选择“是”。如果继续运行，请选择“否”。选择“否”可能会造成应用程序操作不正常。 |
{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. |
| 0x262 | {无效的服务回调入口点}%hs 服务并未正确写入。堆栈指针处于不一致的状态。回调入口点必须声明为 WINAPI 或 STDCALL。选择“确定”会造成服务继续操作。但服务过程操作可能不正确。 |
{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. |
| 0x263 | IP 地址与网络上的其他系统有冲突。 |
There is an IP address conflict with another system on the network |
| 0x265 | {注册表空间不足}系统已达到注册表系统部分所允许的最大大小。将忽略附加存储请求。 |
{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. |
| 0x266 | 没有启动回调功能时，回调系统服务不能运行。 |
A callback return system service cannot be executed when no callback is active. |
| 0x267 | 提供的密码太短，不符合用户帐户的策略请求。请输入较长的密码。 |
The password provided is too short to meet the policy of your user account.Please choose a longer password. |
| 0x268 | 你的用户帐户策略不允许你经常更改密码。这样可避免用户将密码更改回熟悉的，但可能被别人猜到的密码。如果你觉得密码已经被别人知道，请立即与管理员联系以取得新的密码。 |
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. |
| 0x269 | 更改的密码过去曾经用过。你的用户帐户策略不允许你这样做，请选择没有用过的密码。 |
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. |
| 0x26A | 不支持指定的压缩格式。 |
The specified compression format is unsupported. |
| 0x26B | 指定的硬件配置文件配置无效。 |
The specified hardware profile configuration is invalid. |
| 0x26C | 指定的即插即用注册表设备的路径无效。 |
The specified Plug and Play registry device path is invalid. |
| 0x26D | 指定的限额列表与其描述符不一致。 |
The specified quota list is internally inconsistent with its descriptor. |
| 0x26E | {Windows 测试版通知}所安装的 Windows 测试版已经超过使用期限。系统将在一小时后关闭。要还原对所安装 Windows 的访问，请使用该产品的分发许可证进行升级。 |
{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. |
| 0x26F | {无效的系统 DLL 重定位}系统 DLL %hs 在内存中重定位。应用程序将不能正常运行。由于 DLL %hs 占用了为 Windows 系统 DLL 保存的地址范围而产生了错误。应当与提供该 DLL 的供应商联系以得到新的 DLL。 |
{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. |
| 0x270 | {DLL 初始化失败}因为窗口站已关闭，应用程序初始化失败。 |
{DLL Initialization Failed}The application failed to initialize because the window station is shutting down. |
| 0x271 | 验证过程需要进行到下一步。 |
The validation process needs to continue on to the next step. |
| 0x272 | 不再有与当前索引列举相匹配的项。 |
There are no more matches for the current index enumeration. |
| 0x273 | 由于冲突，无法将区域添加到区域列表。 |
The range could not be added to the range list because of a conflict. |
| 0x274 | 服务器进程运行的 SID 跟客户端要求的不同。 |
The server process is running under a SID different than that required by client. |
| 0x275 | 不能启用标为“只用于否定”的组。 |
A group marked use for deny only cannot be enabled. |
| 0x276 | {异常}多浮点错。 |
{EXCEPTION}Multiple floating point faults. |
| 0x277 | {异常}多浮点陷阱。 |
{EXCEPTION}Multiple floating point traps. |
| 0x278 | 不支持所请求的接口。 |
The requested interface is not supported. |
| 0x279 | {系统待机失败}驱动程序 %hs 不支持待机模式。更新这个驱动程序会允许系统进入待机模式。 |
{System Standby Failed}The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode. |
| 0x27A | 系统文件 %1 已损坏而且已经被替换。 |
The system file %1 has become corrupt and has been replaced. |
| 0x27B | {虚拟内存最小值太低}你的系统虚拟内存太低。Windows 会增加虚拟内存页面文件的大小。在这个过程中，一些应用程序的内存请求会被拒绝。有关详细信息，请参阅“帮助”。 |
{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. |
| 0x27C | 删除了一个设备，因此必须重新启动枚举。 |
A device was removed so enumeration must be restarted. |
| 0x27D | {严重系统错误}系统映像 %s 没有正确签名。文件已由被签名的文件替换。系统已被关闭。 |
{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. |
| 0x27E | 不重新启动计算机，设备不会开始运行。 |
Device will not start without a reboot. |
| 0x27F | 电源不足，无法完成要求的操作。 |
There is not enough power to complete the requested operation. |
| 0x280 | ERROR_MULTIPLE_FAULT_VIOLATION |
ERROR_MULTIPLE_FAULT_VIOLATION |
| 0x281 | 系统正在关机。 |
The system is in the process of shutting down. |
| 0x282 | 试图删除 DebugPort 生成的进程，但端口没有同此进程相关联。 |
An attempt to remove a processes DebugPort was made, but a port was not already associated with the process. |
| 0x283 | 这一版本的 Windows 与目录林、域或域控制器的版本不兼容。 |
This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller. |
| 0x284 | 在范围列表中找不到指定的范围。 |
The specified range could not be found in the range list. |
| 0x286 | 系统正在以安全模式启动，因此没有加载驱动程序。 |
The driver was not loaded because the system is booting into safe mode. |
| 0x287 | 由于初始化调用失败，驱动程序无法加载。 |
The driver was not loaded because it failed its initialization call. |
| 0x288 | \"%hs\" 在接通电源或读取该设备的配置时出现错误。这可能由硬件故障或接触不良引起。 |
The \"%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. |
| 0x289 | 创建操作失败，因为名称含有至少一个装入点，它引起生成的卷没有同指定的设备对象连接上。 |
The 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. |
| 0x28A | 设备对象参数不是有效的设备对象，或者没有附到文件名指定的卷。 |
The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. |
| 0x28B | 发生计算机检查错误。有关额外信息，请查阅系统事件日志。 |
A Machine Check Error has occurred. Please check the system eventlog for additional information. |
| 0x28C | 处理驱动程序数据库时发生错误 [%2]。 |
There was error [%2] processing the driver database. |
| 0x28D | 系统配置单元大小已超出限制。 |
System hive size has exceeded its limit. |
| 0x28E | 上一版本的驱动程序还在内存中，因此无法加载驱动程序。 |
The driver could not be loaded because a previous version of the driver is still in memory. |
| 0x28F | {卷影复制服务}卷影复制服务准备用于休眠的卷 %hs 时请稍候。 |
{Volume Shadow Copy Service}Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation. |
| 0x290 | 系统未能休眠(错误代码是 %hs)。系统重新启动之前，休眠将被禁用。 |
The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted. |
| 0x291 | 提供的密码太长，不符合用户帐户的策略。请选择一个较短的密码。 |
The password provided is too long to meet the policy of your user account.Please choose a shorter password. |
| 0x299 | 由于文件系统限制，因此请求的操作无法完成 |
The requested operation could not be completed due to a file system limitation |
| 0x29C | 出现声明故障。 |
An assertion failure has occurred. |
| 0x29D | ACPI 子系统中出现故障。 |
An error occurred in the ACPI subsystem. |
| 0x29E | WOW 断言错误。 |
WOW Assertion Error. |
| 0x29F | 系统 BIOS MPS 表格缺一个设备。不会使用设备。有关系统 BIOS 更新，请与系统供应商联系。 |
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. |
| 0x2A0 | 转换程序未能转换资源。 |
A translator failed to translate resources. |
| 0x2A1 | IRQ 转换程序未能转换资源。 |
A IRQ translator failed to translate resources. |
| 0x2A2 | 驱动程序 %2 返回了子设备 (%3) 的无效 ID。 |
Driver %2 returned invalid ID for a child device (%3). |
| 0x2A3 | {内核调试程序}由中断触发的系统调试程序。 |
{Kernel Debugger Awakened}the system debugger was awakened by an interrupt. |
| 0x2A4 | {已关闭句柄}依操作请求而自动关闭的对象句柄。 |
{Handles Closed}Handles to objects have been automatically closed as a result of the requested operation. |
| 0x2A5 | {过多的信息}指定的访问控制列表(ACL)中包含过多的信息。 |
{Too Much Information}The specified access control list (ACL) contained more information than was expected. |
| 0x2A6 | 这个警告等级状态指出事务状态已经存在于注册表子目录树，但之前事务确认操作已中止。确认操作并未完成，也未还原到上一步的操作。(它可能还处在确认状态)。 |
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). |
| 0x2A7 | {媒体已更改}媒体可能已更改。 |
{Media Changed}The media may have changed. |
| 0x2A8 | {GUID 替换}在将全局标识符(GUID)转换为 Windows 安全 ID (SID)的过程中，找不到系统定义的 GUID 前缀。已使用不会损害系统安全的替代前缀。但是，这可能提供更严格的访问限制。 |
{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. |
| 0x2A9 | 创建操作在到达符号链接后停止。 |
The create operation stopped after reaching a symbolic link |
| 0x2AA | 一个长跳转已经运行。 |
A long jump has been executed. |
| 0x2AB | 即插即用查询未成功。 |
The Plug and Play query operation was not successful. |
| 0x2AC | 帧合并已经执行。 |
A frame consolidation has been executed. |
| 0x2AD | {注册表配置单元已恢复}注册表配置单元(文件):%hs曾经损坏而且已经恢复。可能丢失一些数据。 |
{Registry Hive Recovered}Registry hive (file):%hswas corrupted and it has been recovered. Some data might have been lost. |
| 0x2AE | 应用程序正在试图从模块 %hs 运行可执行代码。这可能不安全。另一模块 %hs 可用。是否让应用程序使用安全模块 %hs? |
The application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs? |
| 0x2AF | 应用程序正在从模块 %hs 加载可执行代码。这是安全的，但可能与操作系统的上一版本不兼容。另一模块 %hs 可用。是否让应用程序使用安全模块 %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? |
| 0x2B0 | 调试程序没有处理异常现象。 |
Debugger did not handle the exception. |
| 0x2B1 | 调试程序会以后答复。 |
Debugger will reply later. |
| 0x2B2 | 调试程序无法提供句柄。 |
Debugger cannot provide handle. |
| 0x2B3 | 调试程序终止了线程。 |
Debugger terminated thread. |
| 0x2B4 | 调试程序终止了过程。 |
Debugger terminated process. |
| 0x2B5 | 调试程序得到了控件 C。 |
Debugger got control C. |
| 0x2B6 | 调试程序打印了控件 C 上的异常现象。 |
Debugger printed exception on control C. |
| 0x2B7 | 调试程序收到了 RIP 异常现象。 |
Debugger received RIP exception. |
| 0x2B8 | 调试程序收到了控件中断。 |
Debugger received control break. |
| 0x2B9 | 调试程序命令通信异常。 |
Debugger command communication exception. |
| 0x2BA | {对象已存在}试图创建一名称已存在的对象。 |
{Object Exists}An attempt was made to create an object and the object name already existed. |
| 0x2BB | {暂停线程}暂停线程时将暂时终止线程。当继续线程时即取消终止。 |
{Thread Suspended}A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded. |
| 0x2BC | {映像重定位}无法在映像文件中指定的地址映射该映像文件。必须对映像文件进行本地修正。 |
{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. |
| 0x2BD | 这个信息等级状态表示某个特定注册表的子目录树事务处理状态不存在，且必须创建。 |
This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created. |
| 0x2BE | {段加载}一个虚拟 DOS 机(VDM)正在加载、卸载或移动一个 MS-DOS 或 Win16 程序区域映像。产生异常让除错程序能在这些 16 位区域中加载、卸载或跟踪符号与中断点。 |
{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. |
| 0x2BF | {无效的当前目录}过程无法切换到启动当前目录 %hs。选择“确定”将当前目录设置为 %hs，或选择“取消”退出。 |
{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. |
| 0x2C0 | {冗余读取}若要完成读取请求，NT 容错文件系统必须从冗余备份中成功地读取所请求的数据。这项操作已完成，因文件系统的容错卷的一个部分失败，而无法重新指派设备的失败区域。 |
{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. |
| 0x2C1 | {冗余写入}若要完成写入请求，NT 容错文件系统必须成功地写入一冗余备份。这项操作已完成，因文件系统的容错卷一个部分失败，而无法重新分配设备的失败区域。 |
{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. |
| 0x2C2 | {机器类型不匹配}映像文件 %hs 无效，但它对另一种机器类型有效。选择“确定”继续，或者“取消”使加载 DLL 失败。 |
{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. |
| 0x2C3 | {已接收部分数据}网络已向客户端传输部分数据。稍后再传送其余数据。 |
{Partial Data Received}The network transport returned partial data to its client. The remaining data will be sent later. |
| 0x2C4 | {已接收发送的数据}网络传输传回数据至客户端并在远程系统上标记已发送。 |
{Expedited Data Received}The network transport returned data to its client that was marked as expedited by the remote system. |
| 0x2C5 | {已接收发送的部分数据}网络传输已传回部分数据至客户端且标记为远程系统发送的数据。稍后再传送其余数据。 |
{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. |
| 0x2C6 | {TDI 事件完成}TDI 标示已成功完成。 |
{TDI Event Done}The TDI indication has completed successfully. |
| 0x2C7 | {TDI 事件尚未完成}TDI 标示进入等待状态。 |
{TDI Event Pending}The TDI indication has entered the pending state. |
| 0x2C8 | 正在检查 %wZ 上的文件系统 |
Checking file system on %wZ |
| 0x2C9 | {致命的应用程序退出}%hs |
{Fatal Application Exit}%hs |
| 0x2CA | 一个预定义的句柄引用指定的注册表项。 |
The specified registry key is referenced by a predefined handle. |
| 0x2CB | {解除页面锁定}页面锁定的保护状态更改为“不允许访问”且从内存及过程中解除页面锁定。 |
{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. |
| 0x2CC | %hs |
%hs |
| 0x2CD | {页面锁定}要锁定的页面已锁定。 |
{Page Locked}One of the pages to lock was already locked. |
| 0x2CE | 弹出应用程序: %1: %2 |
Application popup: %1 : %2 |
| 0x2CF | ERROR_ALREADY_WIN32 |
ERROR_ALREADY_WIN32 |
| 0x2D0 | {计算机类型不匹配}映像文件 %hs 无效，但它对另一种计算机类型有效。 |
{Machine Type Mismatch}The image file %hs is valid, but is for a machine type other than the current machine. |
| 0x2D1 | 执行了一次转交，没有可以运行的线程。 |
A yield execution was performed and no thread was available to run. |
| 0x2D2 | 定时器 API 可还原标志被忽略。 |
The resumable flag to a timer API was ignored. |
| 0x2D3 | 仲裁程序已经将这些资源的仲裁顺延到它的父系上 |
The arbiter has deferred arbitration of these resources to its parent |
| 0x2D4 | 插入的 CardBus 设备无法启动，因为“%hs”上的配置错误。 |
The inserted CardBus device cannot be started because of a configuration error on \"%hs\". |
| 0x2D5 | 在此多处理器系统中的 CPU 不都在同一修订等级。若要使用所有处理器，则操作系统本身会受到系统中性能最低的处理器的限制。如果此系统出现问题，请与 CPU 制造商联系，以确认是否支持这种处理器的混合使用。 |
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. |
| 0x2D6 | 系统进入休眠。 |
The system was put into hibernation. |
| 0x2D7 | 系统从休眠中恢复。 |
The system was resumed from hibernation. |
| 0x2D8 | Windows 检测到系统固件 (BIOS) 已经更新 [以前的固件日期 = %2, 当前固件日期 %3]。 |
Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]. |
| 0x2D9 | 设备驱动程序正在泄露导致系统降级的锁定 I/O 页。系统已经自动启用跟踪代码以重试并捕获原因。 |
A 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. |
| 0x2DA | 系统已经恢复 |
The system has awoken |
| 0x2DB | ERROR_WAIT_1 |
ERROR_WAIT_1 |
| 0x2DC | ERROR_WAIT_2 |
ERROR_WAIT_2 |
| 0x2DD | ERROR_WAIT_3 |
ERROR_WAIT_3 |
| 0x2DE | ERROR_WAIT_63 |
ERROR_WAIT_63 |
| 0x2DF | ERROR_ABANDONED_WAIT_0 |
ERROR_ABANDONED_WAIT_0 |
| 0x2E0 | ERROR_ABANDONED_WAIT_63 |
ERROR_ABANDONED_WAIT_63 |
| 0x2E1 | ERROR_USER_APC |
ERROR_USER_APC |
| 0x2E2 | ERROR_KERNEL_APC |
ERROR_KERNEL_APC |
| 0x2E3 | ERROR_ALERTED |
ERROR_ALERTED |
| 0x2E4 | 请求的操作需要提升。 |
The requested operation requires elevation. |
| 0x2E5 | 因为文件名产生符号链接，所以需由对象管理器重新运行分析操作。 |
A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. |
| 0x2E6 | 在 oplock 中断进行中完成一项打开/创建操作。 |
An open/create operation completed while an oplock break is underway. |
| 0x2E7 | 文件系统已装入新卷。 |
A new volume has been mounted by a file system. |
| 0x2E8 | 这个成功等级状态指出事务状态已经存在于注册表子目录树，但之前事务确认已中止。现已完成确认。这个状态数值是由运行库(RTL)注册表事务包(RXact)所返回的。 |
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. |
| 0x2E9 | 表示由于关闭句柄而产生的提示更改请求已完成。 |
This indicates that a notify change request has been completed due to closing the handle which made the notify change request. |
| 0x2EA | {主要传输连接故障}试图连接到主要传输上的远程服务器 %hs，但没有成功。计算机可以连接到次要传输上。 |
{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. |
| 0x2EB | 页面错误为传输错误。 |
Page fault was a transition fault. |
| 0x2EC | 页面错误为请求 0 错误。 |
Page fault was a demand zero fault. |
| 0x2EF | 可以从次要存储设备上读取以弥补页面错误。 |
Page fault was satisfied by reading from a secondary storage device. |
| 0x2F0 | 操作时锁定高速缓存页。 |
Cached page was locked during operation. |
| 0x2F1 | 页面文件中有故障转储。 |
Crash dump exists in paging file. |
| 0x2F2 | 指定的缓冲区含有的都是零。 |
Specified buffer contains all zeros. |
| 0x2F4 | 设备已经完成“查询停止”，并且它的资源需求已更改。 |
The device has succeeded a query-stop and its resource requirements have changed. |
| 0x2F5 | 转换器已经将这些资源转换到全局空间，不应该运行更多的转换。 |
The translator has translated these resources into the global space and no further translations should be performed. |
| 0x2F6 | 终止的进程没有线程来终止。 |
A process being terminated has no threads to terminate. |
| 0x2F7 | 指定的进程不是作业的一部分。 |
The specified process is not part of a job. |
| 0x2F8 | 指定的进程是作业的一部分。 |
The specified process is part of a job. |
| 0x2F9 | {卷影复制服务}系统准备好进入休眠。 |
{Volume Shadow Copy Service}The system is now ready for hibernation. |
| 0x2FA | 文件系统或文件系统筛选器驱动程序已经成功完成 FsFilter 操作。 |
A file system or file system filter driver has successfully completed an FsFilter operation. |
| 0x2FB | 指定的中断矢量已经连接。 |
The specified interrupt vector was already connected. |
| 0x2FC | 指定的中断矢量仍处于连接状态。 |
The specified interrupt vector is still connected. |
| 0x2FD | 操作被阻止，正在等待操作锁定完成。 |
An operation is blocked waiting for an oplock. |
| 0x2FE | 调试程序处理了异常现象 |
Debugger handled exception |
| 0x2FF | 调试程序继续运行 |
Debugger continued |
| 0x300 | 用户模式回调中出现异常，应删除内核回调框架。 |
An exception occurred in a user mode callback and the kernel callback frame should be removed. |
| 0x301 | 禁止压缩该卷。 |
Compression is disabled for this volume. |
| 0x302 | 数据提供程序无法在结果集中向后获取数据。 |
The data provider cannot fetch backwards through a result set. |
| 0x303 | 数据提供程序无法在结果集中向后滚动。 |
The data provider cannot scroll backwards through a result set. |
| 0x304 | 数据提供程序要求在请求更多数据之前释放先前获取的数据。 |
The data provider requires that previously fetched data is released before asking for more data. |
| 0x305 | 数据提供程序无法解释访问器中绑定列的标志集。 |
The data provider was not able to interpret the flags set for a column binding in an accessor. |
| 0x306 | 处理请求时出现一个或多个错误。 |
One or more errors occurred while processing the request. |
| 0x307 | 实现无法执行此请求。 |
The implementation is not capable of performing the request. |
| 0x308 | 组件的客户端请求一个操作，但由于组件实例的状态，该操作无效。 |
The client of a component requested an operation which is not valid given the state of the component instance. |
| 0x309 | 无法解析版本号。 |
A version number could not be parsed. |
| 0x30A | 迭代程序的起始位置无效。 |
The iterator's start position is invalid. |
| 0x30B | 硬件已报告不可纠正的内存错误。 |
The hardware has reported an uncorrectable memory error. |
| 0x30C | 尝试的操作要求启用自疗功能。 |
The attempted operation required self healing to be enabled. |
| 0x30D | 桌面堆在分配会话内存时遇到错误。系统事件日志中包含详细信息。 |
The Desktop heap encountered an error while allocating session memory. There is more information in the system event log. |
| 0x30E | 系统电源状态正从 %2 转换为 %3。 |
The system power state is transitioning from %2 to %3. |
| 0x30F | 系统电源状态正从 %2 转换为 %3，但可能进入 %4。 |
The system power state is transitioning from %2 to %3 but could enter %4. |
| 0x310 | 由于 MCA，正使用 MCA EXCEPTION 调度线程。 |
A thread is getting dispatched with MCA EXCEPTION because of MCA. |
| 0x311 | 对 %1 的访问由策略规则 %2 监视。 |
Access to %1 is monitored by policy rule %2. |
| 0x312 | 管理员用策略规则 %2 限制了对 %1 的访问。 |
Access to %1 has been restricted by your Administrator by policy rule %2. |
| 0x313 | 有效的休眠文件已经变得无效，应该放弃该文件。 |
A valid hibernation file has been invalidated and should be abandoned. |
| 0x314 | {延迟写入失败}Windows 无法保存文件 %hs 的所有数据；数据已丢失。此错误可能是由网络连接问题所导致。请尝试将此文件保存到其他位置。 |
{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. |
| 0x315 | {延迟写入失败}Windows 无法保存文件 %hs 的所有数据；数据已丢失。此错误由文件所在的服务器返回。请尝试将此文件保存到其他位置。 |
{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. |
| 0x316 | {延迟写入失败}Windows 无法保存文件 %hs 的所有数据；数据已丢失。如果设备已移除或介质为写保护状态，则可能导致此错误。 |
{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. |
| 0x317 | 此设备所需的资源与 MCFG 表冲突。 |
The resources required for this device conflict with the MCFG table. |
| 0x318 | 卷处于联机时无法进行修复。请安排使卷脱机，以便能够对其进行修复。 |
The volume repair could not be performed while it is online.Please schedule to take the volume offline so that it can be repaired. |
| 0x319 | 卷修复不成功。 |
The volume repair was not successful. |
| 0x31A | 其中一个卷损坏日志已满。无法记录检测到的更多损坏。 |
One of the volume corruption logs is full. Further corruptions that may be detected won't be logged. |
| 0x31B | 其中一个卷损坏日志内部已损坏，需要重新创建。该卷可能包含未检测到的损坏，并且必须进行扫描。 |
One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned. |
| 0x31C | 无法对其中一个卷损坏日志进行操作。 |
One of the volume corruption logs is unavailable for being operated on. |
| 0x31D | 已经删除其中一个卷损坏日志，但是该日志中仍然包含损坏记录。该卷包含检测到的损坏，并且必须进行扫描。 |
One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned. |
| 0x31E | chkdsk 已经清除了其中一个卷损坏日志，并且不再包含真实损坏。 |
One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions. |
| 0x31F | 卷中存在孤立文件，但是无法恢复，因为无法在恢复目录中创建更多新名称。文件必须从恢复目录中移出。 |
Orphaned 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. |
| 0x320 | 与此句柄相关联的操作锁定现在与其他句柄相关联。 |
The oplock that was associated with this handle is now associated with a different handle. |
| 0x321 | 无法授予所请求级别的操作锁定。较低级别的操作锁定可能可用。 |
An oplock of the requested level cannot be granted. An oplock of a lower level may be available. |
| 0x322 | 操作未能成功完成，因为这将导致操作锁定中断。调用方已要求现有操作锁定不被中断。 |
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. |
| 0x323 | 此操作锁定所关联的句柄已关闭。操作锁定现已中断。 |
The handle with which this oplock was associated has been closed. The oplock is now broken. |
| 0x324 | 指定的访问控制项(ACE)不包含某个条件。 |
The specified access control entry (ACE) does not contain a condition. |
| 0x325 | 指定的访问控制项(ACE)包含无效的条件。 |
The specified access control entry (ACE) contains an invalid condition. |
| 0x326 | 已吊销对指定文件句柄的访问权限。 |
Access to the specified file handle has been revoked. |
| 0x327 | {映像重定位}虽然映射映像文件的地址不同于映像文件中指定的地址，但系统仍会自动对映像进行修正。 |
{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. |
| 0x328 | 无法完成对加密文件执行的读取或写入操作，因为尚未打开该文件以进行数据访问。 |
The read or write operation to an encrypted file could not be completed because the file has not been opened for data access. |
| 0x329 | 文件元数据优化已在进行中。 |
File metadata optimization is already in progress. |
| 0x32A | 由于配额操作仍在进行中，请求的操作失败。 |
The requested operation failed due to quota operation is still in progress. |
| 0x32B | 已吊销对指定句柄的访问权限。 |
Access to the specified handle has been revoked. |
| 0x32C | 回调函数必须通过内联方式调用。 |
The callback function must be invoked inline. |
| 0x32D | 指定的 CPU 设置 ID 无效。 |
The specified CPU Set IDs are invalid. |
| 0x3E2 | 拒绝访问扩展属性。 |
Access to the extended attribute was denied. |
| 0x3E3 | 由于线程退出或应用程序请求，已中止 I/O 操作。 |
The I/O operation has been aborted because of either a thread exit or an application request. |
| 0x3E4 | 重叠 I/O 事件不在信号状态中。 |
Overlapped I/O event is not in a signaled state. |
| 0x3E5 | 重叠 I/O 操作在进行中。 |
Overlapped I/O operation is in progress. |
| 0x3E6 | 内存位置访问无效。 |
Invalid access to memory location. |
| 0x3E7 | 执行页内操作时的错误。 |
Error performing inpage operation. |
| 0x3E9 | 递归太深；堆栈溢出。 |
Recursion too deep; the stack overflowed. |
| 0x3EA | 窗口无法在已发送的消息上操作。 |
The window cannot act on the sent message. |
| 0x3EB | 无法完成此功能。 |
Cannot complete this function. |
| 0x3EC | 无效标志。 |
Invalid flags. |
| 0x3ED | 此卷不包含可识别的文件系统。请确定所有请求的文件系统驱动程序已加载，且此卷未损坏。 |
The 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. |
| 0x3EE | 文件所在的卷已被外部更改，因此打开的文件不再有效。 |
The volume for a file has been externally altered so that the opened file is no longer valid. |
| 0x3EF | 无法在全屏幕模式下运行请求的操作。 |
The requested operation cannot be performed in full-screen mode. |
| 0x3F0 | 试图引用不存在的令牌。 |
An attempt was made to reference a token that does not exist. |
| 0x3F1 | 配置注册表数据库损坏。 |
The configuration registry database is corrupt. |
| 0x3F2 | 配置注册表项无效。 |
The configuration registry key is invalid. |
| 0x3F3 | 无法打开配置注册表项。 |
The configuration registry key could not be opened. |
| 0x3F4 | 无法读取配置注册表项。 |
The configuration registry key could not be read. |
| 0x3F5 | 无法写入配置注册表项。 |
The configuration registry key could not be written. |
| 0x3F6 | 注册表数据库中的某一文件必须使用记录或替换副本来恢复。恢复成功完成。 |
One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful. |
| 0x3F7 | 注册表损坏。包含注册表数据的某一文件结构损坏，或系统的文件内存映像损坏，或因为替换副本、日志缺少或损坏而无法恢复文件。 |
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. |
| 0x3F8 | 由注册表启动的 I/O 操作失败并无法恢复。注册表无法读入、写出或清除任意一个包含注册表系统映像的文件。 |
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. |
| 0x3F9 | 系统试图加载或还原文件到注册表，但指定的文件并非注册表文件格式。 |
The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format. |
| 0x3FA | 试图在标记为删除的注册表项上进行不合法的操作。 |
Illegal operation attempted on a registry key that has been marked for deletion. |
| 0x3FB | 系统无法分配注册表日志中所需空间。 |
System could not allocate the required space in a registry log. |
| 0x3FC | 无法在已有子项或值的注册表项中创建符号链接。 |
Cannot create a symbolic link in a registry key that already has subkeys or values. |
| 0x3FD | 无法在易变父项下创建稳定子项。 |
Cannot create a stable subkey under a volatile parent key. |
| 0x3FE | 正在完成通知更改请求，而且信息没有返回到呼叫方的缓冲区中。当前呼叫方必须枚举文件来查找更改。 |
A 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. |
| 0x41B | 停止控制被发送到其他正在运行的服务所依赖的服务。 |
A stop control has been sent to a service that other running services are dependent on. |
| 0x41C | 请求的控件对此服务无效。 |
The requested control is not valid for this service. |
| 0x41D | 服务没有及时响应启动或控制请求。 |
The service did not respond to the start or control request in a timely fashion. |
| 0x41E | 无法创建此服务的线程。 |
A thread could not be created for the service. |
| 0x41F | 服务数据库已锁定。 |
The service database is locked. |
| 0x420 | 服务的实例已在运行中。 |
An instance of the service is already running. |
| 0x421 | 帐户名无效或不存在，或者密码对于指定的帐户名无效。 |
The account name is invalid or does not exist, or the password is invalid for the account name specified. |
| 0x422 | 无法启动服务，原因可能是已被禁用或与其相关联的设备没有启动。 |
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. |
| 0x423 | 指定了循环服务依赖关系。 |
Circular service dependency was specified. |
| 0x424 | 指定的服务未安装。 |
The specified service does not exist as an installed service. |
| 0x425 | 服务无法在此时接受控制信息。 |
The service cannot accept control messages at this time. |
| 0x426 | 服务尚未启动。 |
The service has not been started. |
| 0x427 | 服务进程无法连接到服务控制器上。 |
The service process could not connect to the service controller. |
| 0x428 | 当处理控制请求时，在服务中发生异常。 |
An exception occurred in the service when handling the control request. |
| 0x429 | 指定的数据库不存在。 |
The database specified does not exist. |
| 0x42A | 服务已返回特定的服务错误代码。 |
The service has returned a service-specific error code. |
| 0x42B | 进程意外终止。 |
The process terminated unexpectedly. |
| 0x42C | 依赖服务或组无法启动。 |
The dependency service or group failed to start. |
| 0x42D | 由于登录失败而无法启动服务。 |
The service did not start due to a logon failure. |
| 0x42E | 启动后，服务停留在启动暂停状态。 |
After starting, the service hung in a start-pending state. |
| 0x42F | 指定的服务数据库锁定无效。 |
The specified service database lock is invalid. |
| 0x430 | 指定的服务已标记为删除。 |
The specified service has been marked for deletion. |
| 0x431 | 指定的服务已存在。 |
The specified service already exists. |
| 0x432 | 系统当前以最后所知的好的配置运行。 |
The system is currently running with the last-known-good configuration. |
| 0x433 | 服务不存在，或已被标记为删除。 |
The dependency service does not exist or has been marked for deletion. |
| 0x434 | 已接受使用当前引导作为最后一次正确的控制设置。 |
The current boot has already been accepted for use as the last-known-good control set. |
| 0x435 | 上次启动之后，仍未尝试引导服务。 |
No attempts to start the service have been made since the last boot. |
| 0x436 | 名称已用作服务名或服务显示名称。 |
The name is already in use as either a service name or a service display name. |
| 0x437 | 此服务的帐户不同于运行于同一进程上的其他服务的帐户。 |
The account specified for this service is different from the account specified for other services running in the same process. |
| 0x438 | 只能为 Win32 服务设置失败操作，不能为驱动程序设置。 |
Failure actions can only be set for Win32 services, not for drivers. |
| 0x439 | 这个服务所运行的处理和服务控制管理器相同。所以，如果服务处理程序意外中止的话，服务控制管理器无法进行任何操作。 |
This 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. |
| 0x43A | 这个服务尚未设置恢复程序。 |
No recovery program has been configured for this service. |
| 0x43B | 配置成在该可执行程序中运行的这个服务不能执行该服务。 |
The executable program that this service is configured to run in does not implement the service. |
| 0x43C | 不能在安全模式中启动这项服务 |
This service cannot be started in Safe Mode |
| 0x44C | 已达磁带的实际结尾。 |
The physical end of the tape has been reached. |
| 0x44D | 磁带访问已达文件标记。 |
A tape access reached a filemark. |
| 0x44E | 已达磁带或磁盘分区的开头。 |
The beginning of the tape or a partition was encountered. |
| 0x44F | 磁带访问已达一组文件的结尾。 |
A tape access reached the end of a set of files. |
| 0x450 | 磁带上不再有任何数据。 |
No more data is on the tape. |
| 0x451 | 磁带不能分区。 |
Tape could not be partitioned. |
| 0x452 | 在访问多卷分区的新磁带时，当前的块大小不正确。 |
When accessing a new tape of a multivolume partition, the current block size is incorrect. |
| 0x453 | 在加载磁带时找不到磁带分区信息。 |
Tape partition information could not be found when loading a tape. |
| 0x454 | 无法锁定媒体弹出功能。 |
Unable to lock the media eject mechanism. |
| 0x455 | 无法卸载媒体发。 |
Unable to unload the media. |
| 0x456 | 驱动器中的媒体可能已更改。 |
The media in the drive may have changed. |
| 0x457 | 已重置 I/O 总线。 |
The I/O bus was reset. |
| 0x458 | 驱动器中没有媒体。 |
No media in drive. |
| 0x459 | 在多字节的目标代码页中，没有此 Unicode 字符可以映射到的字符。 |
No mapping for the Unicode character exists in the target multi-byte code page. |
| 0x45A | 动态链接库(DLL)初始化例程失败。 |
A dynamic link library (DLL) initialization routine failed. |
| 0x45C | 因为没有任何进行中的关机过程，所以无法中止系统关机。 |
Unable to abort the system shutdown because no shutdown was in progress. |
| 0x45D | 由于 I/O 设备错误，无法运行此项请求。 |
The request could not be performed because of an I/O device error. |
| 0x45E | 串行设备初始化不成功。串行驱动程序将卸载。 |
No serial device was successfully initialized. The serial driver will unload. |
| 0x45F | 无法打开正在与其他设备共享中断请求(IRQ)的设备。至少有一个使用该 IRQ 的其他设备已打开。 |
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. |
| 0x460 | 序列 I/O 操作已由另一个串行端口的写入完成。(IOCTL_SERIAL_XOFF_COUNTER 已达零。) |
A serial I/O operation was completed by another write to the serial port.(The IOCTL_SERIAL_XOFF_COUNTER reached zero.) |
| 0x461 | 因为已过超时时间，所以串行 I/O 操作完成。(IOCTL_SERIAL_XOFF_COUNTER 未达零。) |
A serial I/O operation completed because the timeout period expired.(The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.) |
| 0x462 | 在软盘上找不到 ID 地址标记。 |
No ID address mark was found on the floppy disk. |
| 0x463 | 软盘扇区 ID 字符域与软盘控制器磁道地址不匹配。 |
Mismatch between the floppy disk sector ID field and the floppy disk controller track address. |
| 0x464 | 软盘控制器报告软盘驱动程序不能识别的错误。 |
The floppy disk controller reported an error that is not recognized by the floppy disk driver. |
| 0x465 | 软盘控制器返回与其寄存器中不一致的结果。 |
The floppy disk controller returned inconsistent results in its registers. |
| 0x466 | 访问硬盘时，重新校准操作失败。重试之后仍然不成功。 |
While accessing the hard disk, a recalibrate operation failed, even after retries. |
| 0x467 | 访问硬盘时，磁盘操作失败。重试之后仍然不成功。 |
While accessing the hard disk, a disk operation failed even after retries. |
| 0x468 | 当访问硬盘时，即使失败，仍须重置磁盘控制器。 |
While accessing the hard disk, a disk controller reset was needed, but even that failed. |
| 0x469 | 已达磁带结尾。 |
Physical end of tape encountered. |
| 0x46A | 服务器存储不足，无法处理此命令。 |
Not enough server storage is available to process this command. |
| 0x46B | 检测出潜在的死锁状态。 |
A potential deadlock condition has been detected. |
| 0x46C | 指定的基址或文件偏移量没有适当对齐。 |
The base address or the file offset specified does not have the proper alignment. |
| 0x474 | 更改系统供电状态的尝试被另一应用程序或驱动程序否决。 |
An attempt to change the system power state was vetoed by another application or driver. |
| 0x475 | 系统 BIOS 更改系统供电状态的尝试失败。 |
The system BIOS failed an attempt to change the system power state. |
| 0x476 | 试图在文件上创建超过文件系统支持的链接数。 |
An attempt was made to create more links on a file than the file system supports. |
| 0x47E | 指定程序要求更新的 Windows 版本。 |
The specified program requires a newer version of Windows. |
| 0x47F | 指定程序不是 Windows 或 MS-DOS 程序。 |
The specified program is not a Windows or MS-DOS program. |
| 0x480 | 只能启动该指定程序的一个范例。 |
Cannot start more than one instance of the specified program. |
| 0x481 | 该指定程序是为以前一个版本的 Windows 而写的。 |
The specified program was written for an earlier version of Windows. |
| 0x482 | 运行该应用程序所需的一个库文件已被损坏。 |
One of the library files needed to run this application is damaged. |
| 0x483 | 没有应用程序与此操作的指定文件有关联。 |
No application is associated with the specified file for this operation. |
| 0x484 | 在输送命令到应用程序的过程中出现错误。 |
An error occurred in sending the command to the application. |
| 0x485 | 执行该应用程序所需的库文件之一无法找到。 |
One of the library files needed to run this application cannot be found. |
| 0x486 | 当前程序已使用了 Window 管理器对象的系统允许的所有句柄。 |
The current process has used all of its system allowance of handles for Window Manager objects. |
| 0x487 | 消息只能与同步操作一起使用。 |
The message can be used only with synchronous operations. |
| 0x488 | 指出的源元素没有媒体。 |
The indicated source element has no media. |
| 0x489 | 指出的目标元素已包含媒体。 |
The indicated destination element already contains media. |
| 0x48A | 指出的元素不存在。 |
The indicated element does not exist. |
| 0x48B | 指出的元素是未显示的存储资源的一部分。 |
The indicated element is part of a magazine that is not present. |
| 0x48C | 由于硬件错误，显示设备需要重新初始化。 |
The indicated device requires reinitialization due to hardware errors. |
| 0x48D | 设备指示在尝试进一步操作之前需要清除。 |
The device has indicated that cleaning is required before further operations are attempted. |
| 0x48E | 设备指示门是打开的。 |
The device has indicated that its door is open. |
| 0x48F | 设备没有连接。 |
The device is not connected. |
| 0x490 | 找不到元素。 |
Element not found. |
| 0x491 | 索引中没有同指定项相匹配的项。 |
There was no match for the specified key in the index. |
| 0x492 | 在对象上不存在指定的属性集。 |
The property set specified does not exist on the object. |
| 0x493 | 传递到 GetMouseMovePoints 的点不在缓冲区中。 |
The point passed to GetMouseMovePoints is not in the buffer. |
| 0x494 | 跟踪(工作站)服务没有运行。 |
The tracking (workstation) service is not running. |
| 0x495 | 找不到卷 ID。 |
The Volume ID could not be found. |
| 0x497 | 无法删除要被替换的文件。 |
Unable to remove the file to be replaced. |
| 0x498 | 无法将替换文件移到要被替换的文件。要被替换的文件保持原始名称。 |
Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name. |
| 0x499 | 无法将替换文件移到要被替换的文件。要被替换的文件已被重新命名为备份名称。 |
Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name. |
| 0x49A | 正在删除卷更改日志。 |
The volume change journal is being deleted. |
| 0x49B | 卷更改日志处于非活动状态。 |
The volume change journal is not active. |
| 0x49C | 找到一份文件，但是可能不是正确的文件。 |
A file was found, but it may not be the correct file. |
| 0x49D | 日志项已从日志中被删除。 |
The journal entry has been deleted from the journal. |
| 0x49F | CFG 启用时，无法设置驱动程序验证程序易失性设置。 |
Driver Verifier Volatile settings cannot be set when CFG is enabled. |
| 0x4A6 | 已经计划系统关机。 |
A system shutdown has already been scheduled. |
| 0x4A7 | 无法启动系统关机，因为有其他用户登录到计算机。 |
The system shutdown cannot be initiated because there are other users logged on to the computer. |
| 0x4B0 | 指定的设备名无效。 |
The specified device name is invalid. |
| 0x4B1 | 设备当前未连接上，但其为一个记录连接。 |
The device is not currently connected but it is a remembered connection. |
| 0x4B2 | 本地设备名称已有到另一网络资源的记录连接。 |
The local device name has a remembered connection to another network resource. |
| 0x4B3 | 网络路径键入不正确、不存在或者网络提供程序当前不可用。请尝试重新键入路径或者与网络管理员联系。 |
The 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. |
| 0x4B4 | 指定的网络提供程序名称无效。 |
The specified network provider name is invalid. |
| 0x4B5 | 无法打开网络连接配置文件。 |
Unable to open the network connection profile. |
| 0x4B6 | 网络连接配置文件损坏。 |
The network connection profile is corrupted. |
| 0x4B7 | 无法枚举空载体。 |
Cannot enumerate a noncontainer. |
| 0x4B8 | 出现了扩展错误。 |
An extended error has occurred. |
| 0x4B9 | 指定的组名格式无效。 |
The format of the specified group name is invalid. |
| 0x4BA | 指定的计算机名格式无效。 |
The format of the specified computer name is invalid. |
| 0x4BB | 指定的事件名格式无效。 |
The format of the specified event name is invalid. |
| 0x4BC | 指定的域名格式无效。 |
The format of the specified domain name is invalid. |
| 0x4BD | 指定的服务名格式无效。 |
The format of the specified service name is invalid. |
| 0x4BE | 指定的网络名格式无效。 |
The format of the specified network name is invalid. |
| 0x4BF | 指定的共享名格式无效。 |
The format of the specified share name is invalid. |
| 0x4C0 | 指定的密码格式无效。 |
The format of the specified password is invalid. |
| 0x4C1 | 指定的消息名格式无效。 |
The format of the specified message name is invalid. |
| 0x4C2 | 指定的消息目标格式无效。 |
The format of the specified message destination is invalid. |
| 0x4C3 | 不允许一个用户使用一个以上用户名与服务器或共享资源的多重连接。中断与此服务器或共享资源的所有连接，然后再试一次。 |
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. |
| 0x4C4 | 试图与网络服务器建立会话，但目前与该服务器建立的会话太多。 |
An attempt was made to establish a session to a network server, but there are already too many sessions established to that server. |
| 0x4C5 | 工作组或域名已由网络上的另一部计算机使用。 |
The workgroup or domain name is already in use by another computer on the network. |
| 0x4C6 | 网络不存在或尚未启动。 |
The network is not present or not started. |
| 0x4C7 | 操作已被用户取消。 |
The operation was canceled by the user. |
| 0x4C8 | 请求的操作无法在使用用户映射区域打开的文件上执行。 |
The requested operation cannot be performed on a file with a user-mapped section open. |
| 0x4C9 | 远程计算机拒绝网络连接。 |
The remote computer refused the network connection. |
| 0x4CA | 网络连接已被适当地关闭了。 |
The network connection was gracefully closed. |
| 0x4CB | 网络传输终结点已有与其关联的地址。 |
The network transport endpoint already has an address associated with it. |
| 0x4CC | 地址仍未与网络终结点关联。 |
An address has not yet been associated with the network endpoint. |
| 0x4CD | 企图在不存在的网络连接上进行操作。 |
An operation was attempted on a nonexistent network connection. |
| 0x4CE | 企图在使用中的网络连接上进行无效的操作。 |
An invalid operation was attempted on an active network connection. |
| 0x4CF | 不能访问网络位置。有关网络排除故障的信息，请参阅 Windows 帮助。 |
The network location cannot be reached. For information about network troubleshooting, see Windows Help. |
| 0x4D2 | 没有任何服务正在远程系统上的目标网络终结点上操作。 |
No service is operating at the destination network endpoint on the remote system. |
| 0x4D3 | 请求被中止。 |
The request was aborted. |
| 0x4D4 | 由本地系统中止网络连接。 |
The network connection was aborted by the local system. |
| 0x4D5 | 操作无法完成。应该重试。 |
The operation could not be completed. A retry should be performed. |
| 0x4D6 | 因为已达到此帐户的最大同时连接数限制，所以无法连接服务器。 |
A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached. |
| 0x4D7 | 试图在这个帐户未被授权的时间内登录。 |
Attempting to log in during an unauthorized time of day for this account. |
| 0x4D8 | 此帐户并未得到从这个工作站登录的授权。 |
The account is not authorized to log in from this station. |
| 0x4D9 | 请求的操作不能使用这个网络地址。 |
The network address could not be used for the operation requested. |
| 0x4DA | 服务器已经注册。 |
The service is already registered. |
| 0x4DB | 指定的服务不存在。 |
The specified service does not exist. |
| 0x4DC | 因为用户还未通过身份验证，不能执行所要求的操作。 |
The operation being requested was not performed because the user has not been authenticated. |
| 0x4DD | 因为用户未登录到网络，因此未执行所要求的操作。指定的服务不存在。 |
The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. |
| 0x4DE | 正在继续工作。 |
Continue with work in progress. |
| 0x4DF | 试图进行初始操作，但是初始化已完成。 |
An attempt was made to perform an initialization operation when initialization has already been completed. |
| 0x4E0 | 没有更多的本地设备。 |
No more local devices. |
| 0x4E1 | 指定的站点不存在。 |
The specified site does not exist. |
| 0x4E2 | 具有指定名称的域控制器已经存在。 |
A domain controller with the specified name already exists. |
| 0x4E3 | 只有连接到服务器上时，该操作才受支持。 |
This operation is supported only when you are connected to the server. |
| 0x4E4 | 即使没有更改，组策略框架也应该调用扩展。 |
The group policy framework should call the extension even if there are no changes. |
| 0x4E5 | 指定的用户没有一个有效的配置文件。 |
The specified user does not have a valid profile. |
| 0x4E6 | 运行 Windows Server 2003 for Small Business Server 的计算机不支持此操作。 |
This operation is not supported on a computer running Windows Server 2003 for Small Business Server |
| 0x4E7 | 服务器正在关机。 |
The server machine is shutting down. |
| 0x4E8 | 远程系统不可用。有关网络疑难解答，请参阅 Windows 帮助。 |
The remote system is not available. For information about network troubleshooting, see Windows Help. |
| 0x4E9 | 提供的安全标识符不是来自一个帐户域。 |
The security identifier provided is not from an account domain. |
| 0x4EA | 提供的安全标识符没有域组件。 |
The security identifier provided does not have a domain component. |
| 0x4EB | 取消了 AppHelp 对话，导致应用程序无法启动。 |
AppHelp dialog canceled thus preventing the application from starting. |
| 0x4EC | 组策略阻止了这个程序。要获取详细信息，请与系统管理员联系。 |
This program is blocked by group policy. For more information, contact your system administrator. |
| 0x4ED | 一个程序企图用无效的注册值。通常由未初始化的注册表引起。此错误是 Itanium 特有的。 |
A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific. |
| 0x4EE | 该共享目前处于脱机状态，或者不存在。 |
The share is currently offline or does not exist. |
| 0x4EF | 在智能卡登录过程中，验证 KDC 证书时 kerberos 协议遇到错误。系统事件日志中包含详细信息。 |
The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log. |
| 0x4F0 | 尝试使用智能卡子系统时，Kerberos 协议遇到错误。 |
The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem. |
| 0x4F1 | 系统无法联系域控制器来为身份验证请求提供服务。请稍后再试。 |
The system cannot contact a domain controller to service the authentication request. Please try again later. |
| 0x4F7 | 计算机已经锁定而且不使用强制选项无法关机。 |
The machine is locked and cannot be shut down without the force option. |
| 0x4F8 | 你不能访问此共享文件夹，因为你组织的安全策略阻止未经身份验证的来宾访问。这些策略可帮助保护你的电脑免受网络上不安全设备或恶意设备的威胁。 |
You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network. |
| 0x4F9 | 当调用一个应用程序定义的回调时，出现无效数据错误。 |
An application-defined callback gave invalid data when called. |
| 0x4FA | 在同步前台策略刷新时，组策略框架应该调用扩展。 |
The group policy framework should call the extension in the synchronous foreground policy refresh. |
| 0x4FB | 此驱动程序被阻止加载 |
This driver has been blocked from loading |
| 0x4FC | 动态链接库(DLL)引用的模块不是 DLL 也不是过程可执行映像。 |
A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image. |
| 0x4FD | Windows 无法打开此程序因为它被禁用。 |
Windows cannot open this program since it has been disabled. |
| 0x4FE | Windows 无法打开此程序因为许可证强制系统已经被篡改或者损坏。 |
Windows cannot open this program because the license enforcement system has been tampered with or become corrupted. |
| 0x4FF | 事务处理恢复失败。 |
A transaction recover failed. |
| 0x500 | 当前线程已经转换到 fiber。 |
The current thread has already been converted to a fiber. |
| 0x501 | 当前线程已经从 fiber 转换。 |
The current thread has already been converted from a fiber. |
| 0x502 | 系统在此应用程序中检测到基于堆栈的缓冲区溢出。溢出可能允许恶意用户获得此应用程序的控制。 |
The 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. |
| 0x503 | 函数不能操作参数之一中的数据。 |
Data present in one of the parameters is more than the function can operate on. |
| 0x504 | 尝试调试对象的操作失败，因为对象正在被删除。 |
An attempt to do an operation on a debug object failed because the object is in the process of being deleted. |
| 0x505 | 未能延迟加载 .dll 或从延迟加载的 .dll 获得函数地址。 |
An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed. |
| 0x506 | %1 是一个 16 位应用程序。你没有权限执行 16 位应用程序。请与系统管理员检查你的权限。 |
%1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator. |
| 0x507 | 已有信息不足，无法识别故障的原因。 |
Insufficient information exists to identify the cause of failure. |
| 0x508 | 传递到 C 运行时函数的参数不正确。 |
The parameter passed to a C runtime function is incorrect. |
| 0x509 | 发生超出文件有效数据长度的操作。 |
The operation occurred beyond the valid data length of the file. |
| 0x50A | 由于同一进程中的一个或多个服务的服务 SID 类型设置不兼容，因此服务启动失败。具有受限服务 SID 类型的服务只能与具有受限 SID 类型的其他服务共存于同一进程中。如果刚刚配置该服务的服务 SID 类型，则必须重新启动承载进程，以便启动该服务。 |
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. |
| 0x50B | 承载该设备的驱动程序的进程已终止。 |
The process hosting the driver for this device has been terminated. |
| 0x50C | 尝试的操作超出实现定义的限制。 |
An operation attempted to exceed an implementation-defined limit. |
| 0x50D | 目标进程或目标线程的包含进程是受保护的进程。 |
Either the target process, or the target thread's containing process, is a protected process. |
| 0x50E | 服务通知客户端严重滞后于计算机中当前服务状态。 |
The service notification client is lagging too far behind the current state of services in the machine. |
| 0x50F | 请求的文件操作失败，因为超出存储配额。若要释放磁盘空间，请将文件移至其他位置或删除不必要的文件。有关详细信息，请与系统管理员联系。 |
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. |
| 0x510 | 请求的文件操作失败，因为存储策略阻止此类型文件。有关详细信息，请与系统管理员联系。 |
The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator. |
| 0x511 | 服务帐户配置中不存在服务正常运行所需的特权。你可以使用 Services Microsoft Management Console (MMC)管理单元(services.msc)和 Local Security Settings MMC 管理单元(secpol.msc)来查看服务配置和帐户配置。 |
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. |
| 0x512 | 在此操作中所涉及的线程看似没有响应。 |
A thread involved in this operation appears to be unresponsive. |
| 0x513 | 指明特定的安全 ID 可能不能作为对象的标签分配。 |
Indicates a particular Security ID may not be assigned as the label of an object. |
| 0x514 | 并非所有被引用的特权或组都分配给呼叫方。 |
Not all privileges or groups referenced are assigned to the caller. |
| 0x515 | 帐户名和安全 ID 间的某些映射未完成。 |
Some mapping between account names and security IDs was not done. |
| 0x516 | 没有为该帐户特别设置系统配额限制。 |
No system quota limits are specifically set for this account. |
| 0x517 | 没有可用的加密密钥。返回了一个已知加密密钥。 |
No encryption key is available. A well-known encryption key was returned. |
| 0x518 | 密码太复杂，无法转换成 LAN Manager 密码。返回的 LAN Manager 密码为空字符串。 |
The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string. |
| 0x519 | 修订级别未知。 |
The revision level is unknown. |
| 0x51A | 表明两个修订级别是不兼容的。 |
Indicates two revision levels are incompatible. |
| 0x51B | 这个安全 ID 不能分配为此对象的所有者。 |
This security ID may not be assigned as the owner of this object. |
| 0x51C | 这个安全 ID 不能分配为对象的主要组。 |
This security ID may not be assigned as the primary group of an object. |
| 0x51D | 目前未模仿客户端的线程试图在模仿令牌上操作。 |
An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client. |
| 0x51E | 组可能未被禁用。 |
The group may not be disabled. |
| 0x51F | 我们无法使用此凭据登录，因为你的域不可用。请确保你的设备已连接到你组织的网络，然后重试。如果你以前使用其他凭据登录到了此设备，则可以使用该凭据登录。 |
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. |
| 0x520 | 指定的登录会话不存在。可能已被终止。 |
A specified logon session does not exist. It may already have been terminated. |
| 0x521 | 指定的特权不存在。 |
A specified privilege does not exist. |
| 0x522 | 客户端没有所需的特权。 |
A required privilege is not held by the client. |
| 0x523 | 提供的名称不是正确格式的帐户名。 |
The name provided is not a properly formed account name. |
| 0x524 | 指定的帐户已存在。 |
The specified account already exists. |
| 0x525 | 指定的帐户不存在。 |
The specified account does not exist. |
| 0x526 | 指定的组已存在。 |
The specified group already exists. |
| 0x527 | 指定的组不存在。 |
The specified group does not exist. |
| 0x528 | 指定的用户帐户已是指定组的成员，或是因为组包含成员所以无法删除指定的组。 |
Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member. |
| 0x529 | 指定的用户帐户不是指定组帐户的成员。 |
The specified user account is not a member of the specified group account. |
| 0x52A | 不允许执行此操作，因为这可能会导致禁用或删除管理帐户，或者使管理帐户无法登录。 |
This operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon. |
| 0x52B | 无法更新密码。提供作为当前密码的值不正确。 |
Unable to update the password. The value provided as the current password is incorrect. |
| 0x52C | 无法更新密码。提供给新密码的值包含密码中不允许的值。 |
Unable to update the password. The value provided for the new password contains values that are not allowed in passwords. |
| 0x52D | 无法更新密码。为新密码提供的值不符合字符域的长度、复杂性或历史要求。 |
Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain. |
| 0x52E | 用户名或密码不正确。 |
The user name or password is incorrect. |
| 0x52F | 用户帐户限制阻止了此用户进行登录。例如：不允许使用空密码，登录次数的限制，或强制实施的某个策略限制。 |
Account 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. |
| 0x530 | 你帐户的时间限制使你无法立刻登录。 |
Your account has time restrictions that keep you from signing in right now. |
| 0x531 | 不允许此用户登录到这台计算机。 |
This user isn't allowed to sign in to this computer. |
| 0x532 | 此帐户的密码已过期。 |
The password for this account has expired. |
| 0x533 | 此用户无法登录，因为该帐户当前已被禁用。 |
This user can't sign in because this account is currently disabled. |
| 0x534 | 帐户名与安全标识间无任何映射完成。 |
No mapping between account names and security IDs was done. |
| 0x535 | 一次请求过多的本地用户标识符(LUIDs)。 |
Too many local user identifiers (LUIDs) were requested at one time. |
| 0x536 | 无更多可用的本地用户标识符(LUIDs)。 |
No more local user identifiers (LUIDs) are available. |
| 0x537 | 对于该特别用法，安全 ID 的次级授权部分无效。 |
The subauthority part of a security ID is invalid for this particular use. |
| 0x538 | 访问控制列表(ACL)结构无效。 |
The access control list (ACL) structure is invalid. |
| 0x539 | 安全 ID 结构无效。 |
The security ID structure is invalid. |
| 0x53A | 安全描述符结构无效。 |
The security descriptor structure is invalid. |
| 0x53C | 无法创建固有的访问控制列表(ACL)或访问控制项目(ACE)。 |
The inherited access control list (ACL) or access control entry (ACE) could not be built. |
| 0x53D | 服务器当前已禁用。 |
The server is currently disabled. |
| 0x53E | 服务器当前已启用。 |
The server is currently enabled. |
| 0x53F | 所提供的值是无效的标识符颁发机构的值。 |
The value provided was an invalid value for an identifier authority. |
| 0x540 | 无更多可用的内存以更新安全信息。 |
No more memory is available for security information updates. |
| 0x541 | 指定的特性无效，或不与组的特性兼容。 |
The specified attributes are invalid, or incompatible with the attributes for the group as a whole. |
| 0x542 | 未提供所需的模拟级别，或提供的模拟级别无效。 |
Either a required impersonation level was not provided, or the provided impersonation level is invalid. |
| 0x543 | 无法打开匿名级安全令牌。 |
Cannot open an anonymous level security token. |
| 0x544 | 请求的验证信息类无效。 |
The validation information class requested was invalid. |
| 0x545 | 令牌的类型对其尝试使用的方法不适当。 |
The type of the token is inappropriate for its attempted use. |
| 0x546 | 无法在与安全性无关联的对象上运行安全性操作。 |
Unable to perform a security operation on an object that has no associated security. |
| 0x547 | 无法从域控制器读取配置信息，因为计算机不可用，或者因为访问已被拒绝。 |
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. |
| 0x548 | 安全帐户管理器(SAM)或本地安全机构(LSA)服务器处于运行安全操作的错误状态。 |
The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation. |
| 0x549 | 域处于运行安全操作的错误状态。 |
The domain was in the wrong state to perform the security operation. |
| 0x54B | 指定的域不存在，或无法联系。 |
The specified domain either does not exist or could not be contacted. |
| 0x54C | 指定的域已存在。 |
The specified domain already exists. |
| 0x54D | 试图超出每服务器域个数的限制。 |
An attempt was made to exceed the limit on the number of domains per server. |
| 0x54E | 无法完成请求操作，因为磁盘上的严重媒体失败或数据结构损坏。 |
Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk. |
| 0x54F | 出现了内部错误。 |
An internal error occurred. |
| 0x550 | 通用访问类型包含于已映射到非通用类型的访问掩码中。 |
Generic access types were contained in an access mask which should already be mapped to nongeneric types. |
| 0x551 | 安全描述符格式不正确(绝对或自相关的)。 |
A security descriptor is not in the right format (absolute or self-relative). |
| 0x552 | 请求的操作只准登录过程使用。该调用过程并未被记录为登录过程。 |
The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process. |
| 0x553 | 无法使用已在使用中的标识启动新的会话。 |
Cannot start a new logon session with an ID that is already in use. |
| 0x554 | 指定的身份验证数据包未知。 |
A specified authentication package is unknown. |
| 0x555 | 登录会话并非处于与请求操作一致的状态中。 |
The logon session is not in a state that is consistent with the requested operation. |
| 0x556 | 登录会话标识已在使用中。 |
The logon session ID is already in use. |
| 0x557 | 登录请求包含无效的登录类型值。 |
A logon request contained an invalid logon type value. |
| 0x558 | 在使用命名管道读取数据之前，无法经由该管道模拟。 |
Unable to impersonate using a named pipe until data has been read from that pipe. |
| 0x559 | 注册表子树的事务处理状态与请求状态不一致。 |
The transaction state of a registry subtree is incompatible with the requested operation. |
| 0x55A | 安全性数据库内部出现损坏。 |
An internal security database corruption has been encountered. |
| 0x55B | 无法在内置帐户上运行此操作。 |
Cannot perform this operation on built-in accounts. |
| 0x55C | 无法在内置特殊组上运行此操作。 |
Cannot perform this operation on this built-in special group. |
| 0x55D | 无法在内置特殊用户上运行此操作。 |
Cannot perform this operation on this built-in special user. |
| 0x55E | 无法从组中删除用户，因为当前组为用户的主要组。 |
The user cannot be removed from a group because the group is currently the user's primary group. |
| 0x55F | 令牌已作为主要令牌使用。 |
The token is already in use as a primary token. |
| 0x560 | 指定的本地组不存在。 |
The specified local group does not exist. |
| 0x561 | 指定的帐户名不是此组的成员。 |
The specified account name is not a member of the group. |
| 0x562 | 指定的帐户名已是此组的成员。 |
The specified account name is already a member of the group. |
| 0x563 | 指定的本地组已存在。 |
The specified local group already exists. |
| 0x564 | 登录失败: 未授予用户在此计算机上的请求登录类型。 |
Logon failure: the user has not been granted the requested logon type at this computer. |
| 0x565 | 已超过在单一系统中可保存机密的最大个数。 |
The maximum number of secrets that may be stored in a single system has been exceeded. |
| 0x566 | 机密的长度超过允许的最大长度。 |
The length of a secret exceeds the maximum length allowed. |
| 0x567 | 本地安全机构数据库内部包含不一致性。 |
The local security authority database contains an internal inconsistency. |
| 0x568 | 在尝试登录的过程中，用户的安全上下文积累了过多的安全标识。 |
During a logon attempt, the user's security context accumulated too many security IDs. |
| 0x56A | 更改用户密码时需要交叉加密密码。 |
A cross-encrypted password is necessary to change a user password. |
| 0x56B | 该成员不存在，因此不能将其添加到本地组中或从本地组删除。 |
A member could not be added to or removed from the local group because the member does not exist. |
| 0x56C | 无法将新成员加入到本地组中，因为成员的帐户类型错误。 |
A new member could not be added to a local group because the member has the wrong account type. |
| 0x56D | 已指定过多的安全标识。 |
Too many security IDs have been specified. |
| 0x56E | 更改此用户密码时需要交叉加密密码。 |
A cross-encrypted password is necessary to change this user password. |
| 0x56F | 表明 ACL 未包含任何可承继的组件。 |
Indicates an ACL contains no inheritable components. |
| 0x570 | 文件或目录损坏且无法读取。 |
The file or directory is corrupted and unreadable. |
| 0x571 | 磁盘结构损坏且无法读取。 |
The disk structure is corrupted and unreadable. |
| 0x572 | 没有指定登录会话的用户会话密钥。 |
There is no user session key for the specified logon session. |
| 0x573 | 正在访问的服务受特定连接数目授权限制。此时无法对该服务进行更多数目的连接，原因是已达到该服务可接受的连接数目上限。 |
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. |
| 0x574 | 目标帐户名称不正确。 |
The target account name is incorrect. |
| 0x575 | 相互身份验证失败。该服务器在域控制器的密码过期。 |
Mutual Authentication failed. The server's password is out of date at the domain controller. |
| 0x576 | 在客户端和服务器之间存在时间和/或日期差。 |
There is a time and/or date difference between the client and server. |
| 0x577 | 无法在当前域上执行此操作。 |
This operation cannot be performed on the current domain. |
| 0x578 | 无效的窗口句柄。 |
Invalid window handle. |
| 0x579 | 无效的菜单句柄。 |
Invalid menu handle. |
| 0x57A | 无效的光标句柄。 |
Invalid cursor handle. |
| 0x57B | 无效的加速器表句柄。 |
Invalid accelerator table handle. |
| 0x57C | 无效的挂钩句柄。 |
Invalid hook handle. |
| 0x57D | 无效的多重窗口位置结构句柄。 |
Invalid handle to a multiple-window position structure. |
| 0x57E | 无法创建最上层子窗口。 |
Cannot create a top-level child window. |
| 0x57F | 找不到窗口类。 |
Cannot find window class. |
| 0x580 | 无效窗口；它属于另一线程。 |
Invalid window; it belongs to other thread. |
| 0x581 | 热键已注册。 |
Hot key is already registered. |
| 0x582 | 类已存在。 |
Class already exists. |
| 0x583 | 类不存在。 |
Class does not exist. |
| 0x584 | 类仍有打开的窗口。 |
Class still has open windows. |
| 0x585 | 无效索引。 |
Invalid index. |
| 0x586 | 无效的图标句柄。 |
Invalid icon handle. |
| 0x587 | 使用专用 DIALOG 窗口字词。 |
Using private DIALOG window words. |
| 0x588 | 找不到列表框标识符。 |
The list box identifier was not found. |
| 0x589 | 找不到通配字符。 |
No wildcards were found. |
| 0x58A | 线程没有打开的剪贴板。 |
Thread does not have a clipboard open. |
| 0x58B | 没有注册热键。 |
Hot key is not registered. |
| 0x58C | 窗口不是合法的对话窗口。 |
The window is not a valid dialog window. |
| 0x58D | 找不到控件 ID。 |
Control ID not found. |
| 0x58E | 因为没有编辑控制，所以组合框的消息无效。 |
Invalid message for a combo box because it does not have an edit control. |
| 0x58F | 窗口不是组合框。 |
The window is not a combo box. |
| 0x590 | 高度必须小于 256。 |
Height must be less than 256. |
| 0x591 | 无效的设备上下文(DC)句柄。 |
Invalid device context (DC) handle. |
| 0x592 | 无效的挂接程序类型。 |
Invalid hook procedure type. |
| 0x593 | 无效的挂接程序。 |
Invalid hook procedure. |
| 0x594 | 没有模块句柄无法设置非本机的挂接。 |
Cannot set nonlocal hook without a module handle. |
| 0x595 | 此挂接程序只可整体设置。 |
This hook procedure can only be set globally. |
| 0x596 | 日记挂接程序已安装。 |
The journal hook procedure is already installed. |
| 0x597 | 挂接程序尚未安装。 |
The hook procedure is not installed. |
| 0x598 | 单一选择列表框的无效消息。 |
Invalid message for single-selection list box. |
| 0x599 | LB_SETCOUNT 发送到非被动的列表框。 |
LB_SETCOUNT sent to non-lazy list box. |
| 0x59A | 此列表框不支持制表位。 |
This list box does not support tab stops. |
| 0x59B | 无法毁坏由另一个线程创建的对象。 |
Cannot destroy object created by another thread. |
| 0x59C | 子窗口没有菜单。 |
Child windows cannot have menus. |
| 0x59D | 窗口没有系统菜单。 |
The window does not have a system menu. |
| 0x59E | 无效的消息对话框样式。 |
Invalid message box style. |
| 0x59F | 无效的系统范围内的(SPI_*)参数。 |
Invalid system-wide (SPI_*) parameter. |
| 0x5A0 | 已锁定屏幕。 |
Screen already locked. |
| 0x5A1 | 多重窗口位置结构中窗口的所有句柄必须具有相同的上层。 |
All handles to windows in a multiple-window position structure must have the same parent. |
| 0x5A2 | 窗口不是子窗口。 |
The window is not a child window. |
| 0x5A3 | 无效的 GW_* 命令。 |
Invalid GW_* command. |
| 0x5A4 | 无效的线程标识符符。 |
Invalid thread identifier. |
| 0x5A5 | 无法处理非多重文档接口(MDI)窗口中的消息。 |
Cannot process a message from a window that is not a multiple document interface (MDI) window. |
| 0x5A6 | 弹出式菜单已经激活。 |
Popup menu already active. |
| 0x5A7 | 窗口没有滚动条。 |
The window does not have scroll bars. |
| 0x5A8 | 滚动条范围不可大于 MAXLONG。 |
Scroll bar range cannot be greater than MAXLONG. |
| 0x5A9 | 无法以指定的方式显示或删除窗口。 |
Cannot show or remove the window in the way specified. |
| 0x5AA | 系统资源不足，无法完成请求的服务。 |
Insufficient system resources exist to complete the requested service. |
| 0x5AD | 配额不足，无法完成请求的服务。 |
Insufficient quota to complete the requested service. |
| 0x5AF | 页面文件太小，无法完成操作。 |
The paging file is too small for this operation to complete. |
| 0x5B0 | 找不到菜单项。 |
A menu item was not found. |
| 0x5B1 | 键盘布局句柄无效。 |
Invalid keyboard layout handle. |
| 0x5B2 | 不允许使用挂钩类型。 |
Hook type not allowed. |
| 0x5B3 | 该操作需要交互式窗口工作站。 |
This operation requires an interactive window station. |
| 0x5B4 | 由于超时时间已过，该操作返回。 |
This operation returned because the timeout period expired. |
| 0x5B5 | 无效监视器句柄。 |
Invalid monitor handle. |
| 0x5B6 | 参数大小错误。 |
Incorrect size argument. |
| 0x5B7 | 无法遵循符号链接，因为其类型已禁用。 |
The symbolic link cannot be followed because its type is disabled. |
| 0x5B8 | 这个应用程序不支持在符号链接上执行当前操作。 |
This application does not support the current operation on symbolic links. |
| 0x5B9 | Windows 无法分析请求的 XML 数据。 |
Windows was unable to parse the requested XML data. |
| 0x5BA | 处理 XML 数字签名时出现错误。 |
An error was encountered while processing an XML digital signature. |
| 0x5BB | 此应用程序必须重新启动。 |
This application must be restarted. |
| 0x5BC | 呼叫方提出在错误路由分段中请求连接。 |
The caller made the connection request in the wrong routing compartment. |
| 0x5BD | 尝试连接到远程主机时，发生 AuthIP 故障。 |
There was an AuthIP failure when attempting to connect to the remote host. |
| 0x5BE | 没有足够的 NVRAM 资源，因此无法完成请求的服务。可能需要重新启动。 |
Insufficient NVRAM resources exist to complete the requested service. A reboot might be required. |
| 0x5BF | 无法完成请求的操作，因为指定的进程不是 GUI 进程。 |
Unable to finish the requested operation because the specified process is not a GUI process. |
| 0x5DC | 事件日志文件损坏。 |
The event log file is corrupted. |
| 0x5DD | 无法打开事件日志文件，事件日志服务没有启动。 |
No event log file could be opened, so the event logging service did not start. |
| 0x5DE | 事件日志文件已满。 |
The event log file is full. |
| 0x5DF | 事件日志文件已在读取间更改。 |
The event log file has changed between read operations. |
| 0x5E0 | 指定的作业已有为其分配的容器。 |
The specified Job already has a container assigned to it. |
| 0x5E1 | 指定的作业没有为其分配的容器。 |
The specified Job does not have a container assigned to it. |
| 0x60E | 指定的任务名称无效。 |
The specified task name is invalid. |
| 0x60F | 指定的任务索引无效。 |
The specified task index is invalid. |
| 0x610 | 指定的线程已加入任务。 |
The specified thread is already joining a task. |
| 0x641 | 无法访问 Windows Installer 服务。没有正确安装 Windows Installer 时可能发生这种情况。请与技术支持人员联系以获得帮助。 |
The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance. |
| 0x642 | 用户取消了安装。 |
User cancelled installation. |
| 0x643 | 安装时发生严重错误 |
Fatal error during installation. |
| 0x644 | 安装已暂停，未完成。 |
Installation suspended, incomplete. |
| 0x645 | 这个操作只对当前安装的产品有效。 |
This action is only valid for products that are currently installed. |
| 0x646 | 功能 ID 未注册。 |
Feature ID not registered. |
| 0x647 | 组件 ID 并未注册。 |
Component ID not registered. |
| 0x648 | 未知属性。 |
Unknown property. |
| 0x649 | 句柄处于不正确的状态。 |
Handle is in an invalid state. |
| 0x64A | 这个产品的配置数据已损坏。请与技术支持人员联系。 |
The configuration data for this product is corrupt. Contact your support personnel. |
| 0x64B | 组件限制语不存在。 |
Component qualifier not present. |
| 0x64C | 这个产品的安装来源无法使用。请验证来源是否存在，是否可以访问。 |
The installation source for this product is not available. Verify that the source exists and that you can access it. |
| 0x64D | Windows Installer 服务无法安装这个安装程序包。你必须安装含有 Windows Installer 服务更新版本的 Windows Service Pack。 |
This 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. |
| 0x64E | 没有卸载产品。 |
Product is uninstalled. |
| 0x64F | SQL 查询语法不正确或不被支持。 |
SQL query syntax invalid or unsupported. |
| 0x650 | 记录字符域不存在。 |
Record field does not exist. |
| 0x651 | 设备已被删除。 |
The device has been removed. |
| 0x652 | 正在进行另一个安装操作。请在继续这个安装操作之前完成那个操作。 |
Another installation is already in progress. Complete that installation before proceeding with this install. |
| 0x653 | 未能打开这个安装程序包。请验证程序包是否存在，是否可以访问；或者与应用程序供应商联系，验证这是否是有效的 Windows Installer 程序包。 |
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. |
| 0x654 | 未能打开这个安装程序包。请与应用程序供应商联系，验证这是否是有效的 Windows Installer 程序包。 |
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. |
| 0x655 | 启动 Windows Installer 服务用户界面时有错误。请与技术支持人员联系。 |
There was an error starting the Windows Installer service user interface. Contact your support personnel. |
| 0x656 | 打开安装日志文件的错误。请验证指定的日志文件位置是否存在，是否可以写入。 |
Error opening installation log file. Verify that the specified log file location exists and that you can write to it. |
| 0x657 | 安装程序包的语言不受系统支持。 |
The language of this installation package is not supported by your system. |
| 0x658 | 应用转换时的错误。请验证指定的转换路径是否有效。 |
Error applying transforms. Verify that the specified transform paths are valid. |
| 0x659 | 系统策略禁止这个安装。请与系统管理员联系。 |
This installation is forbidden by system policy. Contact your system administrator. |
| 0x65A | 无法执行函数。 |
Function could not be executed. |
| 0x65B | 执行期间，函数出了问题。 |
Function failed during execution. |
| 0x65C | 指定了无效的或未知的表格。 |
Invalid or unknown table specified. |
| 0x65D | 提供的数据类型不对。 |
Data supplied is of wrong type. |
| 0x65E | 这个类型的数据不受支持。 |
Data of this type is not supported. |
| 0x65F | Windows Installer 服务未能启动。请与你的技术支持人员联系。 |
The Windows Installer service failed to start. Contact your support personnel. |
| 0x660 | 驱动器上的临时文件夹已满或无法访问。请释放一些空间或验证你是否有写入临时文件夹的权限。 |
The 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. |
| 0x661 | 这个处理器类型不支持该安装程序包。请与产品供应商联系。 |
This installation package is not supported by this processor type. Contact your product vendor. |
| 0x662 | 组件没有在这台计算机上使用。 |
Component not used on this computer. |
| 0x663 | 无法打开更新程序包。请验证修更新程序包是否存在，是否可以访问；或者与应用程序供应商联系，验证这是否是 Windows Installer 的更新程序包。 |
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. |
| 0x664 | 无法打开更新程序包。请与应用程序供应商联系，验证这是否是 Windows Installer 的更新程序包。 |
This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package. |
| 0x665 | Windows Installer 服务无法处理这个更新程序包。你必须安装含有 Windows Installer 服务更新版本的 Windows Service Pack。 |
This 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. |
| 0x666 | 已安装这个产品的另一个版本。这个版本的安装无法继续。要配置或删除这个产品的现有版本，请用“控制面板”上的“添加/删除程序”。 |
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. |
| 0x667 | 无效的命令行参数。有关详细的命令行帮助，请查阅 Windows Installer 的 SDK。 |
Invalid command line argument. Consult the Windows Installer SDK for detailed command line help. |
| 0x668 | 在终端服务远程会话期间，只有管理员有添加、删除或配置服务器软件的权限。如果你想在服务器上安装或配置软件，请与网络管理员联系。 |
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. |
| 0x669 | 要求的操作已成功结束。要使更改生效，必须重新启动系统。 |
The requested operation completed successfully. The system will be restarted so the changes can take effect. |
| 0x66A | Windows Installer 服务无法安装升级更新程序，因为被升级的程序可能会丢失或是升级更新程序可能更新此程序的一个不同版本。请确认要被升级的程序在你的计算机上且你的升级更新程序是正确的。 |
The 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. |
| 0x66B | 软件限制策略不允许有更新程序包。 |
The update package is not permitted by software restriction policy. |
| 0x66C | 软件限制策略不允许一个或多个自定义项。 |
One or more customizations are not permitted by software restriction policy. |
| 0x66D | Windows Installer 不允许从远程桌面连接安装。 |
The Windows Installer does not permit installation from a Remote Desktop Connection. |
| 0x66E | 不支持卸载更新程序包。 |
Uninstallation of the update package is not supported. |
| 0x66F | 更新程序未应用到此产品。 |
The update is not applied to this product. |
| 0x670 | 找不到更新程序集的有效顺序。 |
No valid sequence could be found for the set of updates. |
| 0x671 | 策略禁用删除更新程序。 |
Update removal was disallowed by policy. |
| 0x672 | XML 更新程序数据无效。 |
The XML update data is invalid. |
| 0x673 | Windows Installer 不允许更新经过管理的播发产品。应用更新程序之前，必须至少安装产品的一个功能。 |
Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update. |
| 0x674 | 无法在安全模式下访问 Windows Installer 服务。请在计算机不处于安全模式时再次尝试，或者可以使用系统还原，使计算机返回到前一个良好状态。 |
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. |
| 0x675 | 发生快速异常检测失败。不会调用异常处理程序并且进程将立即终止。 |
A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. |
| 0x676 | 此版本的 Windows 上不支持尝试运行的应用。 |
The app that you are trying to run is not supported on this version of Windows. |
| 0x677 | 操作被阻止，因为进程禁止动态生成代码。 |
The operation was blocked as the process prohibits dynamic code generation. |
| 0x678 | 对象不同。 |
The objects are not identical. |
| 0x679 | 指定的映像文件被阻止加载，因为未启用进程所需的功能: 控制流防护。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard. |
| 0x67A | 指定的映像文件被阻止加载，因为未启用进程所需的功能: 返回流防护。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Return Flow Guard. |
| 0x67B | 发生了针对返回流防护受限区域的无效内存访问。 |
An invalid memory access occurred to a Return Flow Guard restricted region. |
| 0x67C | 无法更新线程会话，因为已限制对该进程执行此操作。 |
The thread context could not be updated because this has been restricted for the process. |
| 0x67D | 尝试进行的跨分区专用文件/节访问无效。 |
An invalid cross-partition private file/section access was attempted. |
| 0x6A4 | 字符串绑定无效。 |
The string binding is invalid. |
| 0x6A5 | 绑定句柄的类型不正确。 |
The binding handle is not the correct type. |
| 0x6A6 | 绑定句柄无效。 |
The binding handle is invalid. |
| 0x6A7 | 不支持 RPC 协议序列。 |
The RPC protocol sequence is not supported. |
| 0x6A8 | RPC 协议序列无效。 |
The RPC protocol sequence is invalid. |
| 0x6A9 | 字符串通用唯一标识符(UUID)无效。 |
The string universal unique identifier (UUID) is invalid. |
| 0x6AA | 终结点格式无效。 |
The endpoint format is invalid. |
| 0x6AB | 网络地址无效。 |
The network address is invalid. |
| 0x6AC | 找不到终结点。 |
No endpoint was found. |
| 0x6AD | 超时值无效。 |
The timeout value is invalid. |
| 0x6AE | 找不到对象通用唯一标识符(UUID)。 |
The object universal unique identifier (UUID) was not found. |
| 0x6AF | 对象通用唯一标识符(UUID)已注册。 |
The object universal unique identifier (UUID) has already been registered. |
| 0x6B0 | 类型通用唯一标识符(UUID)已注册。 |
The type universal unique identifier (UUID) has already been registered. |
| 0x6B1 | RPC 服务器已在侦听。 |
The RPC server is already listening. |
| 0x6B2 | 未登记任何协议序列。 |
No protocol sequences have been registered. |
| 0x6B3 | RPC 服务器未在侦听。 |
The RPC server is not listening. |
| 0x6B4 | 管理程序类型未知。 |
The manager type is unknown. |
| 0x6B5 | 接口未知。 |
The interface is unknown. |
| 0x6B6 | 没有绑定。 |
There are no bindings. |
| 0x6B7 | 没有协议序列。 |
There are no protocol sequences. |
| 0x6B8 | 无法创建终结点。 |
The endpoint cannot be created. |
| 0x6B9 | 资源不足，无法完成该操作。 |
Not enough resources are available to complete this operation. |
| 0x6BA | RPC 服务器不可用。 |
The RPC server is unavailable. |
| 0x6BB | RPC 服务器太忙，不能完成该操作。 |
The RPC server is too busy to complete this operation. |
| 0x6BC | 网络选项无效。 |
The network options are invalid. |
| 0x6BD | 该线程中没有远程过程调用活动。 |
There are no remote procedure calls active on this thread. |
| 0x6BE | 远程过程调用失败。 |
The remote procedure call failed. |
| 0x6BF | 远程过程调用失败且未执行。 |
The remote procedure call failed and did not execute. |
| 0x6C0 | 远程过程调用(RPC)协议出错。 |
A remote procedure call (RPC) protocol error occurred. |
| 0x6C1 | 拒绝访问 HTTP 代理。 |
Access to the HTTP proxy is denied. |
| 0x6C2 | RPC 服务器不支持传送语法。 |
The transfer syntax is not supported by the RPC server. |
| 0x6C4 | 不支持通用唯一标识符(UUID)类型。 |
The universal unique identifier (UUID) type is not supported. |
| 0x6C5 | 标记无效。 |
The tag is invalid. |
| 0x6C6 | 数组绑定无效。 |
The array bounds are invalid. |
| 0x6C7 | 绑定不包含登录项名字。 |
The binding does not contain an entry name. |
| 0x6C8 | 名称语法无效。 |
The name syntax is invalid. |
| 0x6C9 | 不支持该名称语法。 |
The name syntax is not supported. |
| 0x6CB | 没有可用来创建通用唯一标识符(UUID)的网络地址。 |
No network address is available to use to construct a universal unique identifier (UUID). |
| 0x6CC | 终结点重复。 |
The endpoint is a duplicate. |
| 0x6CD | 未知的身份验证类型。 |
The authentication type is unknown. |
| 0x6CE | 调用的最大个数太小。 |
The maximum number of calls is too small. |
| 0x6CF | 字符串太长。 |
The string is too long. |
| 0x6D0 | 找不到 RPC 协议顺序。 |
The RPC protocol sequence was not found. |
| 0x6D1 | 过程号超出范围。 |
The procedure number is out of range. |
| 0x6D2 | 绑定不包含任何身份验证信息。 |
The binding does not contain any authentication information. |
| 0x6D3 | 未知的身份验证服务。 |
The authentication service is unknown. |
| 0x6D4 | 未知的身份验证级别。 |
The authentication level is unknown. |
| 0x6D5 | 安全上下文无效。 |
The security context is invalid. |
| 0x6D6 | 未知的授权服务。 |
The authorization service is unknown. |
| 0x6D7 | 项目无效。 |
The entry is invalid. |
| 0x6D8 | 服务器终结点无法运行操作。 |
The server endpoint cannot perform the operation. |
| 0x6D9 | 终结点映射器中没有更多的终结点可用。 |
There are no more endpoints available from the endpoint mapper. |
| 0x6DA | 未导出任何接口。 |
No interfaces have been exported. |
| 0x6DB | 项目名不完整。 |
The entry name is incomplete. |
| 0x6DC | 版本选项无效。 |
The version option is invalid. |
| 0x6DD | 没有其他成员。 |
There are no more members. |
| 0x6DE | 没有内容未导出。 |
There is nothing to unexport. |
| 0x6DF | 找不到接口。 |
The interface was not found. |
| 0x6E0 | 项目已存在。 |
The entry already exists. |
| 0x6E1 | 找不到项目。 |
The entry is not found. |
| 0x6E2 | 名称服务不可用。 |
The name service is unavailable. |
| 0x6E3 | 网络地址族无效。 |
The network address family is invalid. |
| 0x6E4 | 不支持请求的操作。 |
The requested operation is not supported. |
| 0x6E5 | 没有安全上下文可用来允许模仿。 |
No security context is available to allow impersonation. |
| 0x6E6 | 远程过程调用(RPC)中发生内部错误。 |
An internal error occurred in a remote procedure call (RPC). |
| 0x6E7 | RPC 服务器试图以零除整数。 |
The RPC server attempted an integer division by zero. |
| 0x6E8 | RPC 服务器出现寻址错误。 |
An addressing error occurred in the RPC server. |
| 0x6E9 | RPC 服务器上的浮点操作导至以零做除数。 |
A floating-point operation at the RPC server caused a division by zero. |
| 0x6EA | RPC 服务器上发生浮点下溢。 |
A floating-point underflow occurred at the RPC server. |
| 0x6EB | RPC 服务器上发生浮点溢出。 |
A floating-point overflow occurred at the RPC server. |
| 0x6EC | 自动句柄绑定的可用 RPC 服务器列表已用完。 |
The list of RPC servers available for the binding of auto handles has been exhausted. |
| 0x6ED | 无法打开字符翻译表文件。 |
Unable to open the character translation table file. |
| 0x6EE | 包含字符转换表的文件小于 512 字节。 |
The file containing the character translation table has fewer than 512 bytes. |
| 0x6EF | 在远程过程调用时，将空的上下文句柄从客户端传递到主机。 |
A null context handle was passed from the client to the host during a remote procedure call. |
| 0x6F1 | 在远程过程调用时，上下文句柄已更改。 |
The context handle changed during a remote procedure call. |
| 0x6F2 | 传送给远程过程调用的绑定句柄不匹配。 |
The binding handles passed to a remote procedure call do not match. |
| 0x6F3 | 承接体无法获得远程过程调用句柄。 |
The stub is unable to get the remote procedure call handle. |
| 0x6F4 | 向占位程序传送了空的索引指针。 |
A null reference pointer was passed to the stub. |
| 0x6F5 | 枚举值越界。 |
The enumeration value is out of range. |
| 0x6F6 | 字节计数太小。 |
The byte count is too small. |
| 0x6F7 | 占位程序接收到错误数据。 |
The stub received bad data. |
| 0x6F8 | 提供给请求操作的用户缓冲区无效。 |
The supplied user buffer is not valid for the requested operation. |
| 0x6F9 | 磁盘媒体无法识别。可能未被格式化。 |
The disk media is not recognized. It may not be formatted. |
| 0x6FA | 工作站没有信任机密。 |
The workstation does not have a trust secret. |
| 0x6FB | 服务器上的安全数据库没有此工作站信任关系的计算机帐户。 |
The security database on the server does not have a computer account for this workstation trust relationship. |
| 0x6FC | 主域和受信域间的信任关系失败。 |
The trust relationship between the primary domain and the trusted domain failed. |
| 0x6FD | 此工作站和主域间的信任关系失败。 |
The trust relationship between this workstation and the primary domain failed. |
| 0x6FE | 网络登录失败。 |
The network logon failed. |
| 0x6FF | 此线程的远程过程调用已在进行中。 |
A remote procedure call is already in progress for this thread. |
| 0x700 | 试图登录，但是网络登录服务没有启动。 |
An attempt was made to logon, but the network logon service was not started. |
| 0x701 | 用户帐户已过期。 |
The user's account has expired. |
| 0x702 | 重定向程序正使用中，不能卸装。 |
The redirector is in use and cannot be unloaded. |
| 0x703 | 指定的打印机驱动程序已安装。 |
The specified printer driver is already installed. |
| 0x704 | 指定的端口未知。 |
The specified port is unknown. |
| 0x705 | 未知的打印机驱动程序。 |
The printer driver is unknown. |
| 0x706 | 未知的打印处理器。 |
The print processor is unknown. |
| 0x707 | 指定的分隔页文件无效。 |
The specified separator file is invalid. |
| 0x708 | 指定的优先级无效。 |
The specified priority is invalid. |
| 0x709 | 打印机名无效。 |
The printer name is invalid. |
| 0x70A | 打印机已存在。 |
The printer already exists. |
| 0x70B | 打印机命令无效。 |
The printer command is invalid. |
| 0x70C | 指定的数据类型无效。 |
The specified datatype is invalid. |
| 0x70D | 指定的环境无效。 |
The environment specified is invalid. |
| 0x70E | 没有更多的绑定。 |
There are no more bindings. |
| 0x70F | 所用帐户为域间信任帐户。请使用你的全局用户帐户或本地用户帐户来访问这台服务器。 |
The account used is an interdomain trust account. Use your global user account or local user account to access this server. |
| 0x710 | 所用帐户是一个计算机帐户。使用你的全局用户帐户或本地用户帐户来访问此服务器。 |
The account used is a computer account. Use your global user account or local user account to access this server. |
| 0x711 | 已使用的帐户为服务器信任帐户。使用你的全局用户帐户或本地用户帐户来访问此服务器。 |
The account used is a server trust account. Use your global user account or local user account to access this server. |
| 0x712 | 指定域的名称或安全 ID (SID)与该域的信任信息不一致。 |
The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain. |
| 0x713 | 服务器在使用中且无法卸载。 |
The server is in use and cannot be unloaded. |
| 0x714 | 指定的映像文件不包含资源区域。 |
The specified image file did not contain a resource section. |
| 0x715 | 找不到映像文件中指定的资源类型。 |
The specified resource type cannot be found in the image file. |
| 0x716 | 找不到映像文件中指定的资源名。 |
The specified resource name cannot be found in the image file. |
| 0x717 | 找不到映像文件中指定的资源语言标识。 |
The specified resource language ID cannot be found in the image file. |
| 0x718 | 配额不足，无法处理此命令。 |
Not enough quota is available to process this command. |
| 0x719 | 未登记任何接口。 |
No interfaces have been registered. |
| 0x71A | 远程过程调用被取消。 |
The remote procedure call was cancelled. |
| 0x71B | 绑定句柄不包含所有需要的信息。 |
The binding handle does not contain all required information. |
| 0x71C | 在远程过程调用过程中通信失败。 |
A communications failure occurred during a remote procedure call. |
| 0x71D | 请求的身份验证级别不被支持。 |
The requested authentication level is not supported. |
| 0x71E | 未登记任何主名称。 |
No principal name registered. |
| 0x71F | 指定的错误不是有效的 Windows RPC 错误代码。 |
The error specified is not a valid Windows RPC error code. |
| 0x720 | 已经分配只在这台计算机上有效的 UUID。 |
A UUID that is valid only on this computer has been allocated. |
| 0x721 | 出现了特定的安全程序包错误。 |
A security package specific error occurred. |
| 0x722 | 线程未取消。 |
Thread is not canceled. |
| 0x723 | 无效的编码/解码句柄操作。 |
Invalid operation on the encoding/decoding handle. |
| 0x724 | 系列软件包的不兼容版本。 |
Incompatible version of the serializing package. |
| 0x725 | RPC 占位程序的不兼容版本。 |
Incompatible version of the RPC stub. |
| 0x726 | RPC 管道对象无效或已损坏。 |
The RPC pipe object is invalid or corrupted. |
| 0x727 | 试图在 RPC 管道对象上进行无效操作。 |
An invalid operation was attempted on an RPC pipe object. |
| 0x728 | 不支持该版本的 RPC 管道。 |
Unsupported RPC pipe version. |
| 0x729 | HTTP 代理服务器拒绝连接，因为 cookie 身份验证失败。 |
HTTP proxy server rejected the connection because the cookie authentication failed. |
| 0x72A | RPC 服务器已暂停，无法继续执行此请求。未执行调用。 |
The RPC server is suspended, and could not be resumed for this request. The call did not execute. |
| 0x72B | RPC 调用包含过多的句柄，无法通过单个请求传输。 |
The RPC call contains too many handles to be transmitted in a single request. |
| 0x72C | RPC 调用包含的某个句柄不同于声明的句柄类型。 |
The RPC call contains a handle that differs from the declared handle type. |
| 0x76A | 找不到该组成员。 |
The group member was not found. |
| 0x76B | 无法创建终结点映射表数据库项。 |
The endpoint mapper database entry could not be created. |
| 0x76C | 对象通用唯一标识符(UUID)为 nil UUID。 |
The object universal unique identifier (UUID) is the nil UUID. |
| 0x76D | 指定的时间无效。 |
The specified time is invalid. |
| 0x76E | 指定的格式名称无效。 |
The specified form name is invalid. |
| 0x76F | 指定的格式大小无效。 |
The specified form size is invalid. |
| 0x770 | 指定的打印机句柄正等候在 |
The specified printer handle is already being waited on |
| 0x771 | 已删除指定的打印机。 |
The specified printer has been deleted. |
| 0x772 | 打印机的状态无效。 |
The state of the printer is invalid. |
| 0x773 | 在登录之前，必须更改用户的密码。 |
The user's password must be changed before signing in. |
| 0x774 | 找不到此域的域控制器。 |
Could not find the domain controller for this domain. |
| 0x775 | 引用的帐户当前已锁定，且可能无法登录。 |
The referenced account is currently locked out and may not be logged on to. |
| 0x776 | 找不到指定的对象导出程序 |
The object exporter specified was not found. |
| 0x777 | 找不到指定的对象。 |
The object specified was not found. |
| 0x778 | 找不到指定的对象解析程序。 |
The object resolver set specified was not found. |
| 0x779 | 一些待发数据仍停留在请求缓冲区内。 |
Some data remains to be sent in the request buffer. |
| 0x77A | 无效的异步远程过程调用句柄。 |
Invalid asynchronous remote procedure call handle. |
| 0x77B | 这个操作的异步 RPC 调用句柄无效。 |
Invalid asynchronous RPC call handle for this operation. |
| 0x77C | RPC 管道对象已经关闭。 |
The RPC pipe object has already been closed. |
| 0x77D | 在 RPC 调用完成之前全部的管道都已处理完成。 |
The RPC call completed before all pipes were processed. |
| 0x77E | 没有其他可用的数据来自 RPC 管道。 |
No more data is available from the RPC pipe. |
| 0x77F | 这台计算机没有可用的站点名。 |
No site name is available for this machine. |
| 0x780 | 系统无法访问此文件。 |
The file cannot be accessed by the system. |
| 0x781 | 系统无法辨识文件名。 |
The name of the file cannot be resolved by the system. |
| 0x782 | 项目不是所要的类型。 |
The entry is not of the expected type. |
| 0x783 | 无法将所有对象的 UUID 导出到指定的项。 |
Not all object UUIDs could be exported to the specified entry. |
| 0x784 | 无法将接口导出到指定的项。 |
Interface could not be exported to the specified entry. |
| 0x785 | 无法添加指定的配置文件项。 |
The specified profile entry could not be added. |
| 0x786 | 无法添加指定的配置文件元素。 |
The specified profile element could not be added. |
| 0x787 | 无法删除指定的配置文件元素。 |
The specified profile element could not be removed. |
| 0x788 | 无法添加组元素。 |
The group element could not be added. |
| 0x789 | 无法删除组元素。 |
The group element could not be removed. |
| 0x78A | 打印机驱动程序与你计算机上启用的阻止 NT 4.0 驱动程序的策略不兼容。 |
The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers. |
| 0x78B | 上下文已过期，不能再用了。 |
The context has expired and can no longer be used. |
| 0x78C | 已经超过当前用户的委派信任创建限额。 |
The current user's delegated trust creation quota has been exceeded. |
| 0x78D | 已经超过委派信任创建限额的总数。 |
The total delegated trust creation quota has been exceeded. |
| 0x78E | 已经超过当前用户的委派信任删除限额。 |
The current user's delegated trust deletion quota has been exceeded. |
| 0x78F | 你正在登录的计算机受到身份验证防火墙的保护。不允许指定的帐户通过此计算机的身份验证。 |
The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer. |
| 0x790 | 到此后台打印程序的远程连接被你计算机上的策略集阻止。 |
Remote connections to the Print Spooler are blocked by a policy set on your machine. |
| 0x791 | 身份验证失败，原因是已禁用 NTLM 身份验证。 |
Authentication failed because NTLM authentication has been disabled. |
| 0x792 | 登录失败: EAS 策略要求用户先更改其密码，然后才能执行此操作。 |
Logon Failure: EAS policy requires that the user change their password before this operation can be performed. |
| 0x793 | 管理员已限制登录。若要登录，请确保设备已连接到 Internet，并让管理员先登录。 |
An administrator has restricted sign in. To sign in, make sure your device is connected to the Internet, and have your administrator sign in first. |
| 0x7D0 | 无效的像素格式。 |
The pixel format is invalid. |
| 0x7D1 | 指定的驱动程序无效。 |
The specified driver is invalid. |
| 0x7D2 | 窗口样式或类属性对此操作无效。 |
The window style or class attribute is invalid for this operation. |
| 0x7D3 | 不支持请求的图元操作。 |
The requested metafile operation is not supported. |
| 0x7D4 | 不支持请求的转换操作。 |
The requested transformation operation is not supported. |
| 0x7D5 | 不支持请求的剪裁操作。 |
The requested clipping operation is not supported. |
| 0x7DA | 指定的颜色管理模块无效。 |
The specified color management module is invalid. |
| 0x7DB | 制定的颜色配置文件无效。 |
The specified color profile is invalid. |
| 0x7DC | 找不到指定的标记。 |
The specified tag was not found. |
| 0x7DD | 找不到所需的标记。 |
A required tag is not present. |
| 0x7DE | 指定的标记已经存在。 |
The specified tag is already present. |
| 0x7DF | 指定的颜色配置文件与指定设备不相关。 |
The specified color profile is not associated with the specified device. |
| 0x7E0 | 找不到该指定的颜色配置文件 |
The specified color profile was not found. |
| 0x7E1 | 指定的颜色空间无效。 |
The specified color space is invalid. |
| 0x7E2 | 图像颜色管理没有启动。 |
Image Color Management is not enabled. |
| 0x7E3 | 在删除该颜色传输时有一个错误。 |
There was an error while deleting the color transform. |
| 0x7E4 | 该指定的颜色传输无效。 |
The specified color transform is invalid. |
| 0x7E5 | 该指定的转换与位图的颜色空间不匹配。 |
The specified transform does not match the bitmap's color space. |
| 0x7E6 | 该指定的命名颜色索引在配置文件中不存在。 |
The specified named color index is not present in the profile. |
| 0x7E7 | 指定的配置文件预期用于与指定设备的类型不同的设备。 |
The specified profile is intended for a device of a different type than the specified device. |
| 0x83C | 网络连接已成功，但需要提示用户输入一个不同于原始指定的密码。 |
The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified. |
| 0x83D | 使用默认凭据成功连接网络。 |
The network connection was made successfully using default credentials. |
| 0x89A | 指定的用户名无效。 |
The specified username is invalid. |
| 0x8CA | 此网络连接不存在。 |
This network connection does not exist. |
| 0x961 | 此网络连接有文件打开或请求挂起。 |
This network connection has files open or requests pending. |
| 0x962 | 活动连接仍存在。 |
Active connections still exist. |
| 0x964 | 设备正由活动进程使用，无法断开连接。 |
The device is in use by an active process and cannot be disconnected. |
| 0xBB8 | 指定了未知的打印监视器。 |
The specified print monitor is unknown. |
| 0xBB9 | 指定的打印机驱动程序当前正在使用。 |
The specified printer driver is currently in use. |
| 0xBBA | 找不到缓冲文件。 |
The spool file was not found. |
| 0xBBB | 未发送 StartDocPrinter 调用。 |
A StartDocPrinter call was not issued. |
| 0xBBC | 未发送 AddJob 调用。 |
An AddJob call was not issued. |
| 0xBBD | 指定的打印处理器已经安装。 |
The specified print processor has already been installed. |
| 0xBBE | 指定的打印监视器已经安装。 |
The specified print monitor has already been installed. |
| 0xBBF | 该指定的打印监视器不具备所要求的功能。 |
The specified print monitor does not have the required functions. |
| 0xBC0 | 该指定的打印监视器正在使用中。 |
The specified print monitor is currently in use. |
| 0xBC1 | 当打印机有作业排队时此操作请求是不允许的。 |
The requested operation is not allowed when there are jobs queued to the printer. |
| 0xBC2 | 请求的操作成功。直到重新启动系统前更改将不会生效。 |
The requested operation is successful. Changes will not be effective until the system is rebooted. |
| 0xBC3 | 请求的操作成功。直到重新启动服务前更改将不会生效。 |
The requested operation is successful. Changes will not be effective until the service is restarted. |
| 0xBC4 | 找不到打印机。 |
No printers were found. |
| 0xBC5 | 已知打印机驱动程序不可靠。 |
The printer driver is known to be unreliable. |
| 0xBC6 | 已知打印机驱动程序会伤害系统。 |
The printer driver is known to harm the system. |
| 0xBC7 | 指定的打印机驱动程序包当前正在使用中。 |
The specified printer driver package is currently in use. |
| 0xBC8 | 无法找到打印机驱动程序包要求的核心驱动程序包。 |
Unable to find a core driver package that is required by the printer driver package. |
| 0xBC9 | 请求的操作失败。需要重新启动系统才能回退所做的更改。 |
The requested operation failed. A system reboot is required to roll back changes made. |
| 0xBCA | 请求的操作失败。已开始重新启动系统以回退所做的更改。 |
The requested operation failed. A system reboot has been initiated to roll back changes made. |
| 0xBCB | 在系统上找不到指定的打印机驱动程序，需要下载该驱动程序。 |
The specified printer driver was not found on the system and needs to be downloaded. |
| 0xBCC | 未能打印请求的打印作业。打印系统更新要求重新提交该作业。 |
The requested print job has failed to print. A print system update requires the job to be resubmitted. |
| 0xBCD | 打印机驱动程序不包含有效的清单或者包含过多的清单。 |
The printer driver does not contain a valid manifest, or contains too many manifests. |
| 0xBCE | 无法共享指定的打印机。 |
The specified printer cannot be shared. |
| 0xBEA | 操作已经暂停。 |
The operation was paused. |
| 0xF6E | 将给定操作作为缓存 IO 操作重新发出 |
Reissue the given operation as a cached IO operation |
| 0xFA0 | WINS 在处理命令时遇到错误。 |
WINS encountered an error while processing the command. |
| 0xFA1 | 本地的 WINS 不能删除。 |
The local WINS cannot be deleted. |
| 0xFA2 | 文件导入操作失败。 |
The importation from the file failed. |
| 0xFA3 | 备份操作失败。是否先前已作过完整备份? |
The backup failed. Was a full backup done before? |
| 0xFA4 | 备份操作失败。请检查你备份数据库的目录。 |
The backup failed. Check the directory to which you are backing the database. |
| 0xFA5 | WINS 数据库中没有这个名称。 |
The name does not exist in the WINS database. |
| 0xFA6 | 不允许复制一个尚未配置的伙伴。 |
Replication with a nonconfigured partner is not allowed. |
| 0xFD2 | 提供的内容信息版本不受支持。 |
The version of the supplied content information is not supported. |
| 0xFD3 | 提供的内容信息格式错误。 |
The supplied content information is malformed. |
| 0xFD4 | 在本地缓存或对等缓存中找不到请求的数据。 |
The requested data cannot be found in local or peer caches. |
| 0xFD5 | 没有提供或不需要更多数据。 |
No more data is available or required. |
| 0xFD6 | 提供的对象尚未初始化。 |
The supplied object has not been initialized. |
| 0xFD7 | 提供的对象已经初始化。 |
The supplied object has already been initialized. |
| 0xFD8 | 关机操作正在执行。 |
A shutdown operation is already in progress. |
| 0xFD9 | 提供的对象已经无效。 |
The supplied object has already been invalidated. |
| 0xFDA | 元素已经存在，并且未被替换。 |
An element already exists and was not replaced. |
| 0xFDB | 由于请求的操作已经完成，故无法取消。 |
Can not cancel the requested operation as it has already been completed. |
| 0xFDC | 由于请求的操作已经完成，故无法执行。 |
Can not perform the reqested operation because it has already been carried out. |
| 0xFDD | 操作访问的数据超出有效数据的范围。 |
An operation accessed data beyond the bounds of valid data. |
| 0xFDE | 请求的版本不受支持。 |
The requested version is not supported. |
| 0xFDF | 配置值无效。 |
A configuration value is invalid. |
| 0xFE0 | SKU 未获得许可。 |
The SKU is not licensed. |
| 0xFE1 | PeerDist 服务仍在初始化，稍后方可使用。 |
PeerDist Service is still initializing and will be available shortly. |
| 0xFE2 | 由于最新出现的错误，与一台或多台计算机的通信将暂时被阻止。 |
Communication with one or more computers will be temporarily blocked due to recent errors. |
| 0x1004 | DHCP 客户端获得一个在网络上已被使用的 IP 地址。直到 DHCP 客户端可以获得新的地址前，本地接口将被禁用。 |
The 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. |
| 0x1068 | 无法识别传来的 GUID 是否为有效的 WMI 数据提供程序。 |
The GUID passed was not recognized as valid by a WMI data provider. |
| 0x1069 | 无法识别传来的实例名是否为有效的 WMI 数据提供程序。 |
The instance name passed was not recognized as valid by a WMI data provider. |
| 0x106A | 无法识别传来的数据项目标识符是否为有效的 WMI 数据提供程序。 |
The data item ID passed was not recognized as valid by a WMI data provider. |
| 0x106B | 无法完成 WMI 请求，应该重试一次。 |
The WMI request could not be completed and should be retried. |
| 0x106C | 找不到 WMI 数据提供程序。 |
The WMI data provider could not be located. |
| 0x106D | WMI 数据提供程序引用到一个未注册的实例组。 |
The WMI data provider references an instance set that has not been registered. |
| 0x106E | WMI 数据块或事件通知已启用。 |
The WMI data block or event notification has already been enabled. |
| 0x106F | WMI 数据块不再可用。 |
The WMI data block is no longer available. |
| 0x1070 | WMI 数据服务无法使用。 |
The WMI data service is not available. |
| 0x1071 | WMI 数据提供程序无法完成要求。 |
The WMI data provider failed to carry out the request. |
| 0x1072 | WMI MOF 信息无效。 |
The WMI MOF information is not valid. |
| 0x1073 | WMI 注册信息无效。 |
The WMI registration information is not valid. |
| 0x1074 | WMI 数据块或事件通知已禁用。 |
The WMI data block or event notification has already been disabled. |
| 0x1075 | WMI 数据项目或数据块为只读。 |
The WMI data item or data block is read only. |
| 0x1076 | 不能更改 WMI 数据项目或数据块。 |
The WMI data item or data block could not be changed. |
| 0x109A | 此操作仅在应用容器上下文中有效。 |
This operation is only valid in the context of an app container. |
| 0x109B | 此应用程序只能在应用容器上下文中运行。 |
This application can only run in the context of an app container. |
| 0x109C | 在应用容器上下文中不支持此功能。 |
This functionality is not supported in the context of an app container. |
| 0x109D | 提供的 SID 长度对应用容器 SID 无效。 |
The length of the SID supplied is not a valid length for app container SIDs. |
| 0x10CC | 媒体标识符没有表示一个有效的媒体。 |
The media identifier does not represent a valid medium. |
| 0x10CD | 库标识符没有表示一个有效的库。 |
The library identifier does not represent a valid library. |
| 0x10CE | 媒体缓冲池标识符没有表示一个有效的媒体缓冲池。 |
The media pool identifier does not represent a valid media pool. |
| 0x10CF | 驱动器和媒体不兼容或位于不同的库中。 |
The drive and medium are not compatible or exist in different libraries. |
| 0x10D0 | 媒体目前在脱机库中，你必须联机才能运行这个操作。 |
The medium currently exists in an offline library and must be online to perform this operation. |
| 0x10D1 | 操作无法在脱机库中运行。 |
The operation cannot be performed on an offline library. |
| 0x10D2 | 库、驱动器或媒体缓冲池是空的。 |
The library, drive, or media pool is empty. |
| 0x10D3 | 库、驱动器或媒体缓冲池必须是空的，才能运行这个操作。 |
The library, drive, or media pool must be empty to perform this operation. |
| 0x10D4 | 在这个媒体缓冲池或库中目前没有可用的媒体。 |
No media is currently available in this media pool or library. |
| 0x10D5 | 这个操作所需的资源已禁用。 |
A resource required for this operation is disabled. |
| 0x10D6 | 媒体标识符没有表示一个有效的清洗器。 |
The media identifier does not represent a valid cleaner. |
| 0x10D7 | 无法清洗驱动器或不支持清洗。 |
The drive cannot be cleaned or does not support cleaning. |
| 0x10D8 | 对象标识符没有表示一个有效的对象。 |
The object identifier does not represent a valid object. |
| 0x10D9 | 无法读取或写入数据库。 |
Unable to read from or write to the database. |
| 0x10DA | 数据库已满。 |
The database is full. |
| 0x10DB | 媒体与设备或媒体缓冲池不兼容。 |
The medium is not compatible with the device or media pool. |
| 0x10DC | 这个操作所需的资源不存在。 |
The resource required for this operation does not exist. |
| 0x10DD | 操作标识符不正确。 |
The operation identifier is not valid. |
| 0x10DE | 媒体未被安装，或未就绪。 |
The media is not mounted or ready for use. |
| 0x10E0 | 操作员或系统管理员拒绝了请求。 |
The operator or administrator has refused the request. |
| 0x10E1 | 驱动器标识符不代表一个有效的驱动器。 |
The drive identifier does not represent a valid drive. |
| 0x10E2 | 程序库已满。没有可使用的插槽。 |
Library is full. No slot is available for use. |
| 0x10E3 | 传输程序不能访问媒体。 |
The transport cannot access the medium. |
| 0x10E4 | 无法将媒体加载到驱动器中。 |
Unable to load the medium into the drive. |
| 0x10E5 | 无法检索有关驱动器的状态。 |
Unable to retrieve the drive status. |
| 0x10E6 | 无法检索有关插槽的状态。 |
Unable to retrieve the slot status. |
| 0x10E7 | 无法检索传输的状态。 |
Unable to retrieve status about the transport. |
| 0x10E8 | 因为传输已在使用中，所以无法使用。 |
Cannot use the transport because it is already in use. |
| 0x10E9 | 无法打开或关闭弹入/弹出端口。 |
Unable to open or close the inject/eject port. |
| 0x10EA | 因为媒体在驱动器中，无法将其弹出。 |
Unable to eject the medium because it is in a drive. |
| 0x10EB | 清洗器插槽已被保留。 |
A cleaner slot is already reserved. |
| 0x10EC | 没有保留清洗器插槽。 |
A cleaner slot is not reserved. |
| 0x10ED | 清洗器墨盒已进行了最大次数的驱动器清洗。 |
The cleaner cartridge has performed the maximum number of drive cleanings. |
| 0x10EE | 意外媒体标识符。 |
Unexpected on-medium identifier. |
| 0x10EF | 在这个组或资源中最后剩下的项目不能被删除。 |
The last remaining item in this group or resource cannot be deleted. |
| 0x10F0 | 提供的消息超过了这个参数所允许的最大尺寸。 |
The message provided exceeds the maximum size allowed for this parameter. |
| 0x10F1 | 该卷含有系统和分页文件。 |
The volume contains system or paging files. |
| 0x10F2 | 由于库中至少有一个驱动器可以支持该媒体类型，不能从库中删除媒体类型。 |
The media type cannot be removed from this library since at least one drive in the library reports it can support this media type. |
| 0x10F3 | 由于没有可以使用的已被启动的驱动器，无法将该脱机媒体装入这个系统。 |
This offline media cannot be mounted on this system since no enabled drives are present which can be used. |
| 0x10F4 | 清洗磁带在磁带库中。 |
A cleaner cartridge is present in the tape library. |
| 0x10F5 | 不能使用插入/弹出端口，因为它不是空的。 |
Cannot use the inject/eject port because it is not empty. |
| 0x10FE | 该文件当前不能用于此计算机。 |
This file is currently not available for use on this computer. |
| 0x10FF | 远程存储服务此时不可操作。 |
The remote storage service is not operational at this time. |
| 0x1100 | 远程存储服务遇到一个媒体错误。 |
The remote storage service encountered a media error. |
| 0x1126 | 此文件或目录不是一个重分析点。 |
The file or directory is not a reparse point. |
| 0x1127 | 重分析点的属性不能被设置，因为它与已有的属性冲突。 |
The reparse point attribute cannot be set because it conflicts with an existing attribute. |
| 0x1128 | 在重分析点缓冲区中的数据无效。 |
The data present in the reparse point buffer is invalid. |
| 0x1129 | 在重分析点缓冲区中的标记无效。 |
The tag present in the reparse point buffer is invalid. |
| 0x112A | 请求中指定的标记与重分析点中存在的标记不匹配。 |
There is a mismatch between the tag specified in the request and the tag present in the reparse point. |
| 0x112B | 对象管理器在检索对象时遇到重分析点。 |
The object manager encountered a reparse point while retrieving an object. |
| 0x1130 | 找不到快速缓存数据。 |
Fast Cache data not found. |
| 0x1131 | 快速缓存数据已过期。 |
Fast Cache data expired. |
| 0x1132 | 快速缓存数据损坏。 |
Fast Cache data corrupt. |
| 0x1133 | 快速缓存数据已经超出其最大大小，无法更新。 |
Fast Cache data has exceeded its max size and cannot be updated. |
| 0x1134 | 快速缓存已重置，需要重新启动，然后才能更新。 |
Fast Cache has been ReArmed and requires a reboot until it can be updated. |
| 0x1144 | 安全引导检测到已尝试进行保护数据回退操作。 |
Secure Boot detected that rollback of protected data has been attempted. |
| 0x1145 | 该值受安全引导策略保护，无法进行修改或删除。 |
The value is protected by Secure Boot policy and cannot be modified or deleted. |
| 0x1146 | 安全引导策略无效。 |
The Secure Boot policy is invalid. |
| 0x1147 | 新的安全引导策略在其更新列表中不包含当前发布者。 |
A new Secure Boot policy did not contain the current publisher on its update list. |
| 0x1148 | 安全引导策略未签名或被不可信的签名者签名。 |
The Secure Boot policy is either not signed or is signed by a non-trusted signer. |
| 0x1149 | 此计算机上未启用安全启动。 |
Secure Boot is not enabled on this machine. |
| 0x114A | 安全启动要求某些文件和驱动程序不可被其他文件或驱动程序替换。 |
Secure Boot requires that certain files and drivers are not replaced by other files or drivers. |
| 0x114B | 未授权在此计算机上使用安全启动补充策略文件。 |
The Secure Boot Supplemental Policy file was not authorized on this machine. |
| 0x114C | 在此设备上无法识别补充策略。 |
The Supplemntal Policy is not recognized on this device. |
| 0x114D | 未在安全启动策略中找到防回退版本。 |
The Antirollback version was not found in the Secure Boot Policy. |
| 0x114E | 安全启动策略中指定的平台 ID 与此设备上的平台 ID 不匹配。 |
The Platform ID specified in the Secure Boot policy does not match the Platform ID on this device. |
| 0x114F | 安全启动策略文件的防回退版本比此设备的旧。 |
The Secure Boot policy file has an older Antirollback Version than this device. |
| 0x1150 | 安全启动策略文件与已升级的旧策略不匹配。 |
The Secure Boot policy file does not match the upgraded legacy policy. |
| 0x1151 | 安全引导策略文件是必需的，但找不到。 |
The Secure Boot policy file is required but could not be found. |
| 0x1152 | 补充安全引导策略文件无法作为基本安全引导策略加载。 |
Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy. |
| 0x1153 | 基本安全引导策略文件无法作为补充安全引导策略加载。 |
Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy. |
| 0x1158 | 副本卸载读取操作不受筛选器支持。 |
The copy offload read operation is not supported by a filter. |
| 0x1159 | 副本卸载写入操作不受筛选器支持。 |
The copy offload write operation is not supported by a filter. |
| 0x115A | 不支持对该文件进行副本卸载读取操作。 |
The copy offload read operation is not supported for the file. |
| 0x115B | 不支持对该文件进行副本卸载写入操作。 |
The copy offload write operation is not supported for the file. |
| 0x115C | 此文件当前与一个不同的流 ID 关联。 |
This file is currently associated with a different stream id. |
| 0x1194 | 零备份存储在这个卷上不可用。 |
Single Instance Storage is not available on this volume. |
| 0x11C6 | 系统完整性检测到已尝试策略回退。 |
System Integrity detected that policy rollback has been attempted. |
| 0x11C7 | 你的组织已使用 Device Guard 阻止此应用。有关详细信息，请联系支持人员。 |
Your organization used Device Guard to block this app. Contact your support person for more info. |
| 0x11C8 | 系统完整性策略无效。 |
The System Integrity policy is invalid. |
| 0x11C9 | 系统完整性策略未签名或由不受信任的签名人签名。 |
The System Integrity policy is either not signed or is signed by a non-trusted signer. |
| 0x11D0 | 虚拟安全模式(VSM)未初始化。虚拟机监控程序或 VSM 可能不存在或未启用。 |
Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. |
| 0x11D1 | 由于 IOMMU 不存在或未在 BIOS 中启用，虚拟机监控程序未在保护 DMA。 |
The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS. |
| 0x11DA | 未授权在此计算机上使用该平台清单文件。 |
The Platform Manifest file was not authorized on this machine. |
| 0x11DB | 该平台清单文件无效。 |
The Platform Manifest file was not valid. |
| 0x11DC | 该文件在此平台上未获得授权，因为在平台清单中未找到相应条目。 |
The file is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0x11DD | 该目录在此平台上未获得授权，因为在平台清单中未找到相应条目。 |
The catalog is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0x11DE | 该文件在此平台上未获得授权，因为在嵌入签名中未找到相应的二进制 ID。 |
The file is not authorized on this platform because a Binary ID was not found in the embedded signature. |
| 0x11DF | 此系统上不存在有效的平台清单。 |
No active Platform Manifest exists on this system. |
| 0x11E0 | 该平台清单文件未正确签名。 |
The Platform Manifest file was not properly signed. |
| 0x1389 | 操作无法完成，因为其他资源依赖于此资源。 |
The operation cannot be completed because other resources are dependent on this resource. |
| 0x138A | 找不到此群集资源的依赖。 |
The cluster resource dependency cannot be found. |
| 0x138B | 因为已经处于依赖状态，此群集资源不能依赖于指定的资源。 |
The cluster resource cannot be made dependent on the specified resource because it is already dependent. |
| 0x138C | 此群集资源未联机。 |
The cluster resource is not online. |
| 0x138D | 此操作没有可用的群集节点。 |
A cluster node is not available for this operation. |
| 0x138E | 没有群集资源。 |
The cluster resource is not available. |
| 0x138F | 找不到群集资源。 |
The cluster resource could not be found. |
| 0x1390 | 正在关闭群集。 |
The cluster is being shut down. |
| 0x1391 | 除非节点处于关闭状态或是最后一个节点，群集节点无法从群集中脱离。 |
A cluster node cannot be evicted from the cluster unless the node is down or it is the last node. |
| 0x1392 | 对象已存在。 |
The object already exists. |
| 0x1393 | 此对象已在列表中。 |
The object is already in the list. |
| 0x1394 | 新请求没有可用的群集组。 |
The cluster group is not available for any new requests. |
| 0x1395 | 找不到群集组。 |
The cluster group could not be found. |
| 0x1396 | 因为群集组未联机，此操作不能完成。 |
The operation could not be completed because the cluster group is not online. |
| 0x1397 | 由于指定群集节点不是资源的所有者，或者节点不是资源的可能所有者，因此该操作失败。 |
The 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. |
| 0x1398 | 由于指定群集节点不是组的所有者，或者节点不是组的可能所有者，因此该操作失败。 |
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. |
| 0x1399 | 群集资源不能在指定的资源监视器中创建。 |
The cluster resource could not be created in the specified resource monitor. |
| 0x139A | 群集资源不能通过资源监视器来联机。 |
The cluster resource could not be brought online by the resource monitor. |
| 0x139B | 因为群集资源联机，此操作不能完成。 |
The operation could not be completed because the cluster resource is online. |
| 0x139C | 由于是仲裁资源，群集资源不能被删除或脱机。 |
The cluster resource could not be deleted or brought offline because it is the quorum resource. |
| 0x139D | 由于没有能力成为仲裁资源，此群集不能使指定资源成为仲裁资源。 |
The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource. |
| 0x139E | 群集软件正关闭。 |
The cluster software is shutting down. |
| 0x139F | 组或资源的状态不是执行请求操作的正确状态。 |
The group or resource is not in the correct state to perform the requested operation. |
| 0x13A0 | 属性已被存储，但在下次资源联机前，不是所有的更改生效。 |
The properties were stored but not all changes will take effect until the next time the resource is brought online. |
| 0x13A1 | 由于不属于共享存储类，群集不能使指定资源成为仲裁资源。 |
The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class. |
| 0x13A2 | 由于是内核资源，无法删除群集资源。 |
The cluster resource could not be deleted since it is a core resource. |
| 0x13A3 | 仲裁资源联机失败。 |
The quorum resource failed to come online. |
| 0x13A4 | 无法成功创建或装入仲裁日志。 |
The quorum log could not be created or mounted successfully. |
| 0x13A5 | 群集日志损坏。 |
The cluster log is corrupt. |
| 0x13A6 | 由于该日志已超出最大限量，无法将记录写入群集日志。 |
The record could not be written to the cluster log since it exceeds the maximum size. |
| 0x13A7 | 群集日志已超出最大限量。 |
The cluster log exceeds its maximum size. |
| 0x13A8 | 群集日志找不到检查点记录。 |
No checkpoint record was found in the cluster log. |
| 0x13A9 | 不满足日志所需的最小磁盘空间。 |
The minimum required disk space needed for logging is not available. |
| 0x13AA | 群集节点未能控制仲裁资源，因为它被另一个活动节点拥有。 |
The cluster node failed to take control of the quorum resource because the resource is owned by another active node. |
| 0x13AB | 这个操作的群集网络无效。 |
A cluster network is not available for this operation. |
| 0x13AD | 所有群集节点都必须运行才能执行这个操作。 |
All cluster nodes must be running to perform this operation. |
| 0x13AE | 群集资源失败。 |
A cluster resource failed. |
| 0x13AF | 该群集节点无效。 |
The cluster node is not valid. |
| 0x13B0 | 该群集节点已经存在。 |
The cluster node already exists. |
| 0x13B1 | 一个节点正在加入该群集。 |
A node is in the process of joining the cluster. |
| 0x13B2 | 找不到群集节点。 |
The cluster node was not found. |
| 0x13B3 | 找不到群集本地节点信息。 |
The cluster local node information was not found. |
| 0x13B4 | 群集网络已经存在。 |
The cluster network already exists. |
| 0x13B5 | 找不到群集网络。 |
The cluster network was not found. |
| 0x13B6 | 群集网络接口已经存在。 |
The cluster network interface already exists. |
| 0x13B7 | 找不到群集网络接口。 |
The cluster network interface was not found. |
| 0x13B8 | 群集请求在这个对象中无效。 |
The cluster request is not valid for this object. |
| 0x13B9 | 群集网络提供程序无效。 |
The cluster network provider is not valid. |
| 0x13BA | 群集节点坏了。 |
The cluster node is down. |
| 0x13BB | 无法连接到群集节点。 |
The cluster node is not reachable. |
| 0x13BC | 该群集节点不是群集的一个成员。 |
The cluster node is not a member of the cluster. |
| 0x13BD | 目前没有执行群集加入操作。 |
A cluster join operation is not in progress. |
| 0x13BE | 该群集网络无效。 |
The cluster network is not valid. |
| 0x13C0 | 该群集节点可以使用。 |
The cluster node is up. |
| 0x13C1 | 该群集 IP 地址已在使用中。 |
The cluster IP address is already in use. |
| 0x13C2 | 该群集节点没有中止。 |
The cluster node is not paused. |
| 0x13C3 | 没有有效的群集安全上下文。 |
No cluster security context is available. |
| 0x13C4 | 该群集网络不是为内部群集通信配置的。 |
The cluster network is not configured for internal cluster communication. |
| 0x13C5 | 群集节点已经开始。 |
The cluster node is already up. |
| 0x13C6 | 群集节点已经坏了。 |
The cluster node is already down. |
| 0x13C7 | 群集网络已经联机。 |
The cluster network is already online. |
| 0x13C8 | 群集网络已经脱机。 |
The cluster network is already offline. |
| 0x13C9 | 群集节点已经是该群集的成员。 |
The cluster node is already a member of the cluster. |
| 0x13CA | 该群集网络是为两个或更多活动群集节点进行内部群集通信的唯一配置。不能从网络上删除内部通信功能。 |
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. |
| 0x13CB | 一个或更多的群集资源依靠网络来向客户端提供服务。不能从网络上删除客户端访问功能。 |
One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network. |
| 0x13CC | 当前无法对包含仲裁资源的群集组执行此操作。 |
This operation cannot currently be performed on the cluster group containing the quorum resource. |
| 0x13CD | 该群集仲裁资源不允许有任何依赖关系。 |
The cluster quorum resource is not allowed to have any dependencies. |
| 0x13CE | 该群集节点暂停。 |
The cluster node is paused. |
| 0x13CF | 群集资源不能联机。所有者节点不能在这个资源上运行。 |
The cluster resource cannot be brought online. The owner node cannot run this resource. |
| 0x13D0 | 群集节点没有准备好，不能执行所请求的操作。 |
The cluster node is not ready to perform the requested operation. |
| 0x13D1 | 群集节点正在关闭。 |
The cluster node is shutting down. |
| 0x13D2 | 中止群集节点加入操作。 |
The cluster join operation was aborted. |
| 0x13D3 | 由于要加入的节点及群集中的其他节点具有不兼容的操作系统版本，节点无法加入群集。若要获取有关群集的操作系统版本的详细信息，请运行验证配置向导或 Test-Cluster Windows PowerShell cmdlet。 |
The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet. |
| 0x13D4 | 由于该群集已经到达其所能监督的资源限制，不能创建这个资源。 |
This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor. |
| 0x13D5 | 系统配置在群集加入或形成操作时已更改。中止加入或形成操作。 |
The system configuration changed during the cluster join or form operation. The join or form operation was aborted. |
| 0x13D6 | 找不到指定的资源类型。 |
The specified resource type was not found. |
| 0x13D7 | 指定的节点不支持这类资源，这也许是由于版本不一致或是由于在这个节点上没有资源 DLL。 |
The 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. |
| 0x13D8 | 该资源 DLL 不支持指定的资源名称。这可能是由于一个提供给源 DLL 名称是错误的(或经过更改的)。 |
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. |
| 0x13D9 | 不能在 RPC 服务器上注册任何身份验证数据包。 |
No authentication package could be registered with the RPC server. |
| 0x13DA | 由于组的所有者不在组的首选列表中，不能将组联机。要更改组的所有者节点，请移动组。 |
You 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. |
| 0x13DB | 群集数据库的系列号已更改，或者与锁定程序节点不相容，因此加入操作没有成功。如果在加入操作期间群集数据库有任何更改，这都可能发生。 |
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. |
| 0x13DC | 资源在其当前状态下，资源监视器不允许执行失败操作。资源处于挂起状态时，这都可能发生。 |
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. |
| 0x13DD | 非锁定程序代码收到一个为全局更新保留锁定的请求。 |
A non locker code got a request to reserve the lock for making global updates. |
| 0x13DE | 群集服务找不到仲裁磁盘。 |
The quorum disk could not be located by the cluster service. |
| 0x13DF | 已备份的群集数据库可能已损坏。 |
The backed up cluster database is possibly corrupt. |
| 0x13E0 | DFS 根目录已在这个群集节点中。 |
A DFS root already exists in this cluster node. |
| 0x13E1 | 由于与另一个现有属性冲突，未能修改资源属性。 |
An attempt to modify a resource property failed because it conflicts with another existing property. |
| 0x13E2 | 此操作在没有管理员访问点的群集上不受支持。 |
This operation is not supported on a cluster without an Administrator Access Point. |
| 0x1702 | 尝试的操作与该节点当前成员身份状态不兼容。 |
An operation was attempted that is incompatible with the current membership state of the node. |
| 0x1703 | 仲裁资源不含仲裁日志。 |
The quorum resource does not contain the quorum log. |
| 0x1704 | 成员身份引擎申请关闭该节点上的群集服务。 |
The membership engine requested shutdown of the cluster service on this node. |
| 0x1705 | 加入操作失败，因为要加入的节点的群集实例 ID 与监护人节点上的群集实例 ID 不匹配。 |
The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node. |
| 0x1706 | 找不到指定的 IP 地址的匹配群集网络。 |
A matching cluster network for the specified IP address could not be found. |
| 0x1707 | 此属性的实际数据类型与它预期的数据类型的不匹配。 |
The actual data type of the property did not match the expected data type of the property. |
| 0x1708 | 已成功从群集移出群集节点，但是该节点没有被清除。要确定失败的清除步骤以及恢复方法，请使用事件查看器查看故障转移群集应用程序的事件日志。 |
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. |
| 0x1709 | 为资源属性指定的两个或更多参数值有冲突。 |
Two or more parameter values specified for a resource's properties are in conflict. |
| 0x170A | 此计算机无法成为群集成员。 |
This computer cannot be made a member of a cluster. |
| 0x170B | 因为此计算机没有安装 Windows 的正确版本，它不能成为一个群集的成员。 |
This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed. |
| 0x170C | 无法创建指定群集名称的群集，该群集名称已经使用。请指定其他群集名称。 |
A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster. |
| 0x170D | 群集配置操作已经执行。 |
The cluster configuration action has already been committed. |
| 0x170E | 群集配置操作不能还原。 |
The cluster configuration action could not be rolled back. |
| 0x170F | 某一节点上分配给系统磁盘的驱动器号与另一节点上分配给磁盘的驱动器号冲突。 |
The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node. |
| 0x1710 | 群集中的一个或多个节点正在运行不支持此操作的 Windows 版本。 |
One or more nodes in the cluster are running a version of Windows that does not support this operation. |
| 0x1711 | 相关计算机帐户的名称与此资源的网络名不匹配。 |
The name of the corresponding computer account doesn't match the Network Name for this resource. |
| 0x1712 | 没有可用的网络适配器。 |
No network adapters are available. |
| 0x1713 | 群集节点已中毒。 |
The cluster node has been poisoned. |
| 0x1714 | 由于该组正移动到其他节点，因此无法接受请求。 |
The group is unable to accept the request since it is moving to another node. |
| 0x1715 | 由于资源类型正忙于执行其他操作，因此无法接受请求。 |
The resource type cannot accept the request since is too busy performing another operation. |
| 0x1716 | 调用群集资源 DLL 超时。 |
The call to the cluster resource DLL timed out. |
| 0x1717 | 该地址对 IPv6 地址资源无效。需要一个全局 IPv6 地址，并且该地址必须与一个群集网络匹配。不允许使用兼容性地址。 |
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. |
| 0x1718 | 发生内部群集错误。尝试调用了无效的函数。 |
An internal cluster error occurred. A call to an invalid function was attempted. |
| 0x1719 | 参数值超出了可接受的范围。 |
A parameter value is out of acceptable range. |
| 0x171A | 发送数据到群集中其他节点时出现网络错误。传输的字节数目少于要求的数目。 |
A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required. |
| 0x171B | 尝试了无效的群集注册表操作。 |
An invalid cluster registry operation was attempted. |
| 0x171C | 输入字符串未正确终止。 |
An input string of characters is not properly terminated. |
| 0x171D | 对于其代表的数据，输入的字符串的格式无效。 |
An input string of characters is not in a valid format for the data it represents. |
| 0x171E | 出现内部群集错误。当某个事务正在进行时尝试了群集数据库事务。 |
An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress. |
| 0x171F | 出现内部群集错误。在没有事务进行时尝试了提交群集数据库事务。 |
An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress. |
| 0x1720 | 出现内部群集错误。数据未正确初始化。 |
An internal cluster error occurred. Data was not properly initialized. |
| 0x1721 | 从数据流进行读取时出错。返回了与预期字节数不符的字节数。 |
An error occurred while reading from a stream of data. An unexpected number of bytes was returned. |
| 0x1722 | 写入数据流时出错。无法写入要求的字节数。 |
An error occurred while writing to a stream of data. The required number of bytes could not be written. |
| 0x1723 | 对群集数据流进行反序列化时出错。 |
An error occurred while deserializing a stream of cluster data. |
| 0x1724 | 该资源的一个或多个属性值与和其相关资源关联的一个或多个属性值冲突。 |
One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s). |
| 0x1725 | 群集节点的仲裁不存在，无法形成群集。 |
A quorum of cluster nodes was not present to form a cluster. |
| 0x1726 | 该群集网络对 IPv6 地址资源无效，或它与已配置的地址不匹配。 |
The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address. |
| 0x1727 | 该群集网络对 IPv6 隧道资源无效。请检查该 IPv6 隧道资源依赖的 IP 地址资源的配置。 |
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. |
| 0x1728 | 仲裁资源无法位于可用存储组中。 |
Quorum resource cannot reside in the Available Storage group. |
| 0x1729 | 该资源的依赖关系嵌套过深。 |
The dependencies for this resource are nested too deeply. |
| 0x172A | 对该资源 DLL 的调用引发了一种未经处理的例外。 |
The call into the resource DLL raised an unhandled exception. |
| 0x172B | RHS 进程未能初始化。 |
The RHS process failed to initialize. |
| 0x172C | 此节点上未安装故障转移群集功能。 |
The Failover Clustering feature is not installed on this node. |
| 0x172D | 这些资源必须联机位于执行此操作的相同节点上 |
The resources must be online on the same node for this operation |
| 0x172E | 无法添加新节点，因为该群集已达到其最大的节点数。 |
A new node can not be added since this cluster is already at its maximum number of nodes. |
| 0x172F | 无法创建该群集，因为指定的节点数超过了允许的最大限制。 |
This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit. |
| 0x1730 | 尝试使用指定的群集名称失败，因为域中已存在具有给定名称的已启用计算机对象。 |
An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain. |
| 0x1731 | 该群集无法销毁。它具有无核心应用程序组，必须在销毁组之前将其删除。 |
This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed. |
| 0x1732 | 与文件共享见证资源相关的文件共享无法由该群集或其任意节点承载。 |
File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes. |
| 0x1733 | 此时逐出该节点无效。根据仲裁要求，逐出节点将导致群集关闭。如果它是群集中的最后一个节点，则应使用 destroy cluster 命令。 |
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. |
| 0x1734 | 群集中只允许有该资源类型的一个实例。 |
Only one instance of this resource type is allowed in the cluster. |
| 0x1735 | 每个资源组中只允许有一个该资源类型的实例。 |
Only one instance of this resource type is allowed per resource group. |
| 0x1736 | 由于一个或多个提供程序资源失败，资源无法联机。 |
The resource failed to come online due to the failure of one or more provider resources. |
| 0x1737 | 资源已经表明它无法联机到任何节点上。 |
The resource has indicated that it cannot come online on any node. |
| 0x1738 | 此时不能对此组执行当前操作。 |
The current operation cannot be performed on this group at this time. |
| 0x1739 | 目录或文件未位于群集共享卷上。 |
The directory or file is not located on a cluster shared volume. |
| 0x173A | 安全描述符不符合群集的要求。 |
The Security Descriptor does not meet the requirements for a cluster. |
| 0x173B | 群集中配置了一个或多个共享卷资源。若要使操作成功，必须将这些资源移动到可用的存储中。 |
There 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. |
| 0x173C | 无法直接操纵该组或资源。使用共享卷 API 执行所需的操作。 |
This group or resource cannot be directly manipulated.Use shared volume APIs to perform desired operation. |
| 0x173D | 备份正在执行。请等待备份完成，然后再重试此操作。 |
Back up is in progress. Please wait for backup completion before trying this operation again. |
| 0x173E | 该路径不属于群集共享卷。 |
The path does not belong to a cluster shared volume. |
| 0x173F | 未在该节点上本地装入群集共享卷。 |
The cluster shared volume is not locally mounted on this node. |
| 0x1740 | 正在终止群集监视器。 |
The cluster watchdog is terminating. |
| 0x1741 | 资源拒绝在两个节点之间移动，原因是它们不兼容。 |
A resource vetoed a move between two nodes because they are incompatible. |
| 0x1742 | 请求无效，原因是群集处于仅磁盘仲裁模式时无法更改节点权重，或者更改节点权重将违反群集仲裁最低要求。 |
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. |
| 0x1743 | 资源拒绝调用。 |
The resource vetoed the call. |
| 0x1744 | 资源无法启动或运行，原因是其无法保留足够的系统资源。 |
Resource could not start or run because it could not reserve sufficient system resources. |
| 0x1745 | 资源拒绝在两个节点之间移动，原因是目标当前没有足够的资源来完成操作。 |
A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation. |
| 0x1746 | 资源拒绝在两个节点之间移动，原因是源当前没有足够的资源来完成该操作。 |
A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation. |
| 0x1747 | 无法完成请求的操作，原因是该组已排入操作队列中。 |
The requested operation can not be completed because the group is queued for an operation. |
| 0x1748 | 无法完成请求的操作，原因是资源的状态为已锁定。 |
The requested operation can not be completed because a resource has locked status. |
| 0x1749 | 资源无法移动到另一个节点，原因是群集共享卷拒绝此操作。 |
The resource cannot move to another node because a cluster shared volume vetoed the operation. |
| 0x174A | 节点排出已在进行中。 |
A node drain is already in progress. |
| 0x174B | 群集存储未连接到节点。 |
Clustered storage is not connected to the node. |
| 0x174C | 未将磁盘配置为与 CSV 一起使用。CSV 磁盘必须至少具有一个格式化为 NTFS 或 REFS 的分区。 |
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. |
| 0x174D | 资源必须是可用存储组的一部分才能完成此操作。 |
The resource must be part of the Available Storage group to complete this action. |
| 0x174E | CSVFS 操作失败，因为卷处于重定向模式。 |
CSVFS failed operation as volume is in redirected mode. |
| 0x174F | CSVFS 操作失败，因为卷未处于重定向模式。 |
CSVFS failed operation as volume is not in redirected mode. |
| 0x1750 | 此时无法返回群集属性。 |
Cluster properties cannot be returned at this time. |
| 0x1751 | 群集磁盘资源包含不支持群集共享卷的软件快照差异区域。 |
The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes. |
| 0x1752 | 该操作无法完成，原因是资源正处于维护模式中。 |
The operation cannot be completed because the resource is in maintenance mode. |
| 0x1753 | 由于出现群集关联冲突，无法完成操作 |
The operation cannot be completed because of cluster affinity conflicts |
| 0x1754 | 该操作无法完成，原因是自由是副本虚拟机。 |
The operation cannot be completed because the resource is a replica virtual machine. |
| 0x1755 | 不能提高群集功能级别，因为并非群集中的所有节点都支持升级后的版本。 |
The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version. |
| 0x1756 | 由于群集正在修复仲裁模式下运行，更新群集功能级别失败。请启动其他作为群集成员的节点，直到该群集满足仲裁条件，该群集将自动切出修复仲裁模式，或者在不使用 FixQuorum 开关的情况下停止并重新启动该群集。该群集退出修复仲裁模式后， 请重试 Update-ClusterFunctionalLevel PowerShell cmdlet 以更新群集功能级别。 |
Updating the cluster functional level failed because the cluster is running in fix quorum mode.Start additional nodes which are members of the cluster until the cluster reaches quorum and the cluster will automaticallyswitch out of fix quorum mode, or stop and restart the cluster without the FixQuorum switch. Once the cluster is outof fix quorum mode retry the Update-ClusterFunctionalLevel PowerShell cmdlet to update the cluster functional level. |
| 0x1757 | 群集功能级别已成功更新，但并非所有功能都可用。请通过先使用 Stop-Cluster PowerShell cmdlet再使用 Start-Cluster PowerShell cmdlet 来重新启动群集，然后所有群集功能均将可用。 |
The cluster functional level has been successfully updated but not all features are available yet. Restart the cluster byusing the Stop-Cluster PowerShell cmdlet followed by the Start-Cluster PowerShell cmdlet and all cluster features willbe available. |
| 0x1758 | 群集当前正在执行版本升级。 |
The cluster is currently performing a version upgrade. |
| 0x1759 | 群集未成功完成版本升级。 |
The cluster did not successfully complete the version upgrade. |
| 0x175A | 群集节点处于宽限期。 |
The cluster node is in grace period. |
| 0x175B | 由于 CSV 卷无法在此文件对象中指定的时间恢复，操作已失败。 |
The operation has failed because CSV volume was not able to recover in time specified on this file object. |
| 0x175C | 由于请求的节点当前不是活动群集成员身份的一部分，操作失败。 |
The operation failed because the requested node is not currently part of active cluster membership. |
| 0x175D | 由于请求的群集资源当前未被监视，操作失败。 |
The operation failed because the requested cluster resource is currently unmonitored. |
| 0x175E | 由于资源不支持在未被监视的状态下运行，操作失败。 |
The operation failed because a resource does not support running in an unmonitored state. |
| 0x175F | 由于资源参与复制，无法完成操作。 |
The operation cannot be completed because a resource participates in replication. |
| 0x1760 | 由于请求的群集节点已被隔离，操作失败 |
The operation failed because the requested cluster node has been isolated |
| 0x1762 | 操作失败，因为不符合指定的数据库更新条件 |
The operation failed because the specified database update condition was not met |
| 0x1763 | 群集的空间处于降级状态，此时无法完成请求的操作。 |
A clustered space is in a degraded condition and the requested action cannot be completed at this time. |
| 0x1764 | 操作失败，因为不支持此控件的令牌委派。 |
The operation failed because token delegation for this control is not supported. |
| 0x1765 | 操作失败，因为 CSV 没有通过此文件对象的验证。 |
The operation has failed because CSV has invalidated this file object. |
| 0x1766 | 只有 CSV 协调器节点才支持此操作。 |
This operation is supported only on the CSV coordinator node. |
| 0x1767 | 群集组集不可用于任何进一步的请求。 |
The cluster group set is not available for any further requests. |
| 0x1768 | 找不到群集组集。 |
The cluster group set could not be found. |
| 0x1769 | 现在无法完成该操作，因为群集组集将低于仲裁，不能作为提供者。 |
The action cannot be completed at this time because the cluster group set would fall below quorum and not be able to act as a provider. |
| 0x176A | 未找到指定的父容错域。 |
The specified parent fault domain is not found. |
| 0x176B | 该容错域不能是指定的父级的子级。 |
The fault domain cannot be a child of the parent specified. |
| 0x176C | 存储空间直通已拒绝建议的容错域更改，因为它会影响存储的容错能力。 |
Storage Spaces Direct has rejected the proposed fault domain changes because it impacts the fault tolerance of the storage. |
| 0x176D | 存储空间直通已拒绝建议的容错域更改，因为它会减少连接到系统的存储。 |
Storage Spaces Direct has rejected the proposed fault domain changes because it reduces the storage connected to the system. |
| 0x1770 | 无法加密指定的文件。 |
The specified file could not be encrypted. |
| 0x1771 | 指定的文件无法解密。 |
The specified file could not be decrypted. |
| 0x1772 | 指定的文件已加密，而且用户没有能力解密。 |
The specified file is encrypted and the user does not have the ability to decrypt it. |
| 0x1773 | 这个系统没有有效的加密恢复策略配置。 |
There is no valid encryption recovery policy configured for this system. |
| 0x1774 | 所需的加密驱动程序并未加载到系统中。 |
The required encryption driver is not loaded for this system. |
| 0x1775 | 文件加密所使用的加密驱动程序与目前加载的加密驱动程序不同。 |
The file was encrypted with a different encryption driver than is currently loaded. |
| 0x1776 | 没有为用户定义 EFS 关键字。 |
There are no EFS keys defined for the user. |
| 0x1777 | 指定的文件并未加密。 |
The specified file is not encrypted. |
| 0x1778 | 指定的文件不是定义的 EFS 导出格式。 |
The specified file is not in the defined EFS export format. |
| 0x1779 | 指定的文件是只读文件。 |
The specified file is read only. |
| 0x177A | 已为加密而停用目录。 |
The directory has been disabled for encryption. |
| 0x177B | 不信任服务器来进行远程加密操作。 |
The server is not trusted for remote encryption operation. |
| 0x177C | 为此系统配置的恢复策略包含无效恢复证书。 |
Recovery policy configured for this system contains invalid recovery certificate. |
| 0x177D | 用在此源文件上的加密算法需要比目标文件上更大的密钥缓冲区。 |
The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file. |
| 0x177E | 磁盘分区不支持文件加密。 |
The disk partition does not support file encryption. |
| 0x177F | 这台计算机已为文件加密而停用。 |
This machine is disabled for file encryption. |
| 0x1780 | 需要一个更新的系统来解密此加密文件。 |
A newer system is required to decrypt this encrypted file. |
| 0x1781 | 远程服务器为使用客户端加密打开的文件发送了无效的响应。 |
The remote server sent an invalid response for a file being opened with Client Side Encryption. |
| 0x1782 | 远程服务器不支持客户端加密，即使其声明支持。 |
Client Side Encryption is not supported by the remote server even though it claims to support it. |
| 0x1783 | 文件已加密，应以客户端加密模式打开。 |
File is encrypted and should be opened in Client Side Encryption mode. |
| 0x1784 | 正在新建加密文件，需要提供 $EFS。 |
A new encrypted file is being created and a $EFS needs to be provided. |
| 0x1785 | SMB 客户端在非 CSE 文件上请求 CSE FSCTL。 |
The SMB client requested a CSE FSCTL on a non-CSE file. |
| 0x1786 | 所请求的操作被策略阻止。有关详细信息，请与系统管理员联系。 |
The requested operation was blocked by policy. For more information, contact your system administrator. |
| 0x17E6 | 此工作组的服务器列表当前无法使用 |
The list of servers for this workgroup is not currently available |
| 0x1838 | 要正常运行，任务计划程序服务的配置必须在系统帐户中运行。单独的任务可以被配置成在其他帐户中运行。 |
The 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. |
| 0x19C8 | 日志服务遇到无效日志扇区。 |
Log service encountered an invalid log sector. |
| 0x19C9 | 日志服务遇到块奇偶校验无效的日志扇区。 |
Log service encountered a log sector with invalid block parity. |
| 0x19CA | 日志服务遇到重映射的日志扇区。 |
Log service encountered a remapped log sector. |
| 0x19CB | 日志服务遇到部分或未完成的日志块。 |
Log service encountered a partial or incomplete log block. |
| 0x19CC | 日志服务遇到错误，原因: 试图访问活动日志范围外的数据。 |
Log service encountered an attempt access data outside the active log range. |
| 0x19CD | 日志服务用户排列缓冲区已用尽。 |
Log service user marshalling buffers are exhausted. |
| 0x19CE | 日志服务遇到错误，原因: 试图从读取上下文无效的排列区读取。 |
Log service encountered an attempt read from a marshalling area with an invalid read context. |
| 0x19CF | 日志服务遇到无效日志重新启动区域。 |
Log service encountered an invalid log restart area. |
| 0x19D0 | 日志服务遇到无效日志块版本。 |
Log service encountered an invalid log block version. |
| 0x19D1 | 日志服务遇到无效日志块。 |
Log service encountered an invalid log block. |
| 0x19D2 | 日志服务遇到错误，原因: 试图以无效读取模式读取。 |
Log service encountered an attempt to read the log with an invalid read mode. |
| 0x19D3 | 日志服务遇到错误，原因: 日志流没有重新启动区。 |
Log service encountered a log stream with no restart area. |
| 0x19D4 | 日志服务遇到损坏的元数据文件。 |
Log service encountered a corrupted metadata file. |
| 0x19D5 | 日志服务遇到无法由日志文件系统创建的元数据文件。 |
Log service encountered a metadata file that could not be created by the log file system. |
| 0x19D6 | 日志服务遇到数据不一致的元数据文件。 |
Log service encountered a metadata file with inconsistent data. |
| 0x19D7 | 日志服务遇到错误，原因: 试图分配和排列保留空间。 |
Log service encountered an attempt to erroneous allocate or dispose reservation space. |
| 0x19D8 | 日志服务无法删除日志文件或文件系统容器。 |
Log service cannot delete log file or file system container. |
| 0x19D9 | 日志服务已经达到允许分配给日志文件的容器的上限。 |
Log service has reached the maximum allowable containers allocated to a log file. |
| 0x19DA | 日志服务试图读取或写入日志开始之前的位置。 |
Log service has attempted to read or write backward past the start of the log. |
| 0x19DB | 由于相同类型的策略已经存在，无法安装日志策略。 |
Log policy could not be installed because a policy of the same type is already present. |
| 0x19DC | 该疑问日志策略在请求时尚未安装。 |
Log policy in question was not installed at the time of the request. |
| 0x19DD | 日志上的策略的已安装集无效。 |
The installed set of policies on the log is invalid. |
| 0x19DE | 该疑问日志上的策略阻止完成操作。 |
A policy on the log in question prevented the operation from completing. |
| 0x19DF | 由于日志被存档结尾固定，无法回收日志空间。 |
Log space cannot be reclaimed because the log is pinned by the archive tail. |
| 0x19E0 | 日志记录不是日志文件中的记录。 |
Log record is not a record in the log file. |
| 0x19E1 | 保留的日志记录数或保留的日志记录数的调整无效。 |
Number of reserved log records or the adjustment of the number of reserved log records is invalid. |
| 0x19E2 | 保留的日志空间或日志空间的调整无效。 |
Reserved log space or the adjustment of the log space is invalid. |
| 0x19E3 | 活动日志的一个新的或现有的存档结尾或主体无效。 |
An new or existing archive tail or base of the active log is invalid. |
| 0x19E4 | 日志空间已用尽。 |
Log space is exhausted. |
| 0x19E5 | 无法将日志设置为请求的大小。 |
The log could not be set to the requested size. |
| 0x19E6 | 日志被复用，不允许直接写入物理日志。 |
Log is multiplexed, no direct writes to the physical log is allowed. |
| 0x19E7 | 由于日志是专用日志，操作失败。 |
The operation failed because the log is a dedicated log. |
| 0x19E8 | 操作需要存档上下文。 |
The operation requires an archive context. |
| 0x19E9 | 日志存档进行中。 |
Log archival is in progress. |
| 0x19EA | 操作需要长日志，但该日志是极短日志。 |
The operation requires a non-ephemeral log, but the log is ephemeral. |
| 0x19EB | 日志必须至少拥有两个容器，才能读取或写入。 |
The log must have at least two containers before it can be read from or written to. |
| 0x19EC | 日志客户端已经在该流上注册。 |
A log client has already registered on the stream. |
| 0x19ED | 日志客户端尚未在该流上注册。 |
A log client has not been registered on the stream. |
| 0x19EE | 已经请求处理日志满状况。 |
A request has already been made to handle the log full condition. |
| 0x19EF | 日志服务试图读取日志容器时遇到错误。 |
Log service encountered an error when attempting to read from a log container. |
| 0x19F0 | 日志服务试图写入日志容器时遇到错误。 |
Log service encountered an error when attempting to write to a log container. |
| 0x19F1 | 日志服务试图打开日志容器时遇到错误。 |
Log service encountered an error when attempting open a log container. |
| 0x19F2 | 日志服务试图执行请求的操作时遇到无效容器状态。 |
Log service encountered an invalid container state when attempting a requested action. |
| 0x19F3 | 日志服务状态错误，不能执行请求的操作。 |
Log service is not in the correct state to perform a requested action. |
| 0x19F4 | 由于日志被固定，无法回收日志空间。 |
Log space cannot be reclaimed because the log is pinned. |
| 0x19F5 | 未能刷新日志元数据。 |
Log metadata flush failed. |
| 0x19F6 | 日志及其容器上的安全不一致。 |
Security on the log and its containers is inconsistent. |
| 0x19F7 | 已将记录附加到日志或已进行保留更改，但无法刷新日志。 |
Records were appended to the log or reservation changes were made, but the log could not be flushed. |
| 0x19F8 | 由于保留会消耗大部分日志空间，因此已固定该日志。请释放某些保留的记录以增加可用空间。 |
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. |
| 0x1A2C | 与该操作关联的事务句柄无效。 |
The transaction handle associated with this operation is not valid. |
| 0x1A2D | 请求的操作是在不再活动的事务的上下文中进行的。 |
The requested operation was made in the context of a transaction that is no longer active. |
| 0x1A2E | 请求的操作在当前状态的事务对象上无效。 |
The requested operation is not valid on the Transaction object in its current state. |
| 0x1A2F | 调用方调用了响应 API，但响应不是预期的响应，因为 TM 未将相应的请求发送到调用方。 |
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. |
| 0x1A30 | 执行请求的操作太迟，因为事务已中止。 |
It is too late to perform the requested operation, since the Transaction has already been aborted. |
| 0x1A31 | 执行请求的操作太迟，因为事务已提交。 |
It is too late to perform the requested operation, since the Transaction has already been committed. |
| 0x1A32 | 无法成功启动事务管理器。不支持事务处理操作。 |
The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported. |
| 0x1A33 | 指定的 ResourceManager 未对该事务下的资源进行更改或更新。 |
The specified ResourceManager made no changes or updates to the resource under this transaction. |
| 0x1A34 | 资源管理器已尝试准备其未成功加入的事务。 |
The resource manager has attempted to prepare a transaction that it has not successfully joined. |
| 0x1A35 | Transaction 对象已经具有上级登记，而调用方尝试了一个会创建新上级的操作。仅允许单个上级登记。 |
The 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. |
| 0x1A36 | RM 尝试注册已经存在的协议。 |
The RM tried to register a protocol that already exists. |
| 0x1A37 | 尝试传播事务失败。 |
The attempt to propagate the Transaction failed. |
| 0x1A38 | 请求的传播协议未注册为 CRM。 |
The requested propagation protocol was not registered as a CRM. |
| 0x1A39 | 传递到 PushTransaction 或 PullTransaction 的缓冲区格式无效。 |
The buffer passed in to PushTransaction or PullTransaction is not in a valid format. |
| 0x1A3A | 与线程关联的当前事务上下文对于事务对象不是有效的句柄。 |
The current transaction context associated with the thread is not a valid handle to a transaction object. |
| 0x1A3B | 指定的 Transaction 对象无法打开，因为找不到该对象。 |
The specified Transaction object could not be opened, because it was not found. |
| 0x1A3C | 指定的 ResourceManager 对象无法打开，因为找不到该对象。 |
The specified ResourceManager object could not be opened, because it was not found. |
| 0x1A3D | 指定的 Enlistment 对象无法打开，因为找不到该对象。 |
The specified Enlistment object could not be opened, because it was not found. |
| 0x1A3E | 指定的 TransactionManager 对象无法打开，因为找不到该对象。 |
The specified TransactionManager object could not be opened, because it was not found. |
| 0x1A3F | 无法创建或打开指定的对象，原因是其关联的 TransactionManager 未联机。必须通过调用 RecoverTransactionManager 将 TransactionManager 完全联机以恢复到其 LogFile 的末尾后，才能打开其 Transaction 或 ResourceManager 命名空间中的对象。另外，将记录写入到其 LogFile 时出现的错误可导致 TransactionManager 脱机。 |
The 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. |
| 0x1A40 | 指定的 TransactionManager 无法在 Ob 命名空间中创建包含在其日志文件中的对象。因此，无法恢复 TransactionManager。 |
The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover. |
| 0x1A41 | 用于在此事务对象上创建上级登记的调用无法完成，原因是指定用于登记的事务对象是该事务的下级分支。只有事务的根才能登记为上级。 |
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. |
| 0x1A42 | 由于关联的事物管理器或资源管理器已关闭，因此句柄不再有效。 |
Because the associated transaction manager or resource manager has been closed, the handle is no longer valid. |
| 0x1A43 | 无法在该上级登记上执行指定的操作，因为未使用 NotificationMask 中相应的完成响应创建该登记。 |
The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask. |
| 0x1A44 | 无法执行指定的操作，因为要记录的记录过长。发生这种情况是由于以下两种条件: 该事务上的登记过多，或代表这些登记记录的组合 RecoveryInformation 过长。 |
The 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. |
| 0x1A45 | 不支持隐式事务。 |
Implicit transaction are not supported. |
| 0x1A46 | 核心事务管理器必须中止或忽略该事务，因为它阻止继续进行操作。 |
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. |
| 0x1A47 | 已提供的 TransactionManager 标识与 TransactionManager 的日志文件中记录的标识不匹配。 |
The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file. |
| 0x1A48 | 此快照操作无法继续，因为无法在事务性资源管理器处于当前状态时将其冻结。请再试一次。 |
This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again. |
| 0x1A49 | 无法使用指定的 EnlistmentMask 登记事务，原因是该事务已完成预先准备阶段。为确保正确性，ResourceManager 必须切换到写入模式并停止缓存此事务中的数据。仅登记后面的事务阶段仍可成功。 |
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. |
| 0x1A4A | 该事务没有上级登记。 |
The transaction does not have a superior enlistment. |
| 0x1A4B | 提交事务的尝试已完成，但由于启发，事务树的某些部分可能未成功提交。因此可能没有提交事务中已修改的某些数据，从而导致事务不一致。如果可能的话，请检查关联数据的一致性。 |
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. |
| 0x1A90 | 该函数尝试使用为让另一事务使用而保留的名称。 |
The function attempted to use a name that is reserved for use by another transaction. |
| 0x1A91 | 由于发生错误，指定资源管理器中的事务支持未启动或已关闭。 |
Transaction support within the specified resource manager is not started or was shut down due to an error. |
| 0x1A92 | RM 的元数据已损坏。RM 将不起作用。 |
The metadata of the RM has been corrupted. The RM will not function. |
| 0x1A93 | 指定的目录不包含资源管理器。 |
The specified directory does not contain a resource manager. |
| 0x1A95 | 远程服务器或共享不支持事务处理文件操作。 |
The remote server or share does not support transacted file operations. |
| 0x1A96 | 请求的日志大小无效。 |
The requested log size is invalid. |
| 0x1A97 | 事务保存点回退已删除与句柄关联的对象(文件、流、链接)。 |
The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback. |
| 0x1A98 | 找不到用于此事务处理文件打开的指定文件的迷你版本。 |
The specified file miniversion was not found for this transacted file open. |
| 0x1A99 | 指定的文件迷你版本已找到，但已经无效。最可能是因为事务保存点回退。 |
The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback. |
| 0x1A9A | 迷你版本只能在创建该迷你版本的事务的上下文中打开。 |
A miniversion may only be opened in the context of the transaction that created it. |
| 0x1A9B | 无法使用修改访问来打开迷你版本。 |
It is not possible to open a miniversion with modify access. |
| 0x1A9C | 无法再创建此流的迷你版本。 |
It is not possible to create any more miniversions for this stream. |
| 0x1A9E | 远程服务器发送了使用事务打开的文件的不匹配的版本号或 Fid。 |
The remote server sent mismatching version number or Fid for a file opened with transactions. |
| 0x1A9F | 该句柄已由事务验证无效。最可能的原因是在事务结束或回退到保存点时，文件或打开的句柄上出现内存映射。 |
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. |
| 0x1AA0 | 文件中没有事务元数据。 |
There is no transaction metadata on the file. |
| 0x1AA1 | 日志数据损坏。 |
The log data is corrupt. |
| 0x1AA2 | 无法恢复文件，因为文件上仍然有打开的句柄。 |
The file can't be recovered because there is a handle still open on it. |
| 0x1AA3 | 事务结果不可用，因为对其负责的资源管理器已经断开连接。 |
The transaction outcome is unavailable because the resource manager responsible for it has disconnected. |
| 0x1AA4 | 请求遭到拒绝，因为问题中的登记不是上级登记。 |
The request was rejected because the enlistment in question is not a superior enlistment. |
| 0x1AA5 | 事务性资源管理器已经一致。无需恢复。 |
The transactional resource manager is already consistent. Recovery is not needed. |
| 0x1AA6 | 事务性资源管理器已经启动。 |
The transactional resource manager has already been started. |
| 0x1AA7 | 无法以事务方式打开该文件，因为文件标识取决于一个未解决的事务的结果。 |
The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction. |
| 0x1AA8 | 无法执行该操作，因为另一事务取决于此属性将不会更改的事实。 |
The operation cannot be performed because another transaction is depending on the fact that this property will not change. |
| 0x1AA9 | 该操作将涉及一个文件和两个事务性资源管理器，因此不被允许。 |
The operation would involve a single file with two transactional resource managers and is therefore not allowed. |
| 0x1AAA | $Txf 目录必须为空，此操作才能成功。 |
The $Txf directory must be empty for this operation to succeed. |
| 0x1AAB | 该操作将事务性资源管理器置于不一致状态，因此不被允许。 |
The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed. |
| 0x1AAC | 由于事务管理器没有日志，因此操作无法完成。 |
The operation could not be completed because the transaction manager does not have a log. |
| 0x1AAD | 无法计划回退，因为以前计划的回退已经执行或已排队等候执行。 |
A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. |
| 0x1AAE | 文件或目录上的事务性元数据属性已经损坏，不可读取。 |
The transactional metadata attribute on the file or directory is corrupt and unreadable. |
| 0x1AAF | 无法完成加密操作，因为事务是活动的。 |
The encryption operation could not be completed because a transaction is active. |
| 0x1AB0 | 不允许在事务中打开该对象。 |
This object is not allowed to be opened in a transaction. |
| 0x1AB1 | 尝试在事务性资源管理器日志中创建空间失败。已在事件日志中记录失败状态。 |
An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log. |
| 0x1AB2 | 不支持对事务下的远程文件进行内存映射(创建映射区域)。 |
Memory mapping (creating a mapped section) a remote file under a transaction is not supported. |
| 0x1AB3 | 事务元数据已经存在于该文件中，无法取代。 |
Transaction metadata is already present on this file and cannot be superseded. |
| 0x1AB4 | 无法输入事务处理范围，因为尚未启动范围处理程序。 |
A transaction scope could not be entered because the scope handler has not been initialized. |
| 0x1AB5 | 需要升级才能允许资源管理器登记，但已将事务设置为不允许升级。 |
Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it. |
| 0x1AB6 | 该文件已在未解决的事务中打开进行修改，可能仅有事务处理阅读器才能将其打开用于执行。 |
This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader. |
| 0x1AB7 | 使冻结事务解冻的请求遭到忽略，因为以前并未冻结事务。 |
The request to thaw frozen transactions was ignored because transactions had not previously been frozen. |
| 0x1AB8 | 无法冻结事务，因为正在进行某个冻结过程。 |
Transactions cannot be frozen because a freeze is already in progress. |
| 0x1AB9 | 目标卷并非快照卷。此操作仅在装载为快照的卷上有效。 |
The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot. |
| 0x1ABA | 保存点操作失败，因为在事务上打开文件。上述情况是不允许的。 |
The savepoint operation failed because files are open on the transaction. This is not permitted. |
| 0x1ABB | Windows 发现文件损坏并对该文件进行了修复。可能发生了数据丢失。 |
Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred. |
| 0x1ABC | 无法完成稀疏操作，因为文件上的事务是活动的。 |
The sparse operation could not be completed because a transaction is active on the file. |
| 0x1ABD | 对创建 TransactionManager 对象的调用失败，因为存储在日志文件中的 Tm 标识与作为参数传递的 Tm 标识不匹配。 |
The 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. |
| 0x1ABE | 在由于事务结束而引起浮动的区域对象上尝试 I/O。没有有效的数据。 |
I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data. |
| 0x1ABF | 由于暂时情况(如资源不足)事务性资源管理器当前无法接受事务处理工作。 |
The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources. |
| 0x1AC0 | 事务性资源管理器具有太多无法中止的未决事务处理。事务性资源管理器已经关闭。 |
The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down. |
| 0x1AC1 | 由于磁盘上的群集损坏，因此操作无法完成。 |
The operation could not be completed due to bad clusters on disk. |
| 0x1AC2 | 由于该文件上的一个事务处于活动状态，压缩操作无法完成。 |
The compression operation could not be completed because a transaction is active on the file. |
| 0x1AC3 | 无法完成操作，因为卷有问题。请运行 chkdsk 并重试。 |
The operation could not be completed because the volume is dirty. Please run chkdsk and try again. |
| 0x1AC4 | 无法完成链接跟踪操作，因为事务处于活动状态。 |
The link tracking operation could not be completed because a transaction is active. |
| 0x1AC5 | 无法在事务中执行此操作。 |
This operation cannot be performed in a transaction. |
| 0x1AC6 | 句柄不再正确地与其事务相关联。此句柄可能已在事务资源管理器中打开，而随后该事务资源管理器被强制重新启动。请关闭此句柄并打开新的句柄。 |
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. |
| 0x1AC7 | 无法执行指定操作，因为在事务中未登记资源管理器。 |
The specified operation could not be performed because the resource manager is not enlisted in the transaction. |
| 0x1B59 | 指定的会话名称无效。 |
The specified session name is invalid. |
| 0x1B5A | 指定的协议驱动程序无效。 |
The specified protocol driver is invalid. |
| 0x1B5B | 在系统路径上找不到指定的协议驱动程序。 |
The specified protocol driver was not found in the system path. |
| 0x1B5C | 在系统路径上找不到指定的终端连接驱动程序。 |
The specified terminal connection driver was not found in the system path. |
| 0x1B5D | 不能为这个会话创建一个事件日志的注册表项。 |
A registry key for event logging could not be created for this session. |
| 0x1B5E | 同名的一个服务已经在系统中存在。 |
A service with the same name already exists on the system. |
| 0x1B5F | 在会话上一个关闭操作挂起。 |
A close operation is pending on the session. |
| 0x1B60 | 没有可用的输出缓冲区。 |
There are no free output buffers available. |
| 0x1B61 | 找不到 MODEM.INF 文件。 |
The MODEM.INF file was not found. |
| 0x1B62 | 在 MODEM.INF 中找不到调制解调器名称。 |
The modem name was not found in MODEM.INF. |
| 0x1B63 | 调制解调器没有接受发送给它的命令。验证配置的调制解调器与连接的调制解调器是否匹配。 |
The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem. |
| 0x1B64 | 调制解调器没有接受发送给它的命令。验证该调制解调器是否接线正确并且打开了电源开关。 |
The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on. |
| 0x1B65 | 由于连接被中断，载波检测没有成功，或者载波已被放弃。 |
Carrier detect has failed or carrier has been dropped due to disconnect. |
| 0x1B66 | 在要求的时间内没有检测到拨号音。确定电话线连接正确并可使用。 |
Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional. |
| 0x1B67 | 在远程站点回拨时检测到了占线信号。 |
Busy signal detected at remote site on callback. |
| 0x1B68 | 回拨时在远程站点上检测到了声音。 |
Voice detected at remote site on callback. |
| 0x1B69 | 传输驱动程序错误 |
Transport driver error |
| 0x1B6E | 无法找到指定的会话。 |
The specified session cannot be found. |
| 0x1B6F | 指定的会话名称已在使用中。 |
The specified session name is already in use. |
| 0x1B70 | 由于远程桌面服务当前正忙，因此无法完成你尝试执行的任务。请在几分钟之后重试。其他用户应该仍然能够登录。 |
The 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. |
| 0x1B71 | 试图连接到其视频模式不受当前客户端支持的会话。 |
An attempt has been made to connect to a session whose video mode is not supported by the current client. |
| 0x1B7B | 应用程序试图启用 DOS 图形模式。不支持 DOS 图形模式。 |
The application attempted to enable DOS graphics mode. DOS graphics mode is not supported. |
| 0x1B7D | 你的交互式登录特权已被禁用。请与管理员联系。 |
Your interactive logon privilege has been disabled. Please contact your administrator. |
| 0x1B7E | 请求的操作只能在系统控制台上执行。这通常是驱动程序或系统 DLL 要求直接访问控制台的结果。 |
The 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. |
| 0x1B80 | 客户端未能对服务器连接消息作出响应。 |
The client failed to respond to the server connect message. |
| 0x1B81 | 不支持断开控制台会话的连接。 |
Disconnecting the console session is not supported. |
| 0x1B82 | 不支持重新将一个断开的会话连接到控制台。 |
Reconnecting a disconnected session to the console is not supported. |
| 0x1B84 | 远程控制另一个会话的请求被拒绝。 |
The request to control another session remotely was denied. |
| 0x1B85 | 拒绝请求的会话访问。 |
The requested session access is denied. |
| 0x1B89 | 指定的终端连接驱动程序无效。 |
The specified terminal connection driver is invalid. |
| 0x1B8A | 不能远程控制该请求的会话。这也许是由于该会话被断开连接或目前没有一个用户登录。 |
The requested session cannot be controlled remotely.This may be because the session is disconnected or does not currently have a user logged on. |
| 0x1B8B | 该请求的会话没有配置成允许远程控制。 |
The requested session is not configured to allow remote control. |
| 0x1B8C | 已拒绝连接到该终端服务器的请求。另一个用户正在使用你的终端服务器客户端许可证号码。请与系统管理员联系，获取唯一的许可证号码。 |
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. |
| 0x1B8D | 已拒绝连接到该终端服务器的请求。还没有为这个终端服务器客户端输入你的终端服务器客户端许可证号码。请与系统管理员联系。 |
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. |
| 0x1B8E | 与此计算机的连接数量是有限的，现在已经使用所有连接。请尝试稍后连接或与系统管理员联系。 |
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. |
| 0x1B8F | 你使用的客户端没有使用这个系统的权利。你的登录请求遭到拒绝。 |
The client you are using is not licensed to use this system. Your logon request is denied. |
| 0x1B90 | 系统许可证已过期。登录请求被拒绝。 |
The system license has expired. Your logon request is denied. |
| 0x1B91 | 由于当前没有远程控制指定的会话，无法终止远程控制。 |
Remote control could not be terminated because the specified session is not currently being remotely controlled. |
| 0x1B92 | 由于更改了显示模式，控制台的远程控制已终止。不支持在远程控制会话中更改显示模式。 |
The 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. |
| 0x1B93 | 激活已经被此安装重置最大时间数。不会清除你的激活定时器。 |
Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared. |
| 0x1B94 | 当前已禁用远程登录。 |
Remote logins are currently disabled. |
| 0x1B95 | 没有正确的加密级别，无法访问该会话。 |
You do not have the proper encryption level to access this Session. |
| 0x1B96 | 用户 %s\\\\%s 当前已登录到此计算机。只有当前用户或管理员才能登录此计算机。 |
The user %s\\\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer. |
| 0x1B97 | 用户 %s\\\\%s 已经登录此计算机的控制台。现在你没有权限登录。要解决此问题，请联系 %s\\\\%s 并使其注销。 |
The 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. |
| 0x1B98 | 由于帐户限制，你无法登录。 |
Unable to log you on because of an account restriction. |
| 0x1B99 | RDP 协议组件 %2 在协议流中发现一个错误并且中断了客户端连接。 |
The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client. |
| 0x1B9A | 客户端驱动器映射服务已连接在终端连接上。 |
The Client Drive Mapping Service Has Connected on Terminal Connection. |
| 0x1B9B | 已在终端连接上中断客户端驱动器映射服务。 |
The Client Drive Mapping Service Has Disconnected on Terminal Connection. |
| 0x1B9C | 终端服务器安全层在协议流中检测到错误，并已取消客户端连接。 |
The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. |
| 0x1B9D | 目标会话与当前会话不兼容。 |
The target session is incompatible with the current session. |
| 0x1B9E | Windows 无法连接到会话，因为 Windows 视频子系统出现了问题。请稍后重试连接或与服务器管理员联系以获得帮助。 |
Windows 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. |
| 0x1F41 | 没有正确调用文件复制服务 API。 |
The file replication service API was called incorrectly. |
| 0x1F42 | 无法启动文件复制服务。 |
The file replication service cannot be started. |
| 0x1F43 | 无法停止文件复制服务。 |
The file replication service cannot be stopped. |
| 0x1F44 | 文件复制服务 API 终止了请求。事件日志可能会包含详细信息。 |
The file replication service API terminated the request. The event log may have more information. |
| 0x1F45 | 文件复制服务终止了请求。事件日志可能会包含详细信息。 |
The file replication service terminated the request. The event log may have more information. |
| 0x1F46 | 无法与文件复制服务联系。事件日志可能会包含详细信息。 |
The file replication service cannot be contacted. The event log may have more information. |
| 0x1F47 | 由于用户没有足够特权，文件复制服务无法满足请求。事件日志可能会包含详细信息。 |
The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information. |
| 0x1F48 | 由于已验证的 RPC 不可用，文件复制服务无法满足请求。事件日志可能会包含详细信息。 |
The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information. |
| 0x1F49 | 由于用户在域控制器上没有足够特权，文件复制服务无法满足请求。事件日志可能会包含详细信息。 |
The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information. |
| 0x1F4A | 由于已验证的 RPC 在域控制器上不可用，文件复制服务无法满足请求。事件日志可能会包含详细信息。 |
The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information. |
| 0x1F4B | 该文件复制服务无法与在域控制器上的文件复制服务通信。事件日志可能有详细信息。 |
The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information. |
| 0x1F4C | 域控制器上的文件复制服务无法与这台计算机上的文件复制服务通信。事件日志可能会包含详细信息。 |
The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information. |
| 0x1F4D | 由于内部错误，文件复制服务无法填充系统卷。事件日志可能会包含详细信息。 |
The file replication service cannot populate the system volume because of an internal error. The event log may have more information. |
| 0x1F4E | 由于内部超时，文件复制服务无法填充系统卷。事件日志可能会包含详细信息。 |
The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information. |
| 0x1F4F | 该文件复制服务无法处理此请求。该系统卷仍在忙于前一个请求。 |
The file replication service cannot process the request. The system volume is busy with a previous request. |
| 0x1F50 | 由于内部错误，文件复制服务无法停止复制系统卷。事件日志可能会包含详细信息。 |
The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information. |
| 0x1F51 | 该文件复制服务检测到一个无效参数。 |
The file replication service detected an invalid parameter. |
| 0x2008 | 在安装目录服务时出现一个错误。有关详细信息，请查看事件日志。 |
An error occurred while installing the directory service. For more information, see the event log. |
| 0x2009 | 目录服务在本地评估组成员身份。 |
The directory service evaluated group memberships locally. |
| 0x200A | 指定的目录服务属性或值不存在。 |
The specified directory service attribute or value does not exist. |
| 0x200B | 指定给目录服务的属性语法无效。 |
The attribute syntax specified to the directory service is invalid. |
| 0x200C | 指定给目录服务的属性类型未定义。 |
The attribute type specified to the directory service is not defined. |
| 0x200D | 指定的目录服务属性或值已经存在。 |
The specified directory service attribute or value already exists. |
| 0x200E | 目录服务忙。 |
The directory service is busy. |
| 0x200F | 该目录服务不可用。 |
The directory service is unavailable. |
| 0x2010 | 目录服务无法分配相对标识符。 |
The directory service was unable to allocate a relative identifier. |
| 0x2011 | 目录服务已经用完了相对标识符池。 |
The directory service has exhausted the pool of relative identifiers. |
| 0x2012 | 由于目录服务不是该类操作的主控，未能执行操作。 |
The requested operation could not be performed because the directory service is not the master for that type of operation. |
| 0x2013 | 目录服务无法初始化分配相对标识符的子系统。 |
The directory service was unable to initialize the subsystem that allocates relative identifiers. |
| 0x2014 | 该请求的操作没有满足一个或多个与该对象的类相关的约束。 |
The requested operation did not satisfy one or more constraints associated with the class of the object. |
| 0x2015 | 目录服务只可以在一个页状对象上运行要求的操作。 |
The directory service can perform the requested operation only on a leaf object. |
| 0x2016 | 目录服务不能在一个对象的 RDN 属性上执行该请求的操作。 |
The directory service cannot perform the requested operation on the RDN attribute of an object. |
| 0x2017 | 目录服务检测出修改对象类的尝试。 |
The directory service detected an attempt to modify the object class of an object. |
| 0x2018 | 不能执行请求的跨域移动操作。 |
The requested cross-domain move operation could not be performed. |
| 0x2019 | 无法联系全局目录服务器。 |
Unable to contact the global catalog server. |
| 0x201A | 策略对象是共享的并只可在根目录上修改。 |
The policy object is shared and can only be modified at the root. |
| 0x201B | 策略对象不存在。 |
The policy object does not exist. |
| 0x201C | 请求的策略信息只在目录服务中。 |
The requested policy information is only in the directory service. |
| 0x201D | 正在进行域控制器升级。 |
A domain controller promotion is currently active. |
| 0x201E | 目前没有进行域控制器升级 |
A domain controller promotion is not currently active |
| 0x2020 | 出现了一个操作错误。 |
An operations error occurred. |
| 0x2021 | 出现了一个协议错误。 |
A protocol error occurred. |
| 0x2022 | 已经超过这个请求的时间限制。 |
The time limit for this request was exceeded. |
| 0x2023 | 已经超过这个请求的大小限制。 |
The size limit for this request was exceeded. |
| 0x2024 | 已经超过这个请求的管理限制。 |
The administrative limit for this request was exceeded. |
| 0x2025 | 比较响应是假的。 |
The compare response was false. |
| 0x2026 | 比较响应是真的。 |
The compare response was true. |
| 0x2027 | 这个服务器不支持请求的身份验证方法。 |
The requested authentication method is not supported by the server. |
| 0x2028 | 这台服务器需要一个更安全的身份验证方法。 |
A more secure authentication method is required for this server. |
| 0x2029 | 不适当的身份验证。 |
Inappropriate authentication. |
| 0x202A | 未知的身份验证机制。 |
The authentication mechanism is unknown. |
| 0x202B | 从服务器返回了一个参照。 |
A referral was returned from the server. |
| 0x202C | 该服务器不支持该请求的关键扩展。 |
The server does not support the requested critical extension. |
| 0x202D | 这个请求需要一个安全的连接。 |
This request requires a secure connection. |
| 0x202E | 不恰当的匹配。 |
Inappropriate matching. |
| 0x202F | 出现一个约束冲突。 |
A constraint violation occurred. |
| 0x2030 | 在服务器上没有这样一个对象。 |
There is no such object on the server. |
| 0x2031 | 有一个别名问题。 |
There is an alias problem. |
| 0x2032 | 指定了一个无效的 dn 语法。 |
An invalid dn syntax has been specified. |
| 0x2033 | 该对象为叶对象。 |
The object is a leaf object. |
| 0x2034 | 有一个别名废弃问题。 |
There is an alias dereferencing problem. |
| 0x2035 | 该服务器不愿意处理该请求。 |
The server is unwilling to process the request. |
| 0x2036 | 检测到一个循环。 |
A loop has been detected. |
| 0x2037 | 有一个命名冲突。 |
There is a naming violation. |
| 0x2038 | 结果集太大。 |
The result set is too large. |
| 0x2039 | 该操作会影响到多个 DSA。 |
The operation affects multiple DSAs |
| 0x203A | 该服务器不可操作。 |
The server is not operational. |
| 0x203B | 出现了一个本地错误。 |
A local error has occurred. |
| 0x203C | 出现了一个编码错误。 |
An encoding error has occurred. |
| 0x203D | 出现了一个解码错误。 |
A decoding error has occurred. |
| 0x203E | 无法识别搜索筛选器。 |
The search filter cannot be recognized. |
| 0x203F | 一个或多个参数非法。 |
One or more parameters are illegal. |
| 0x2040 | 不支持指定的方式。 |
The specified method is not supported. |
| 0x2041 | 没有返回结果。 |
No results were returned. |
| 0x2042 | 该服务器不支持该指定的控制。 |
The specified control is not supported by the server. |
| 0x2043 | 客户端检测到一个参照循环。 |
A referral loop was detected by the client. |
| 0x2044 | 超过预置的参照限制。 |
The preset referral limit was exceeded. |
| 0x2045 | 搜索要求 SORT 控制。 |
The search requires a SORT control. |
| 0x2046 | 搜索结果超过指定的偏移范围。 |
The search results exceed the offset range specified. |
| 0x2047 | 目录服务检测到用于分配相对标识符的子系统被禁用。这是系统在确定相对标识符(RID)的重要部分已耗尽时采取的保护机制。请参阅 http://go.microsoft.com/fwlink/?LinkId=228610，了解建议的诊断步骤和重新启用帐户创建的过程。 |
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. |
| 0x206D | 根对象必须是一个命名上下文的头。该根对象不能有范例父类。 |
The root object must be the head of a naming context. The root object cannot have an instantiated parent. |
| 0x206E | 不能执行添加副本操作。命名上下文必须可写才能创建副本。 |
The add replica operation cannot be performed. The naming context must be writeable in order to create the replica. |
| 0x206F | 出现一个对架构中未定义的一个属性的参考。 |
A reference to an attribute that is not defined in the schema occurred. |
| 0x2070 | 超过了一个对象的最大尺寸。 |
The maximum size of an object has been exceeded. |
| 0x2071 | 试图给目录添加一个名称已在使用中的对象。 |
An attempt was made to add an object to the directory with a name that is already in use. |
| 0x2072 | 试图添加一个对象，该对象的类没有在架构中定义的 RDN。 |
An attempt was made to add an object of a class that does not have an RDN defined in the schema. |
| 0x2073 | 试图添加一个使用 RDN 的对象，但该 RDN 不是在架构中定义的 RDN。 |
An attempt was made to add an object using an RDN that is not the RDN defined in the schema. |
| 0x2074 | 在对象中找不到任何请求的属性。 |
None of the requested attributes were found on the objects. |
| 0x2075 | 用户缓冲区太小。 |
The user buffer is too small. |
| 0x2076 | 在操作中指定的属性不在对象上。 |
The attribute specified in the operation is not present on the object. |
| 0x2077 | 修改操作非法。不允许该修改的某个方面。 |
Illegal modify operation. Some aspect of the modification is not permitted. |
| 0x2078 | 指定的对象太大。 |
The specified object is too large. |
| 0x2079 | 指定的实例类型无效。 |
The specified instance type is not valid. |
| 0x207A | 操作必须在主控 DSA 执行。 |
The operation must be performed at a master DSA. |
| 0x207B | 必须指定对象类属性。 |
The object class attribute must be specified. |
| 0x207C | 找不到所需的属性。 |
A required attribute is missing. |
| 0x207D | 试图修改一个对象，以便包括对其类非法的属性。 |
An attempt was made to modify an object to include an attribute that is not legal for its class. |
| 0x207E | 指定的属性已在对象上。 |
The specified attribute is already present on the object. |
| 0x2080 | 指定的属性不存在或没有值。 |
The specified attribute is not present, or has no values. |
| 0x2081 | 为只能有一个值的属性指定了多个值。 |
Multiple values were specified for an attribute that can have only one value. |
| 0x2082 | 属性值不在接受范围内。 |
A value for the attribute was not in the acceptable range of values. |
| 0x2083 | 指定的值已存在。 |
The specified value already exists. |
| 0x2084 | 由于不在对象上，不能删除该属性。 |
The attribute cannot be removed because it is not present on the object. |
| 0x2085 | 由于不在对象上，不能删除该属性值。 |
The attribute value cannot be removed because it is not present on the object. |
| 0x2086 | 指定的根对象不能是子参照。 |
The specified root object cannot be a subref. |
| 0x2087 | 不允许链接。 |
Chaining is not permitted. |
| 0x2088 | 不允许链接的评估。 |
Chained evaluation is not permitted. |
| 0x2089 | 由于对象的父类不是未范例化就是被删除了，所以不能执行操作。 |
The operation could not be performed because the object's parent is either uninstantiated or deleted. |
| 0x208A | 不允许使用是别名的父对象。别名是叶对象。 |
Having a parent that is an alias is not permitted. Aliases are leaf objects. |
| 0x208B | 对象和父对象必须是同一类型，不是都是原件就是都是副本。 |
The object and parent must be of the same type, either both masters or both replicas. |
| 0x208C | 由于存在子对象，无法执行操作。这个操作只能在叶对象上执行。 |
The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object. |
| 0x208D | 找不到目录对象。 |
Directory object not found. |
| 0x208E | 找不到别名对象。 |
The aliased object is missing. |
| 0x208F | 对象名称语法不正确。 |
The object name has bad syntax. |
| 0x2090 | 不允许一个别名参考另一个别名。 |
It is not permitted for an alias to refer to another alias. |
| 0x2091 | 别名不能解除参考。 |
The alias cannot be dereferenced. |
| 0x2092 | 操作超出范围。 |
The operation is out of scope. |
| 0x2093 | 由于正在删除对象，操作无法继续。 |
The operation cannot continue because the object is in the process of being removed. |
| 0x2094 | 不能删除 DSA 对象。 |
The DSA object cannot be deleted. |
| 0x2095 | 出现了一个目录服务错误。 |
A directory service error has occurred. |
| 0x2096 | 操作只能在内部主控 DSA 对象上执行。 |
The operation can only be performed on an internal master DSA object. |
| 0x2097 | 对象必须为 DSA 类。 |
The object must be of class DSA. |
| 0x2098 | 访问特权不够，不能执行该操作。 |
Insufficient access rights to perform the operation. |
| 0x2099 | 由于父类不在可能的上级列表上，不能添加该对象。 |
The object cannot be added because the parent is not on the list of possible superiors. |
| 0x209A | 由于该属性处于“安全帐户管理器” (SAM)，不允许访问该属性。 |
Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM). |
| 0x209B | 名称有太多部分。 |
The name has too many parts. |
| 0x209C | 名称太长。 |
The name is too long. |
| 0x209D | 名称值太长。 |
The name value is too long. |
| 0x209E | 目录服务分析名称时遇到一个错误。 |
The directory service encountered an error parsing a name. |
| 0x209F | 目录服务找不到一个名称的属性类型。 |
The directory service cannot get the attribute type for a name. |
| 0x20A0 | 该名称不能识别一个对象；该名称识别一个幻象。 |
The name does not identify an object; the name identifies a phantom. |
| 0x20A1 | 安全描述符太短。 |
The security descriptor is too short. |
| 0x20A2 | 安全描述符无效。 |
The security descriptor is invalid. |
| 0x20A3 | 未能为删除的对象创建名称。 |
Failed to create name for deleted object. |
| 0x20A4 | 一个新子参考的父项必须存在。 |
The parent of a new subref must exist. |
| 0x20A5 | 该对象必须是一个命名上下文。 |
The object must be a naming context. |
| 0x20A6 | 不允许添加一个属于系统的属性。 |
It is not permitted to add an attribute which is owned by the system. |
| 0x20A7 | 对象的类必须是有结构的；你不能范例化一个抽象类。 |
The class of the object must be structural; you cannot instantiate an abstract class. |
| 0x20A8 | 找不到架构的对象。 |
The schema object could not be found. |
| 0x20A9 | 有这个 GUID (非活动的或活动的)的本地对象已经存在。 |
A local object with this GUID (dead or alive) already exists. |
| 0x20AA | 操作不能在一个后部链接上执行。 |
The operation cannot be performed on a back link. |
| 0x20AB | 找不到指定的命名上下文的互交参考。 |
The cross reference for the specified naming context could not be found. |
| 0x20AC | 由于目录服务关闭，操作不能执行。 |
The operation could not be performed because the directory service is shutting down. |
| 0x20AD | 目录服务请求无效。 |
The directory service request is invalid. |
| 0x20AE | 无法读取角色所有者属性。 |
The role owner attribute could not be read. |
| 0x20AF | 请求的 FSMO 操作失败。不能连接当前的 FSMO 盒。 |
The requested FSMO operation failed. The current FSMO holder could not be contacted. |
| 0x20B0 | 不允许跨过一个命名上下文修改 DN。 |
Modification of a DN across a naming context is not permitted. |
| 0x20B1 | 由于属于系统，不能修改该属性。 |
The attribute cannot be modified because it is owned by the system. |
| 0x20B2 | 只有复制器可以执行这个功能。 |
Only the replicator can perform this function. |
| 0x20B3 | 指定的类没有定义。 |
The specified class is not defined. |
| 0x20B4 | 指定的类不是一个子类。 |
The specified class is not a subclass. |
| 0x20B5 | 名称参照无效。 |
The name reference is invalid. |
| 0x20B6 | 交叉参照已经存在。 |
A cross reference already exists. |
| 0x20B7 | 不允许删除一个主控交叉参照。 |
It is not permitted to delete a master cross reference. |
| 0x20B8 | 只在 NC 头上支持子树通知。 |
Subtree notifications are only supported on NC heads. |
| 0x20B9 | 通知筛选器太复杂。 |
Notification filter is too complex. |
| 0x20BA | 架构更新失败: 重复的 RDN。 |
Schema update failed: duplicate RDN. |
| 0x20BB | 架构更新失败: 重复的 OID。 |
Schema update failed: duplicate OID. |
| 0x20BC | 架构更新失败: 重复的 MAPI 标识符。 |
Schema update failed: duplicate MAPI identifier. |
| 0x20BD | 架构更新失败: 复制架构 id GUID。 |
Schema update failed: duplicate schema-id GUID. |
| 0x20BE | 架构更新失败: 重复的 LDAP 显示名称。 |
Schema update failed: duplicate LDAP display name. |
| 0x20BF | 架构更新失败: 范围下部少于范围上部。 |
Schema update failed: range-lower less than range upper. |
| 0x20C0 | 架构更新失败: 语法不匹配。 |
Schema update failed: syntax mismatch. |
| 0x20C1 | 架构更新失败: 属性在必须包含中使用。 |
Schema deletion failed: attribute is used in must-contain. |
| 0x20C2 | 架构更新失败: 属性在可能包含中使用。 |
Schema deletion failed: attribute is used in may-contain. |
| 0x20C3 | 架构更新失败: 可能包含中的属性不存在。 |
Schema update failed: attribute in may-contain does not exist. |
| 0x20C4 | 架构更新失败:必须包含中的属性不存在。 |
Schema update failed: attribute in must-contain does not exist. |
| 0x20C5 | 架构更新失败: 在辅助类列表中的类不存在或不是一个辅助类。 |
Schema update failed: class in aux-class list does not exist or is not an auxiliary class. |
| 0x20C6 | 架构更新失败: poss-superiors 中的类不存在。 |
Schema update failed: class in poss-superiors does not exist. |
| 0x20C7 | 架构更新失败: 在 subclassof 列表中的类不存在或不能满足等级规则。 |
Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules. |
| 0x20C8 | 架构更新失败: Rdn-Att-Id 语法不对。 |
Schema update failed: Rdn-Att-Id has wrong syntax. |
| 0x20C9 | 架构更新失败: 类作为辅助类使用。 |
Schema deletion failed: class is used as auxiliary class. |
| 0x20CA | 架构更新失败: 类作为子类使用。 |
Schema deletion failed: class is used as sub class. |
| 0x20CB | 架构更新失败: 类作为 poss superior 使用。 |
Schema deletion failed: class is used as poss superior. |
| 0x20CC | 架构更新在重新计算验证缓存时失败。 |
Schema update failed in recalculating validation cache. |
| 0x20CD | 目录树删除没有完成。要继续删除目录树，必须再次发出请求。 |
The tree deletion is not finished. The request must be made again to continue deleting the tree. |
| 0x20CE | 不能执行请求的删除操作。 |
The requested delete operation could not be performed. |
| 0x20CF | 不能读取架构记录管理类标识符。 |
Cannot read the governs class identifier for the schema record. |
| 0x20D0 | 属性架构语法不对。 |
The attribute schema has bad syntax. |
| 0x20D1 | 不能缓存属性。 |
The attribute could not be cached. |
| 0x20D2 | 不能缓存类。 |
The class could not be cached. |
| 0x20D3 | 不能从缓存删除属性。 |
The attribute could not be removed from the cache. |
| 0x20D4 | 无法从缓存中删除类。 |
The class could not be removed from the cache. |
| 0x20D5 | 无法读取可分辨名称的属性。 |
The distinguished name attribute could not be read. |
| 0x20D6 | 目录服务没有配置上级参照。因此目录服务无法为此林之外的对象颁发参照。 |
No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest. |
| 0x20D7 | 不能检索实例类型属性。 |
The instance type attribute could not be retrieved. |
| 0x20D8 | 发生一个内部错误。 |
An internal error has occurred. |
| 0x20D9 | 出现了一个数据库错误。 |
A database error has occurred. |
| 0x20DA | 找不到属性 GOVERNSID。 |
The attribute GOVERNSID is missing. |
| 0x20DB | 找不到需要的属性。 |
An expected attribute is missing. |
| 0x20DC | 指定的命名上下文丢失了一个交叉参考。 |
The specified naming context is missing a cross reference. |
| 0x20DD | 出现了一个安全检查错误。 |
A security checking error has occurred. |
| 0x20DE | 没有加载架构。 |
The schema is not loaded. |
| 0x20DF | 架构分配失败。请检查计算机内存是否不足。 |
Schema allocation failed. Please check if the machine is running low on memory. |
| 0x20E0 | 未能为属性架构获得所需语法。 |
Failed to obtain the required syntax for the attribute schema. |
| 0x20E1 | 全局目录验证失败。全局目录不可用或不支持操作。目录的某些部分目前不可用。 |
The 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. |
| 0x20E2 | 由于有关服务器之间的架构不匹配，复制操作失败。 |
The replication operation failed because of a schema mismatch between the servers involved. |
| 0x20E3 | 找不到 DSA 对象。 |
The DSA object could not be found. |
| 0x20E4 | 找不到命名上下文。 |
The naming context could not be found. |
| 0x20E5 | 在缓存中找不到命名上下文。 |
The naming context could not be found in the cache. |
| 0x20E6 | 无法检索子对象。 |
The child object could not be retrieved. |
| 0x20E7 | 由于安全原因不允许修改。 |
The modification was not permitted for security reasons. |
| 0x20E8 | 操作不能替换隐藏的记录。 |
The operation cannot replace the hidden record. |
| 0x20E9 | 等级文件无效。 |
The hierarchy file is invalid. |
| 0x20EA | 未能构建等级表。 |
The attempt to build the hierarchy table failed. |
| 0x20EB | 注册表中缺少目录配置参数。 |
The directory configuration parameter is missing from the registry. |
| 0x20EC | 尝试计算通讯簿索引失败。 |
The attempt to count the address book indices failed. |
| 0x20ED | 等级表的分配失败。 |
The allocation of the hierarchy table failed. |
| 0x20EE | 目录服务遇到一个内部故障。 |
The directory service encountered an internal failure. |
| 0x20EF | 目录服务遇到一个未知故障。 |
The directory service encountered an unknown failure. |
| 0x20F0 | 根对象需要一个 'top' 类。 |
A root object requires a class of 'top'. |
| 0x20F1 | 这个目录服务器已关闭，并且不能接受新的浮动单主机操作角色的所有权。 |
This directory server is shutting down, and cannot take ownership of new floating single-master operation roles. |
| 0x20F2 | 目录服务没有必需的配置信息，并且不能决定新的浮动单主机操作角色的所有权。 |
The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles. |
| 0x20F3 | 该目录服务无法将一个或多个浮动单主机操作角色的所有权传送给其他服务器。 |
The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers. |
| 0x20F4 | 复制操作失败。 |
The replication operation failed. |
| 0x20F5 | 为这个复制操作指定了一个无效的参数。 |
An invalid parameter was specified for this replication operation. |
| 0x20F6 | 目录服务太忙，目前无法完成这个复制操作。 |
The directory service is too busy to complete the replication operation at this time. |
| 0x20F7 | 为这个复制操作指定的可分辨名称无效。 |
The distinguished name specified for this replication operation is invalid. |
| 0x20F8 | 为这个复制操作所指定的命名上下文无效。 |
The naming context specified for this replication operation is invalid. |
| 0x20F9 | 为这个复制操作指定的可分辨名称已经存在。 |
The distinguished name specified for this replication operation already exists. |
| 0x20FA | 复制系统遇到一个内部错误。 |
The replication system encountered an internal error. |
| 0x20FB | 复制操作遇到数据库不一致问题。 |
The replication operation encountered a database inconsistency. |
| 0x20FC | 不能连接到为这个复制操作指定的服务器上。 |
The server specified for this replication operation could not be contacted. |
| 0x20FD | 复制操作遇到一个有无效实例类型的对象。 |
The replication operation encountered an object with an invalid instance type. |
| 0x20FE | 复制操作无法分配内存。 |
The replication operation failed to allocate memory. |
| 0x20FF | 复制操作遇到一个邮件系统错误。 |
The replication operation encountered an error with the mail system. |
| 0x2100 | 目标服务器的复制参考信息已经存在。 |
The replication reference information for the target server already exists. |
| 0x2101 | 目标服务器的复制参考信息不存在。 |
The replication reference information for the target server does not exist. |
| 0x2102 | 由于是由另一台服务器上复制的，因此不能删除命名上下文。 |
The naming context cannot be removed because it is replicated to another server. |
| 0x2103 | 复制操作遇到一个数据库错误。 |
The replication operation encountered a database error. |
| 0x2104 | 命名上下文要被删除或没有从指定的服务器上复制。 |
The naming context is in the process of being removed or is not replicated from the specified server. |
| 0x2105 | 复制访问被拒绝。 |
Replication access was denied. |
| 0x2106 | 这个版本的目录服务不支持请求的操作。 |
The requested operation is not supported by this version of the directory service. |
| 0x2107 | 取消了复制远程过程调用。 |
The replication remote procedure call was cancelled. |
| 0x2108 | 源服务器目前拒绝复制请求。 |
The source server is currently rejecting replication requests. |
| 0x2109 | 目标服务器目前拒绝复制请求。 |
The destination server is currently rejecting replication requests. |
| 0x210A | 由于对象名称冲突，复制操作失败。 |
The replication operation failed due to a collision of object names. |
| 0x210B | 复制源已被重新安装。 |
The replication source has been reinstalled. |
| 0x210C | 由于一个所需父对象丢失，复制操作失败。 |
The replication operation failed because a required parent object is missing. |
| 0x210D | 复制操作被抢先。 |
The replication operation was preempted. |
| 0x210E | 由于缺乏更新，放弃复制同步尝试。 |
The replication synchronization attempt was abandoned because of a lack of updates. |
| 0x210F | 由于系统正在关闭，复制操作被中断。 |
The replication operation was terminated because the system is shutting down. |
| 0x2110 | 同步尝试失败，因为目标 DC 当前正在等待从源同步新的部分属性。如果最近架构更改修改了部分属性集，此状态正常。目标部分属性集不是源部分属性集的子集。 |
Synchronization 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. |
| 0x2111 | 由于主复制尝试从部分副本同步，复制同步尝试失败。 |
The replication synchronization attempt failed because a master replica attempted to sync from a partial replica. |
| 0x2112 | 已经与为这个复制操作的指定的服务器联系，但是该服务器无法与完成这个操作所需的另外一个服务器联系。 |
The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation. |
| 0x2113 | 源林的目录服务架构与这台计算机上的目录服务的版本不兼容。 |
The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer. |
| 0x2114 | 架构更新失败: 有同一链接标识符的属性已经存在。 |
Schema update failed: An attribute with the same link identifier already exists. |
| 0x2115 | 名称转换: 常见处理错误。 |
Name translation: Generic processing error. |
| 0x2116 | 名称转换: 不能找到该名称；或权限不够，无法看到名称。 |
Name translation: Could not find the name or insufficient right to see name. |
| 0x2117 | 名称转换: 输入名称映射到多个输出名称。 |
Name translation: Input name mapped to more than one output name. |
| 0x2118 | 名称转换: 找到了输出名称，但是找不到相应的输出格式。 |
Name translation: Input name found, but not the associated output format. |
| 0x2119 | 名称转换: 不能完全解析，只找到了域。 |
Name translation: Unable to resolve completely, only the domain was found. |
| 0x211A | 名称转换: 不接到线上，无法在客户端执行纯粹的语法映射。 |
Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire. |
| 0x211B | 不允许修改一个构造属性。 |
Modification of a constructed attribute is not allowed. |
| 0x211C | 指定的 OM-Object-Class 对具有指定语法的属性是不正确的。 |
The OM-Object-Class specified is incorrect for an attribute with the specified syntax. |
| 0x211D | 复制请求已暂停；等待回答。 |
The replication request has been posted; waiting for reply. |
| 0x211E | 要求的操作需要一个目录服务，但没有可用的。 |
The requested operation requires a directory service, and none was available. |
| 0x211F | 类或属性的 LDAP 显示名称含有非 ASCII 字符。 |
The LDAP display name of the class or attribute contains non-ASCII characters. |
| 0x2120 | 请求的搜索操作只支持基本查找。 |
The requested search operation is only supported for base searches. |
| 0x2121 | 搜索未能从数据库检索属性。 |
The search failed to retrieve attributes from the database. |
| 0x2122 | 架构更新操作试图添加一个反向链接，但该反向链接属性没有相应的正向链接。 |
The schema update operation tried to add a backward link attribute that has no corresponding forward link. |
| 0x2123 | 跨域移动的来源和目标在对象日期上不一致。或者是来源，或者是目标没有对象的最新版本。 |
Source 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. |
| 0x2124 | 跨域移动的来源和目标在对象当前的名称上不一致。或者是来源，或者是目标没有对象的最新版本。 |
Source 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. |
| 0x2125 | 跨域移动的来源和目标是一样的。调用程序应该使用本地移动操作，而不是跨域移动操作。 |
Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation. |
| 0x2126 | 跨域移动的来源和目标与林中的命名上下文不一致。来源或目标没有分区容器的最新版本。 |
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. |
| 0x2127 | 跨域移动的目标不是目标命名上下文的权威。 |
Destination of a cross-domain move is not authoritative for the destination naming context. |
| 0x2128 | 跨域移动的来源和目标提供的来源对象的身份不一样。来源或目标没有来源对象的最近版本。 |
Source 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. |
| 0x2129 | 跨域移动的对象应该已经被目标服务器删除。来源服务器没有来源对象的最近版本。 |
Object 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. |
| 0x212A | 要求对 PDC FSMO 的专门访问权的另一个操作正在进行中。 |
Another operation which requires exclusive access to the PDC FSMO is already in progress. |
| 0x212B | 跨域移动没有成功，导致被移动对象有两个版本 - 一个在来源域，一个在目标域。需要删除目标对象，将系统还原到一致状态。 |
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. |
| 0x212C | 因为不允许跨域移动这个类，或者对象有一些特点，如: 信任帐户或防止移动的受限制的 RID；所以不能将该对象跨域移动。 |
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. |
| 0x212D | 一旦移动，不能将带有成员身份的对象跨域移动，这会侵犯帐户组的成员身份条件。从帐户组成员身份删除对象，再试一次。 |
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. |
| 0x212E | 命名上下文标题必须是另一个命名上下文标题的直接子标题，而不是一个内节点的子标题。 |
A naming context head must be the immediate child of another naming context head, not of an interior node. |
| 0x212F | 因为目录没有提议的命名上下文上面的命名上下文的副本，所以无法验证所提议的命名上下文的名称。请保证充当域命名主机的服务器已配置成全局目录服务器，并且服务器及其复制伙伴是最新的。(仅适用于 Windows 2000 域命名主机) |
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) |
| 0x2130 | 目标域必须在纯模式中。 |
Destination domain must be in native mode. |
| 0x2131 | 因为服务器在指定域中没有基础结构容器，所以无法执行操作。 |
The operation cannot be performed because the server does not have an infrastructure container in the domain of interest. |
| 0x2132 | 不允许跨域移动不是空的帐户组。 |
Cross-domain move of non-empty account groups is not allowed. |
| 0x2133 | 不允许跨域移动不是空的资源组。 |
Cross-domain move of non-empty resource groups is not allowed. |
| 0x2134 | 属性的搜索标志无效。ANR 位只在 Unicode 或 Teletex 字符串的属性上有效。 |
The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings. |
| 0x2135 | 不允许在将 NC 头作为后代的对象开始删除目录树。 |
Tree deletions starting at an object which has an NC head as a descendant are not allowed. |
| 0x2136 | 因为目录树在使用中，目录服务未能为删除目录树而将其锁定。 |
The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use. |
| 0x2137 | 删除目录树时，目录服务未能识别要删除的对象列表。 |
The directory service failed to identify the list of objects to delete while attempting a tree deletion. |
| 0x2138 | 安全帐户管理器初始化失败，原因如下: %1。错误状态: 0x%2。请关闭该系统并重新启动到目录服务还原模式。有关详细信息，请检查事件日志。 |
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. |
| 0x2139 | 只有管理员才能修改管理组的成员列表。 |
Only an administrator can modify the membership list of an administrative group. |
| 0x213A | 不能更改域控制器帐户的主要组 ID。 |
Cannot change the primary group ID of a domain controller account. |
| 0x213B | 试图修改基础架构。 |
An attempt is made to modify the base schema. |
| 0x213C | 不允许进行下列操作: 为现有类添加新的强制属性；从现有类删除强制属性；为没有向回链接属性的特殊类 \"Top\" 添加可选属性，向回链接属性指的是直接或通过继承。例如: 添加或删除附属类。 |
Adding 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. |
| 0x213D | 由于 DC 不是架构 FSMO 角色所有者，该域控制器上不允许架构更新。 |
Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner. |
| 0x213E | 无法在架构容器下创建这个类的对象。在架构容器下，你只能创建属性架构和类架构对象。 |
An 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. |
| 0x213F | 副本/子项安装未能获取源 DC 上的架构容器的 objectVersion 属性。架构容器上的属性不存在，或者提供的凭证没有权限读取属性。 |
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. |
| 0x2140 | 副本/子项安装未能读取 system32 目录中的文件 schema.ini 的 SCHEMA 段中的 objectVersion 属性。 |
The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory. |
| 0x2141 | 指定的组类型无效。 |
The specified group type is invalid. |
| 0x2142 | 如果域是安全启用的，在混合型域中不能嵌套全局组。 |
You cannot nest global groups in a mixed domain if the group is security-enabled. |
| 0x2143 | 如果域是安全启用的，在混合型域中不能嵌套本地组。 |
You cannot nest local groups in a mixed domain if the group is security-enabled. |
| 0x2144 | 全局组不能将本地组作为成员。 |
A global group cannot have a local group as a member. |
| 0x2145 | 全局组不能将通用组作为成员。 |
A global group cannot have a universal group as a member. |
| 0x2146 | 通用组不能将本地组作为成员。 |
A universal group cannot have a local group as a member. |
| 0x2147 | 全局组不能有跨域成员。 |
A global group cannot have a cross-domain member. |
| 0x2148 | 本地组不能将另一个跨域本地组作为成员。 |
A local group cannot have another cross domain local group as a member. |
| 0x2149 | 包含主要成员的组不能更改为安全停用的组。 |
A group with primary members cannot change to a security-disabled group. |
| 0x214A | 架构缓存加载未能转换类架构对象上的字符串默认值 SD。 |
The schema cache load failed to convert the string default SD on a class-schema object. |
| 0x214B | 只有配置成全局目录服务器的 DSAs 才能充当域命名主机 FSMO 的角色。(仅适用于 Windows 2000 服务器) |
Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers) |
| 0x214C | 由于 DNS 查找故障，DSA 操作无法进行。 |
The DSA operation is unable to proceed because of a DNS lookup failure. |
| 0x214D | 处理一个对象的 DNS 主机名更改时，服务主要名称数值无法保持同步。 |
While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync. |
| 0x214E | 未能读取安全描述符属性。 |
The Security Descriptor attribute could not be read. |
| 0x214F | 找不到请求的对象，但找到了具有那个密钥的对象。 |
The object requested was not found, but an object with that key was found. |
| 0x2150 | 正在添加的链接属性的语法不正确。正向链接只能有语法 2.5.5.1、2.5.5.7 和 2.5.5.14，而反向链接只能有语法 2.5.5.1 |
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 |
| 0x2151 | 安全帐户管理员需要获得启动密码。 |
Security Account Manager needs to get the boot password. |
| 0x2152 | 安全帐户管理员需要从软盘获得启动密钥。 |
Security Account Manager needs to get the boot key from floppy disk. |
| 0x2153 | 目录服务无法启动。 |
Directory Service cannot start. |
| 0x2154 | 目录服务未能启动。 |
Directory Services could not start. |
| 0x2155 | 客户端和服务器之间的连接要求数据包保密性。 |
The connection between client and server requires packet privacy or better. |
| 0x2156 | 来源域跟目标域不在同一个林中。 |
The source domain may not be in the same forest as destination. |
| 0x2157 | 目标域必须在林中。 |
The destination domain must be in the forest. |
| 0x2158 | 该操作要求启用目标域审核。 |
The operation requires that destination domain auditing be enabled. |
| 0x2159 | 该操作无法找到来源域的 DC。 |
The operation couldn't locate a DC for the source domain. |
| 0x215A | 来源对象必须是一个组或用户。 |
The source object must be a group or user. |
| 0x215B | 来源对象的 SID 已经在目标林中。 |
The source object's SID already exists in destination forest. |
| 0x215C | 来源对象和目标对象必须属于同一类型。 |
The source and destination object must be of the same type. |
| 0x215D | 安全帐户管理器初始化没有成功，原因是以下错误: %1。错误状态: 0x%2。要关闭系统并重新启动到安全模式，请单击“确定”。有关详细信息，请检查事件日志。 |
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. |
| 0x215E | 在复制请求中不能包括架构信息。 |
Schema information could not be included in the replication request. |
| 0x215F | 由于架构不兼容性，无法完成复制操作。 |
The replication operation could not be completed due to a schema incompatibility. |
| 0x2160 | 由于前一个架构的不兼容性，无法完成复制操作。 |
The replication operation could not be completed due to a previous schema incompatibility. |
| 0x2161 | 因为源或目标没有收到有关最近跨域启动操作的信息，所以无法应用复制更新。 |
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. |
| 0x2162 | 因为还有主控这个域的域控制器，所以无法删除请求的域。 |
The requested domain could not be deleted because there exist domain controllers that still host this domain. |
| 0x2163 | 只能在全局编录服务器上执行请求的操作。 |
The requested operation can be performed only on a global catalog server. |
| 0x2164 | 本地组只能是同一个域中其他本地组的成员。 |
A local group can only be a member of other local groups in the same domain. |
| 0x2165 | 外部安全主体不能是通用组的成员。 |
Foreign security principals cannot be members of universal groups. |
| 0x2166 | 出于安全，无法将属性复制到 GC。 |
The attribute is not allowed to be replicated to the GC because of security reasons. |
| 0x2167 | 由于目前正在处理的修改太多，无法采取 PDC 的检查点。 |
The checkpoint with the PDC could not be taken because there too many modifications being processed currently. |
| 0x2168 | 操作需要启用那个源域审核。 |
The operation requires that source domain auditing be enabled. |
| 0x2169 | 安全主要对象仅能在域命名环境菜单中创建。 |
Security principal objects can only be created inside domain naming contexts. |
| 0x216A | 服务主要名称(SPN)无法建造，因为提供的主机名格式不适合。 |
A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format. |
| 0x216B | 筛选器已传递建造的属性。 |
A Filter was passed that uses constructed attributes. |
| 0x216C | unicodePwd 属性值必须括在双引号中。 |
The unicodePwd attribute value must be enclosed in double quotes. |
| 0x216D | 你的计算机无法加入域。已超出此域所允许创建的计算机帐户的最大值。请跟系统管理员联系，以便重置或增加此限制。 |
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. |
| 0x216E | 由于安全原因，操作必须在目标 DC 上运行。 |
For security reasons, the operation must be run on the destination DC. |
| 0x216F | 由于安全原因，源 DC 必须是 NT4SP4 或更新版本。 |
For security reasons, the source DC must be NT4SP4 or greater. |
| 0x2170 | 在树目录删除的操作中不能删除“关键目录服务系统”对象。数目录删除操作可能只进行了一部分。 |
Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed. |
| 0x2171 | 不能开始目录服务，因为以下错误: %1.错误状态: 0x%2. 请单击 OK 来关闭系统。你可用恢复控制台来进一步诊断系统。 |
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. |
| 0x2172 | 安全帐户管理器初始化失败，因为以下错误: %1.错误状态: 0x%2. 请单击 OK 来关闭系统。你可用恢复控制台来进一步诊断系统。 |
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. |
| 0x2173 | 此版本的操作系统与当前 AD DS 林功能级别或 AD LDS 配置集功能级别不兼容。你必须升级到新版本的操作系统才能使此服务器成为 AD DS 域控制器或将 AD LDS 实例添加到此 AD DS 林或 AD LDS 配置集中。 |
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. |
| 0x2174 | 安装的操作系统的版本与当前域功能级别不兼容，要使此服务器成为域中域控制器之前，你必须升级到操作系统的新版本。 |
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. |
| 0x2175 | 此服务器上安装的操作系统版本不再支持当前 AD DS 林功能级别或 AD LDS 配置集功能级别。你必须提升 AD DS 林功能级别或 AD LDS 配置集功能级别才能使此服务器成为 AD DS 域控制器或将 AD LDS 实例添加到该林或配置集中。 |
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. |
| 0x2176 | 此服务器上安装的操作系统的版本不再支持当前域功能级别。要使此服务器成为域中域控制器之前，你必须提升域功能级别。 |
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. |
| 0x2177 | 此服务器上安装的操作系统的版本与当前域或林的功能级别不兼容。 |
The version of the operating system installed on this server is incompatible with the functional level of the domain or forest. |
| 0x2178 | 不能提升此域 (或林) 的功能级别到请求的值，因为域 (或林) 中的已存在一个或多个域控制器处于较低的不兼容功能级别。 |
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. |
| 0x2179 | 不能提升此林功能级别到请求的值，因为一个或多个域仍处于混合域模式。林中所有的域必须处于纯模式以提升林功能级别。 |
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. |
| 0x217A | 请求的排序方式不受支持。 |
The sort order requested is not supported. |
| 0x217B | 请求的名称是已经存在的唯一标识符。 |
The requested name already exists as a unique identifier. |
| 0x217C | 计算机帐户是由 NT4 之前的版本创建的。需要重新创建该帐户。 |
The machine account was created pre-NT4. The account needs to be recreated. |
| 0x217D | 数据库在版本存储之外。 |
The database is out of version store. |
| 0x217E | 无法继续操作，因为用了多个冲突控制。 |
Unable to continue operation because multiple conflicting controls were used. |
| 0x217F | 无法找到这个分区的有效安全描述符参考域。 |
Unable to find a valid security descriptor reference domain for this partition. |
| 0x2180 | 架构更新失败: 链接标识符被保留。 |
Schema update failed: The link identifier is reserved. |
| 0x2181 | 架构更新失败: 链接标识符不可用。 |
Schema update failed: There are no link identifiers available. |
| 0x2182 | 帐户组无法将通用组作为成员。 |
An account group cannot have a universal group as a member. |
| 0x2183 | 不允许在命名上下文标题或只读对象上重新命名或移动操作。 |
Rename or move operations on naming context heads or read-only objects are not allowed. |
| 0x2184 | 不允许在架构命名上下文里的对象上移动操作。 |
Move operations on objects in the schema naming context are not allowed. |
| 0x2185 | 已在对象上设置系统标记并不允许移动或重新命名该对象。 |
A system flag has been set on the object and does not allow the object to be moved or renamed. |
| 0x2186 | 不允许此对象改更改它的祖容器。在此对象上不禁止移动，但限制于移到兄弟容器。 |
This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers. |
| 0x2187 | 无法完全分解，生成对另一林的检索。 |
Unable to resolve completely, a referral to another forest is generated. |
| 0x2188 | 请求的操作在标准服务器上不受支持。 |
The requested action is not supported on standard server. |
| 0x2189 | 不能访问远程服务器上的目录服务的分区。请确保至少有一个服务器在为该分区运行。 |
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. |
| 0x218A | 目录不能验证推荐的命名上下文(或分区)名称，因为它没有副本并且不能联系推荐的命名上下文之上的命名上下文副本。请确保该父命名上下文在 DNS 里的配置正确，并且域命名主机至少可以到达这个命名一个副本。 |
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. |
| 0x218B | 已超出该请求线程的限制。 |
The thread limit for this request was exceeded. |
| 0x218C | 全局目录服务器不在最近的站点。 |
The Global catalog server is not in the closest site. |
| 0x218D | DS 不能派生用之以相互给目标服务器验证身份的服务主要名称(SPN)，这是因为在本地 DS 数据库中与之相对应的服务器对象没有 serverReference 属性。 |
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. |
| 0x218E | 目录服务无法进入单一用户模式。 |
The Directory Service failed to enter single user mode. |
| 0x218F | 由于语法错误，目录服务无法分析此脚本。 |
The Directory Service cannot parse the script because of a syntax error. |
| 0x2190 | 由于发生错误，目录服务无法分解此脚本。 |
The Directory Service cannot process the script because of an error. |
| 0x2191 | 由于涉及的服务器处于不同的复制时期(通常与正在进行的域重命名有关)，目录服务无法执行请求的操作。 |
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). |
| 0x2192 | 由于服务器扩展名信息更改，必须重新协商目录服务绑定。 |
The directory service binding must be renegotiated due to a change in the server extensions information. |
| 0x2193 | 不允许在禁用的交叉引用上操作。 |
Operation not allowed on a disabled cross ref. |
| 0x2194 | 架构更新失败: 没有 msDS-IntId 的值。 |
Schema update failed: No values for msDS-IntId are available. |
| 0x2195 | 架构更新失败: msDS-INtId 已存在。重新尝试此操作。 |
Schema update failed: Duplicate msDS-INtId. Retry the operation. |
| 0x2196 | 架构删除失败: 属性在 rDNAttID 中使用。 |
Schema deletion failed: attribute is used in rDNAttID. |
| 0x2197 | 目录服务无法对此请求进行身份验证。 |
The directory service failed to authorize the request. |
| 0x2198 | 脚本无效，目录服务无法分解此脚本。 |
The Directory Service cannot process the script because it is invalid. |
| 0x2199 | 在域命名主机 FSMO 上的远程创建交叉引用的操作失败。操作的错误在扩展数据中。 |
The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data. |
| 0x219A | 交叉参照已经在本地使用而且名称相同。 |
A cross reference is in use locally with the same name. |
| 0x219B | DS 不能派生用之以相互给目标服务器验证身份的服务主要名称(SPN)，因为已经从林中删除了服务器的域。 |
The 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. |
| 0x219C | 可写 NCs 阻碍了此 DC 降级。 |
Writeable NCs prevent this DC from demoting. |
| 0x219D | 请求的对象包含非唯一标识符而且无法检索。 |
The requested object has a non-unique identifier and cannot be retrieved. |
| 0x219E | 没有给定足够的属性以创建对象。这个对象可能不存在因为它可能已经删除域垃圾收集。 |
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected. |
| 0x219F | 由于请求的组类型上属性的限制，组不能被转换。 |
The group cannot be converted due to attribute restrictions on the requested group type. |
| 0x21A0 | 不允许非空的基本应用程序组的跨域移动。 |
Cross-domain move of non-empty basic application groups is not allowed. |
| 0x21A1 | 不允许非空的基于查询的应用程序组的跨域移动。 |
Cross-domain move of non-empty query based application groups is not allowed. |
| 0x21A2 | 无法验证 FSMO 角色所有权，因为尚未使用至少一个复制伙伴成功地复制其目录分区。 |
The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner. |
| 0x21A3 | 已知对象容器的重定向的目标容器不能是特殊容器。 |
The target container for a redirection of a well known object container cannot already be a special container. |
| 0x21A4 | 目录服务不能执行请求的操作因为正在进行域重命名操作。 |
The Directory Service cannot perform the requested operation because a domain rename operation is in progress. |
| 0x21A5 | 目录服务检测到下列子分区请求新分区名。目录服务的分区等级必须自上而下创建。 |
The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method. |
| 0x21A6 | 目录服务不能与此服务器复制，因为距上一次与此服务器复制的时间已经超过了 tombstone 生存时间。 |
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime. |
| 0x21A7 | 不允许在系统容器下的对象上执行请求的操作。 |
The requested operation is not allowed on an object under the system container. |
| 0x21A8 | LDAP 服务器网络发送队列已满，原因是客户端处理其请求的结果不够快。除非客户端的速度能跟上，否则不会处理更多的请求。如果客户端的速度跟不上，那么它将被断开连接。 |
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. |
| 0x21A9 | 计划的复制没有发生，因为系统太忙，不能在计划窗口内执行请求。复制队列超载。请考虑缩小伙伴的数量或减少计划的复制频率。 |
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. |
| 0x21AA | 现在无法确定分支复制策略在中心域控制器上是否可用。请稍后重试以解释复制延迟的原因。 |
At 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. |
| 0x21AB | 指定站点的站点设置对象不存在。 |
The site settings object for the specified site does not exist. |
| 0x21AC | 本地帐户存储不包含指定帐户的秘密材料。 |
The local account store does not contain secret material for the specified account. |
| 0x21AD | 域中无法找到可写入的域控制器。 |
Could not find a writable domain controller in the domain. |
| 0x21AE | 域控制器的服务器对象不存在。 |
The server object for the domain controller does not exist. |
| 0x21AF | 域控制器的 NTDS 设置对象不存在。 |
The NTDS Settings object for the domain controller does not exist. |
| 0x21B0 | 不支持将请求的搜索操作用于 ASQ 搜索。 |
The requested search operation is not supported for ASQ searches. |
| 0x21B1 | 无法为操作生成请求的审核事件。 |
A required audit event could not be generated for the operation. |
| 0x21B2 | 属性的搜索标志无效。子树索引位仅在单个值的属性上有效。 |
The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes. |
| 0x21B3 | 属性的搜索标志无效。元组索引位仅在 Unicode 字符串的属性上有效。 |
The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings. |
| 0x21B4 | 通讯簿嵌套过深。无法构建层次结构表。 |
The address books are nested too deeply. Failed to build the hierarchy table. |
| 0x21B5 | 指定的最新矢量已损坏。 |
The specified up-to-date-ness vector is corrupt. |
| 0x21B6 | 复制机密的请求被拒绝。 |
The request to replicate secrets is denied. |
| 0x21B7 | 架构更新失败: MAPI 标识符已保留。 |
Schema update failed: The MAPI identifier is reserved. |
| 0x21B8 | 架构更新失败: 没有可用的 MAPI 标识符。 |
Schema update failed: There are no MAPI identifiers available. |
| 0x21B9 | 复制操作失败，因为本地 krbtgt 对象所需的属性丢失。 |
The replication operation failed because the required attributes of the local krbtgt object are missing. |
| 0x21BA | 在林中已存在受信任域的域名。 |
The domain name of the trusted domain already exists in the forest. |
| 0x21BB | 在林中已存在受信任域的平面名称。 |
The flat name of the trusted domain already exists in the forest. |
| 0x21BC | 用户主体名称(UPN)无效。 |
The User Principal Name (UPN) is invalid. |
| 0x21BD | OID 映射组不能具有成员。 |
OID mapped groups cannot have members. |
| 0x21BE | 无法找到指定的 OID。 |
The specified OID cannot be found. |
| 0x21BF | 复制操作失败，因为链接值引用的目标对象被回收。 |
The replication operation failed because the target object referred by a link value is recycled. |
| 0x21C0 | 无法进行重定向操作，原因是目标对象所处的 NC 与当前域控制器的域 NC 不同。 |
The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller. |
| 0x21C1 | AD LDS 配置集的功能级别无法降低为要求的值。 |
The functional level of the AD LDS configuration set cannot be lowered to the requested value. |
| 0x21C2 | 域 (或林) 的功能级别无法降低到所需的值。 |
The functional level of the domain (or forest) cannot be lowered to the requested value. |
| 0x21C3 | AD LDS 配置集的功能级别无法升高到所需的值，原因是存在一个或多个处于更低的不兼容功能级别的 ADLDS 实例。 |
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. |
| 0x21C4 | 无法完成域加入，原因是试图加入的域的 SID 与本计算机的 SID 相同。未正确克隆的操作系统安装会出现这种情况。你应该在本计算机上运行 sysprep，以便生成一个新的计算机 SID。有关详细信息，请参阅 http://go.microsoft.com/fwlink/?LinkId=168895。 |
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. |
| 0x21C5 | 无法进行取消删除操作，原因是正在取消删除的对象的 Sam 帐户名称或附加 Sam 帐户名称与现有的活动对象发生冲突。 |
The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object. |
| 0x21C6 | 该系统对指定的帐户没有授权，因此无法完成此操作。请使用与此帐户相关联的提供程序重新尝试操作。如果这是联机提供程序，请使用提供程序的联机站点。 |
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. |
| 0x21C7 | 操作失败，因为向进行添加/修改而提供的 SPN 值不是全林唯一的。 |
The operation failed because SPN value provided for addition/modification is not unique forest-wide. |
| 0x21C8 | 操作失败，因为向进行添加/修改而提供的 UPN 值不是全林唯一的。 |
The operation failed because UPN value provided for addition/modification is not unique forest-wide. |
| 0x21C9 | 操作失败，因为添加/修改操作引用了一个不存在的入站林级信任。 |
The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present. |
| 0x21CA | 找不到指定的链接值，但找到了具有该键的链接值。 |
The link value specified was not found, but a link value with that key was found. |
| 0x2329 | DNS 服务器无法解释格式。 |
DNS server unable to interpret format. |
| 0x232A | DNS 服务器失败。 |
DNS server failure. |
| 0x232B | DNS 名称不存在。 |
DNS name does not exist. |
| 0x232C | 名称服务器不支持 DNS 请求。 |
DNS request not supported by name server. |
| 0x232D | 拒绝 DNS 操作。 |
DNS operation refused. |
| 0x232E | 不应该存在的 DNS 名称仍然存在。 |
DNS name that ought not exist, does exist. |
| 0x232F | 不应该存在的 DNS RR 集仍然存在。 |
DNS RR set that ought not exist, does exist. |
| 0x2330 | 应该存在的 DNS RR 集不存在。 |
DNS RR set that ought to exist, does not exist. |
| 0x2331 | DNS 服务器对区域没有权威。 |
DNS server not authoritative for zone. |
| 0x2332 | 在更新或 prereq 中的 DNS 名称不在区域中。 |
DNS name in update or prereq is not in zone. |
| 0x2338 | DNS 签名验证失败。 |
DNS signature failed to verify. |
| 0x2339 | DNS 不正确密钥。 |
DNS bad key. |
| 0x233A | DNS 签名验证过期。 |
DNS signature validity expired. |
| 0x238D | 只有作为该区域密钥主机的 DNS 服务器可以执行此操作。 |
Only the DNS server acting as the key master for the zone may perform this operation. |
| 0x238E | 不允许在已签名或包含签名密钥的区域上执行此操作。 |
This operation is not allowed on a zone that is signed or has signing keys. |
| 0x238F | NSEC3 与 RSA-SHA-1 算法不兼容。请选择其他算法或使用 NSEC。 |
NSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC. |
| 0x2390 | 此区域没有足够的签名密钥。必须至少有一个密钥签名密钥(KSK)和一个区域签名密钥(ZSK)。 |
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). |
| 0x2391 | 指定的算法不受支持。 |
The specified algorithm is not supported. |
| 0x2392 | 指定的密钥大小不受支持。 |
The specified key size is not supported. |
| 0x2393 | DNS 服务器无法访问区域的一个或多个签名密钥。在解决此错误之前，区域签名将不起作用。 |
One 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. |
| 0x2394 | 指定的密钥存储提供程序不支持 DPAPI++ 数据保护。在解决此问题之前，区域签名将不起作用。 |
The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved. |
| 0x2395 | 遇到意外的 DPAPI++ 错误。在解决此问题之前，区域签名将不起作用。 |
An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved. |
| 0x2396 | 遇到意外的加密错误。在解决此问题之前，区域签名可能不起作用。 |
An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved. |
| 0x2397 | DNS 服务器遇到版本未知的签名密钥。在解决此错误之前，区域签名将不起作用。 |
The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved. |
| 0x2398 | DNS 服务器无法打开指定的密钥服务提供程序。 |
The specified key service provider cannot be opened by the DNS server. |
| 0x2399 | DNS 服务器无法接受更多具有指定算法的签名密钥，以及用于此区域的 KSK 标志值。 |
The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone. |
| 0x239A | 指定的翻转期无效。 |
The specified rollover period is invalid. |
| 0x239B | 指定的初始翻转偏差无效。 |
The specified initial rollover offset is invalid. |
| 0x239C | 指定的签名密钥已在密钥翻转过程中。 |
The specified signing key is already in process of rolling over keys. |
| 0x239D | 指定的签名密钥没有要注销的备用密钥。 |
The specified signing key does not have a standby key to revoke. |
| 0x239E | 不允许对区域签名密钥(ZSK)执行此操作。 |
This operation is not allowed on a zone signing key (ZSK). |
| 0x239F | 不允许对活动的签名密钥执行此操作。 |
This operation is not allowed on an active signing key. |
| 0x23A0 | 指定的签名密钥已列入滚动队列中。 |
The specified signing key is already queued for rollover. |
| 0x23A1 | 不允许对未签名的区域执行此操作。 |
This operation is not allowed on an unsigned zone. |
| 0x23A2 | 无法完成此操作，原因是列为该区域当前密钥主机的 DNS 服务器已停机或配置错误。请解决此区域当前密钥主机上的问题或使用另一个 DNS 服务器来获取密钥主机角色。 |
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. |
| 0x23A3 | 指定的签名有效期无效。 |
The specified signature validity period is invalid. |
| 0x23A4 | 指定的 NSEC3 迭代计数高于区域中使用的最小密钥长度所允许的迭代计数。 |
The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone. |
| 0x23A5 | 无法完成此操作，原因是 DNS 服务器已配置为禁用 DNSSEC 功能。在 DNS 服务器上启用 DNSSEC。 |
This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server. |
| 0x23A6 | 无法完成此操作，原因是接收到的 XML 流为空或在语法上无效。 |
This operation could not be completed because the XML stream received is empty or syntactically invalid. |
| 0x23A7 | 此操作已完成，但是没有添加信任密钥，原因是接收到的所有信任密钥均无效、不受支持、过期或无法在 30 天内变为有效。 |
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. |
| 0x23A8 | 指定的签名密钥未等待父 DS 更新。 |
The specified signing key is not waiting for parental DS update. |
| 0x23A9 | 在 NSEC3 签名期间检测到哈希冲突。指定其他用户提供的加密盐或使用随机生成的加密盐，然后尝试再次登录该区域。 |
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. |
| 0x23AA | NSEC 与 NSEC3-RSA-SHA-1 算法不兼容。请选择其他算法或使用 NSEC3。 |
NSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3. |
| 0x251D | 为 DNS 查询找不到记录。 |
No records found for given DNS query. |
| 0x251E | 不正确的 DNS 包。 |
Bad DNS packet. |
| 0x251F | 没有 DNS 包。 |
No DNS packet. |
| 0x2520 | DNS 错误，请检查 rcode。 |
DNS error, check rcode. |
| 0x2521 | 没有保险的 DNS 包。 |
Unsecured DNS packet. |
| 0x2522 | DNS 查询请求已挂起。 |
DNS query request is pending. |
| 0x254F | 无效的 DNS 类型。 |
Invalid DNS type. |
| 0x2550 | 无效的 IP 地址。 |
Invalid IP address. |
| 0x2551 | 无效的属性。 |
Invalid property. |
| 0x2552 | 稍后再试一次 DNS 操作。 |
Try DNS operation again later. |
| 0x2553 | 提供的名称和类型的记录不是唯一的。 |
Record for given name and type is not unique. |
| 0x2554 | DNS 名称不符合 RFC 说明。 |
DNS name does not comply with RFC specifications. |
| 0x2555 | DNS 名称是一个完全合格的 DNS 名称。 |
DNS name is a fully-qualified DNS name. |
| 0x2556 | DNS 名称以“.”分隔(多标签)。 |
DNS name is dotted (multi-label). |
| 0x2557 | DNS 名称是单一部分名称。 |
DNS name is a single-part name. |
| 0x2558 | DNS 名称含有无效字符。 |
DNS name contains an invalid character. |
| 0x2559 | DNS 名称完全是数字的。 |
DNS name is entirely numeric. |
| 0x255A | DNS 根目录服务器不允许请求的操作。 |
The operation requested is not permitted on a DNS root server. |
| 0x255B | 无法创建记录因为 DNS 命名空间的这一部分已经委派给另一服务器。 |
The record could not be created because this part of the DNS namespace has been delegated to another server. |
| 0x255C | DNS 服务器无法找到根目录提示集。 |
The DNS server could not find a set of root hints. |
| 0x255D | DNS 服务器找到了根目录按照权利要求，但是他们在所有适配器不一致。 |
The DNS server found root hints but they were not consistent across all adapters. |
| 0x255E | 为该参数指定的值过小。 |
The specified value is too small for this parameter. |
| 0x255F | 为该参数指定的值过大。 |
The specified value is too large for this parameter. |
| 0x2560 | 当 DNS 服务器在后台装载区域时不允许进行此操作。请稍后再试。 |
This operation is not allowed while the DNS server is loading zones in the background. Please try again later. |
| 0x2561 | 当 DNS 服务器在只读 DC 上运行时不允许进行请求的操作。 |
The operation requested is not permitted on against a DNS server running on a read-only DC. |
| 0x2562 | DNAME 记录下面不允许存在任何数据。 |
No data is allowed to exist underneath a DNAME record. |
| 0x2563 | 此操作需要凭据委派。 |
This operation requires credentials delegation. |
| 0x2564 | 名称解析策略表已损坏。在修复该表之前，DNS 解析将失败。请与网络管理员联系。 |
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. |
| 0x2565 | 不允许删除所有地址。 |
Not allowed to remove all addresses. |
| 0x2581 | DNS 区域不存在。 |
DNS zone does not exist. |
| 0x2582 | DNS 区域信息无效。 |
DNS zone information not available. |
| 0x2583 | DNS 区域无效操作。 |
Invalid operation for DNS zone. |
| 0x2584 | 无效 DNS 区域配置。 |
Invalid DNS zone configuration. |
| 0x2585 | DNS 区域没有颁发机构起始(SOA)的记录。 |
DNS zone has no start of authority (SOA) record. |
| 0x2586 | DNS 区域没有名称服务器(NS)的记录。 |
DNS zone has no Name Server (NS) record. |
| 0x2587 | DNS 区域已锁定。 |
DNS zone is locked. |
| 0x2588 | DNS 区域创建失败。 |
DNS zone creation failed. |
| 0x2589 | DNS 区域已经存在。 |
DNS zone already exists. |
| 0x258A | DNS 自动区域已经存在。 |
DNS automatic zone already exists. |
| 0x258B | 无效的 DNS 区域类型。 |
Invalid DNS zone type. |
| 0x258C | 次要 DNS 区域需要主 IP 地址。 |
Secondary DNS zone requires master IP address. |
| 0x258D | DNS 区域不是次要的。 |
DNS zone not secondary. |
| 0x258E | 需要一个次要 IP 地址。 |
Need secondary IP address. |
| 0x258F | WINS 初始化失败。 |
WINS initialization failed. |
| 0x2590 | 需要 WINS 服务器。 |
Need WINS servers. |
| 0x2591 | NBTSTAT 初始化呼叫失败。 |
NBTSTAT initialization call failed. |
| 0x2592 | 颁发机构起始(SOA)删除无效 |
Invalid delete of start of authority (SOA) |
| 0x2593 | 已有一个同名的条件转发区域。 |
A conditional forwarding zone already exists for that name. |
| 0x2594 | 此区域必须用一个或多个主 DNS 服务器的 IP 地址配置。 |
This zone must be configured with one or more master DNS server IP addresses. |
| 0x2595 | 因为该区域已关闭，所以此操作无法执行。 |
The operation cannot be performed because this zone is shut down. |
| 0x2596 | 无法执行此操作，因为当前正在对区域进行签名。请稍后再试。 |
This operation cannot be performed because the zone is currently being signed. Please try again later. |
| 0x25B3 | 主要 DNS 区域需要数据文件。 |
Primary DNS zone requires datafile. |
| 0x25B4 | DNS 区域的无效数据文件名称。 |
Invalid datafile name for DNS zone. |
| 0x25B5 | 未能打开 DNS 区域的数据文件。 |
Failed to open datafile for DNS zone. |
| 0x25B6 | 未能写入 DNS 区域的数据文件。 |
Failed to write datafile for DNS zone. |
| 0x25B7 | 读取 DNS 区域的数据文件时出现故障。 |
Failure while reading datafile for DNS zone. |
| 0x25E5 | DNS 记录不存在。 |
DNS record does not exist. |
| 0x25E6 | DNS 记录格式错误。 |
DNS record format error. |
| 0x25E7 | DNS 中节点创建失败。 |
Node creation failure in DNS. |
| 0x25E8 | 未知 DNS 记录类型。 |
Unknown DNS record type. |
| 0x25E9 | DNS 记录超时。 |
DNS record timed out. |
| 0x25EA | 名称不在 DNS 区域。 |
Name not in DNS zone. |
| 0x25EB | 检测到 CNAME 循环。 |
CNAME loop detected. |
| 0x25EC | 节点为一个 CNAME DNS 记录。 |
Node is a CNAME DNS record. |
| 0x25ED | 指定名称的 CNAME 记录已经存在。 |
A CNAME record already exists for given name. |
| 0x25EE | 记录不在 DNS 区域根目录。 |
Record only at DNS zone root. |
| 0x25EF | DNS 记录已经存在。 |
DNS record already exists. |
| 0x25F0 | 次要 DNS 区域数据错误。 |
Secondary DNS zone data error. |
| 0x25F1 | 不能创建 DNS 缓存数据。 |
Could not create DNS cache data. |
| 0x25F3 | 不能创建指针(PTR)记录。 |
Could not create pointer (PTR) record. |
| 0x25F4 | DNS 域没有被删除。 |
DNS domain was undeleted. |
| 0x25F6 | DNS 区域已经在目录服务中存在。 |
DNS zone already exists in the directory service. |
| 0x25F7 | DNS 服务器没有为目录服务集合 DNS 区域创建或读取启动文件。 |
DNS server not creating or reading the boot file for the directory service integrated DNS zone. |
| 0x25F8 | 节点是一个 DNAME DNS 记录。 |
Node is a DNAME DNS record. |
| 0x25F9 | 给定名称的 DNAME 记录已存在。 |
A DNAME record already exists for given name. |
| 0x25FA | 已检测到别名循环中有 CNAME 或 DNAME 记录。 |
An alias loop has been detected with either CNAME or DNAME records. |
| 0x2617 | DNS AXFR (区域复制)已完成。 |
DNS AXFR (zone transfer) complete. |
| 0x2618 | DNS 区域复制失败。 |
DNS zone transfer failed. |
| 0x2619 | 添加了本地 WINS 服务器。 |
Added local WINS server. |
| 0x2649 | 安全更新呼叫需要继续更新请求。 |
Secure update call needs to continue update request. |
| 0x267B | TCP/IP 没有安装网络协议。 |
TCP/IP network protocol not installed. |
| 0x267C | 没有为本地系统配置 DNS 服务器。 |
No DNS servers configured for local system. |
| 0x26AD | 指定的目录分区不存在。 |
The specified directory partition does not exist. |
| 0x26AE | 指定的目录分区已存在。 |
The specified directory partition already exists. |
| 0x26AF | DNS 服务器没被列入指定的目录分区。 |
This DNS server is not enlisted in the specified directory partition. |
| 0x26B0 | DNS 服务器已被列入指定的目录分区。 |
This DNS server is already enlisted in the specified directory partition. |
| 0x26B1 | 目录分区此时不可用。请等待几分钟然后再试一次。 |
The directory partition is not available at this time. Please wait a few minutes and try again. |
| 0x26B2 | 操作失败，原因是无法获得域命名主机 FSMO 角色。拥有域命名主机 FSMO 角色的域控制器出现故障、无法为该请求提供服务或未运行 Windows Server 2003 或更新版本。 |
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. |
| 0x26B7 | 未启用 RRL。 |
The RRL is not enabled. |
| 0x26B8 | 窗口大小参数无效。它应该大于或等于 1。 |
The window size parameter is invalid. It should be greater than or equal to 1. |
| 0x26B9 | IPv4 前缀长度参数无效。它应小于或等于 32。 |
The IPv4 prefix length parameter is invalid. It should be less than or equal to 32. |
| 0x26BA | IPv6 前缀长度参数无效。它应小于或等于 128。 |
The IPv6 prefix length parameter is invalid. It should be less than or equal to 128. |
| 0x26BB | TC 速率参数无效。它应小于 10。 |
The TC Rate parameter is invalid. It should be less than 10. |
| 0x26BC | 泄漏速率参数无效。它应为 0，或介于 2 到 10 之间。 |
The Leak Rate parameter is invalid. It should be either 0, or between 2 and 10. |
| 0x26BD | 泄漏速率或 TC 速率参数无效。泄漏速率应大于 TC 速率。 |
The Leak Rate or TC Rate parameter is invalid. Leak Rate should be greater than TC Rate. |
| 0x26C1 | 虚拟化实例已存在。 |
The virtualization instance already exists. |
| 0x26C2 | 虚拟化实例不存在。 |
The virtualization instance does not exist. |
| 0x26C3 | 虚拟树已锁定。 |
The virtualization tree is locked. |
| 0x26C4 | 虚拟化实例名称无效。 |
Invalid virtualization instance name. |
| 0x26C5 | 不能添加、删除或修改默认的虚拟化实例。 |
The default virtualization instance cannot be added, removed or modified. |
| 0x26DF | 区域的作用域已存在。 |
The scope already exists for the zone. |
| 0x26E0 | 区域的作用域不存在。 |
The scope does not exist for the zone. |
| 0x26E1 | 作用域与默认区域作用域相同。 |
The scope is the same as the default zone scope. |
| 0x26E2 | 作用域名称包含无效的字符。 |
The scope name contains invalid characters. |
| 0x26E3 | 当该区域存在作用域时，不允许操作。 |
Operation not allowed when the zone has scopes. |
| 0x26E4 | 无法加载区域作用域。 |
Failed to load zone scope. |
| 0x26E5 | 无法写入 DNS 区域作用域的数据文件。请验证该文件确实存在并且可写入。 |
Failed to write data file for DNS zone scope. Please verify the file exists and is writable. |
| 0x26E7 | 该作用域不存在。 |
The scope does not exist. |
| 0x26E8 | 该作用域与默认作用域相同。 |
The scope is the same as the default scope. |
| 0x26E9 | 该操作对于此作用域无效。 |
The operation is invalid on the scope. |
| 0x26EA | 该作用域已锁定。 |
The scope is locked. |
| 0x26EB | 该作用域已存在。 |
The scope already exists. |
| 0x26F3 | 在 DNS 服务器的此级别(服务器级别或区域级别)上，同名的策略已存在。 |
A policy with the same name already exists on this level (server level or zone level) on the DNS server. |
| 0x26F4 | 在 DNS 服务器的此级别(服务器级别或区域级别)上，使用此名称的策略不存在。 |
No policy with this name exists on this level (server level or zone level) on the DNS server. |
| 0x26F5 | 策略中提供的条件无效。 |
The criteria provided in the policy are invalid. |
| 0x26F6 | 此策略至少有一个设置无效。 |
At least one of the settings of this policy is invalid. |
| 0x26F7 | 在根据策略访问客户端子网时无法将其删除。 |
The client subnet cannot be deleted while it is being accessed by a policy. |
| 0x26F8 | 在 DNS 服务器上，客户端子网不存在。 |
The client subnet does not exist on the DNS server. |
| 0x26F9 | 在 DNS 服务器上，使用此名称的客户端子网已存在。 |
A client subnet with this name already exists on the DNS server. |
| 0x26FA | 客户端子网中不存在指定的 IP 子网。 |
The IP subnet specified does not exist in the client subnet. |
| 0x26FB | 客户端子网中已存在正在添加的 IP 子网。 |
The IP subnet that is being added, already exists in the client subnet. |
| 0x26FC | 该策略已锁定。 |
The policy is locked. |
| 0x26FD | 作用域在策略中的权重无效。 |
The weight of the scope in the policy is invalid. |
| 0x26FE | DNS 策略名称无效。 |
The DNS policy name is invalid. |
| 0x26FF | 策略缺少条件。 |
The policy is missing criteria. |
| 0x2700 | 客户端子网记录名称无效。 |
The name of the the client subnet record is invalid. |
| 0x2701 | 策略处理顺序无效。 |
Invalid policy processing order. |
| 0x2702 | 尚未为需要作用域信息的策略提供该信息。 |
The scope information has not been provided for a policy that requires it. |
| 0x2703 | 已为不需要作用域信息的策略提供该信息。 |
The scope information has been provided for a policy that does not require it. |
| 0x2704 | 无法删除该服务器作用域，因为它被某个 DNS 策略引用。 |
The server scope cannot be deleted because it is referenced by a DNS Policy. |
| 0x2705 | 无法删除该区域作用域，因为它被某个 DNS 策略引用。 |
The zone scope cannot be deleted because it is referenced by a DNS Policy. |
| 0x2706 | 在策略中提供的标准客户端子网无效。 |
The criterion client subnet provided in the policy is invalid. |
| 0x2707 | 在策略中提供的标准传输协议无效。 |
The criterion transport protocol provided in the policy is invalid. |
| 0x2708 | 在策略中提供的标准网络协议无效。 |
The criterion network protocol provided in the policy is invalid. |
| 0x2709 | 在策略中提供的标准接口无效。 |
The criterion interface provided in the policy is invalid. |
| 0x270A | 在策略中提供的标准 FQDN 无效。 |
The criterion FQDN provided in the policy is invalid. |
| 0x270B | 在策略中提供的标准查询类型无效。 |
The criterion query type provided in the policy is invalid. |
| 0x270C | 在策略中提供的标准时间无效。 |
The criterion time of day provided in the policy is invalid. |
| 0x00002714 | 一个封锁操作被对 WSACancelBlockingCall 的调用中断。 |
A blocking operation was interrupted by a call to WSACancelBlockingCall. |
| 0x00002719 | 提供的文件句柄无效。 |
The file handle supplied is not valid. |
| 0x0000271D | 以一种访问权限不允许的方式做了一个访问套接字的尝试。 |
An attempt was made to access a socket in a way forbidden by its access permissions. |
| 0x0000271E | 系统检测到在一个调用中尝试使用指针参数时的无效指针地址。 |
The system detected an invalid pointer address in attempting to use a pointer argument in a call. |
| 0x00002726 | 提供了一个无效的参数。 |
An invalid argument was supplied. |
| 0x00002728 | 打开的套接字太多。 |
Too many open sockets. |
| 0x00002733 | 无法立即完成一个非阻止性套接字操作。 |
A non-blocking socket operation could not be completed immediately. |
| 0x00002734 | 目前正在执行一个阻止性操作。 |
A blocking operation is currently executing. |
| 0x00002735 | 在一个非阻止性套接字上尝试了一个已经在进行的操作。 |
An operation was attempted on a non-blocking socket that already had an operation in progress. |
| 0x00002736 | 在一个非套接字上尝试了一个操作。 |
An operation was attempted on something that is not a socket. |
| 0x00002737 | 请求的地址在一个套接字中从操作中忽略。 |
A required address was omitted from an operation on a socket. |
| 0x00002738 | 一个在数据报套接字上发送的消息大于内部消息缓冲区或其他一些网络限制，或该用户用于接收数据报的缓冲区比数据报小。 |
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. |
| 0x00002739 | 在套接字函数调用中指定的一个协议不支持请求的套接字类型的语法。 |
A protocol was specified in the socket function call that does not support the semantics of the socket type requested. |
| 0x0000273A | 在 getsockopt 或 setsockopt 调用中指定的一个未知的、无效的或不受支持的选项或层次。 |
An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call. |
| 0x0000273B | 请求的协议还没有在系统中配置，或者没有它存在的迹象。 |
The requested protocol has not been configured into the system, or no implementation for it exists. |
| 0x0000273C | 在这个地址家族中不存在对指定的插槽类型的支持。 |
The support for the specified socket type does not exist in this address family. |
| 0x0000273D | 参考的对象类型不支持尝试的操作。 |
The attempted operation is not supported for the type of object referenced. |
| 0x0000273E | 协议家族尚未配置到系统中或没有它的存在迹象。 |
The protocol family has not been configured into the system or no implementation for it exists. |
| 0x0000273F | 使用了与请求的协议不兼容的地址。 |
An address incompatible with the requested protocol was used. |
| 0x00002740 | 通常每个套接字地址(协议/网络地址/端口)只允许使用一次。 |
Only one usage of each socket address (protocol/network address/port) is normally permitted. |
| 0x00002741 | 在其上下文中，该请求的地址无效。 |
The requested address is not valid in its context. |
| 0x00002742 | 套接字操作遇到了一个已死的网络。 |
A socket operation encountered a dead network. |
| 0x00002743 | 向一个无法连接的网络尝试了一个套接字操作。 |
A socket operation was attempted to an unreachable network. |
| 0x00002744 | 当该操作在进行中，由于保持活动的操作检测到一个故障，该连接中断。 |
The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. |
| 0x00002745 | 你的主机中的软件中止了一个已建立的连接。 |
An established connection was aborted by the software in your host machine. |
| 0x00002746 | 远程主机强迫关闭了一个现有的连接。 |
An existing connection was forcibly closed by the remote host. |
| 0x00002747 | 由于系统缓冲区空间不足或队列已满，不能执行套接字上的操作。 |
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. |
| 0x00002748 | 在一个已经连接的套接字上做了一个连接请求。 |
A connect request was made on an already connected socket. |
| 0x00002749 | 由于套接字没有连接并且(当使用一个 sendto 调用发送数据报套接字时)没有提供地址，发送或接收数据的请求没有被接受。 |
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. |
| 0x0000274A | 由于以前的关闭调用，套接字在那个方向已经关闭，发送或接收数据的请求没有被接受。 |
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. |
| 0x0000274B | 对某个内核对象的引用过多。 |
Too many references to some kernel object. |
| 0x0000274C | 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 |
A 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. |
| 0x0000274D | 由于目标计算机积极拒绝，无法连接。 |
No connection could be made because the target machine actively refused it. |
| 0x0000274E | 无法转换名称。 |
Cannot translate name. |
| 0x0000274F | 名称组件或名称太长。 |
Name component or name was too long. |
| 0x00002750 | 由于目标主机坏了，套接字操作失败。 |
A socket operation failed because the destination host was down. |
| 0x00002751 | 套接字操作尝试一个无法连接的主机。 |
A socket operation was attempted to an unreachable host. |
| 0x00002752 | 不能删除目录，除非它是空的。 |
Cannot remove a directory that is not empty. |
| 0x00002753 | 一个 Windows 套接字操作可能在可以同时使用的应用程序数目上有限制。 |
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. |
| 0x00002754 | 限额不足。 |
Ran out of quota. |
| 0x00002755 | 磁盘限额不足。 |
Ran out of disk quota. |
| 0x00002756 | 文件句柄引用不再可用。 |
File handle reference is no longer available. |
| 0x00002757 | 项目在本地不可用。 |
Item is not available locally. |
| 0x0000276B | 因为它使用提供网络服务的系统目前无效，WSAStartup 目前不能正常工作。 |
WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable. |
| 0x0000276C | 不支持请求的 Windows 套接字版本。 |
The Windows Sockets version requested is not supported. |
| 0x0000276D | 应用程序没有调用 WSAStartup，或者 WSAStartup 失败。 |
Either the application has not called WSAStartup, or WSAStartup failed. |
| 0x00002775 | 由 WSARecv 或 WSARecvFrom 返回表示远程方面已经开始了关闭步骤。 |
Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence. |
| 0x00002776 | WSALookupServiceNext 不能返回更多的结果。 |
No more results can be returned by WSALookupServiceNext. |
| 0x00002777 | 在该调用还处于处理中时，就调用了 WSALookupServiceEnd。该调用被取消。 |
A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled. |
| 0x00002778 | 过程调用表无效。 |
The procedure call table is invalid. |
| 0x00002779 | 请求的服务提供程序无效。 |
The requested service provider is invalid. |
| 0x0000277A | 无法加载或初始化请求的服务提供程序。 |
The requested service provider could not be loaded or initialized. |
| 0x0000277B | 系统调用失败。 |
A system call has failed. |
| 0x0000277C | 此服务不存在。在指定的命名空间中找不这个服务。 |
No such service is known. The service cannot be found in the specified name space. |
| 0x0000277D | 找不到指定的类。 |
The specified class was not found. |
| 0x00002780 | 由于被拒绝，数据库查询失败。 |
A database query failed because it was actively refused. |
| 0x00002AF9 | 不知道这样的主机。 |
No such host is known. |
| 0x00002AFA | 这是在主机名解析时通常出现的暂时错误，它意味着本地服务器没有从权威服务器上收到响应。 |
This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. |
| 0x00002AFB | 在数据库查找中出现一个不可恢复的错误。 |
A non-recoverable error occurred during a database lookup. |
| 0x00002AFC | 请求的名称有效，但是找不到请求的类型的数据。 |
The requested name is valid, but no data of the requested type was found. |
| 0x00002AFD | 至少到达了一个保留。 |
At least one reserve has arrived. |
| 0x00002AFE | 至少到达了一个路径。 |
At least one path has arrived. |
| 0x00002AFF | 没有发送方。 |
There are no senders. |
| 0x00002B00 | 没有接受方。 |
There are no receivers. |
| 0x00002B01 | 保留已经确认。 |
Reserve has been confirmed. |
| 0x00002B02 | 错误是由于资源不足造成。 |
Error due to lack of resources. |
| 0x00002B03 | 由于管理原因被拒绝 - 无效凭证。 |
Rejected for administrative reasons - bad credentials. |
| 0x00002B04 | 未知或有冲突类型。 |
Unknown or conflicting style. |
| 0x00002B05 | 通常 filterspec 或 providerspecific 缓冲区的部分有问题。 |
Problem with some part of the filterspec or providerspecific buffer in general. |
| 0x00002B06 | flowspec 的某部分有问题。 |
Problem with some part of the flowspec. |
| 0x00002B07 | 一般性 QOS 错误。 |
General QOS error. |
| 0x00002B08 | 在流程规格中发现一个无效的或不可识别的服务类型。 |
An invalid or unrecognized service type was found in the flowspec. |
| 0x00002B09 | 在 QOS 结构中发现一个无效的或不一致的流程规格。 |
An invalid or inconsistent flowspec was found in the QOS structure. |
| 0x00002B0A | 无效的 QOS 提供程序特定缓冲区。 |
Invalid QOS provider-specific buffer. |
| 0x00002B0B | 使用了无效的 QOS 筛选器样式。 |
An invalid QOS filter style was used. |
| 0x00002B0C | 使用了无效的 QOS 筛选器类型。 |
An invalid QOS filter type was used. |
| 0x00002B0D | FLOWDESCRIPTOR 中指定的 QOS FILTERSPEC 数量不正确。 |
An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR. |
| 0x00002B0E | 在 QOS 提供程序特定缓冲区中指定了一个 ObjectLength 字符域无效的对象。 |
An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer. |
| 0x00002B0F | QOS 结构中指定的流程描述符数量不正确。 |
An incorrect number of flow descriptors was specified in the QOS structure. |
| 0x00002B10 | 在 QOS 提供程序特定缓冲区中发现一个不可识别的对象。 |
An unrecognized object was found in the QOS provider-specific buffer. |
| 0x00002B11 | 在 QOS 提供程序特定缓冲区中发现一个无效的策略对象。 |
An invalid policy object was found in the QOS provider-specific buffer. |
| 0x00002B12 | 在流程描述符列表中发现一个无效的 QOS 流程描述符。 |
An invalid QOS flow descriptor was found in the flow descriptor list. |
| 0x00002B13 | 在 QOS 提供程序特定缓冲区中发现一个无效的或不一致的流程规格。 |
An invalid or inconsistent flowspec was found in the QOS provider specific buffer. |
| 0x00002B14 | 在 QOS 提供程序特定缓冲区中发现一个无效的 FILTERSPEC。 |
An invalid FILTERSPEC was found in the QOS provider-specific buffer. |
| 0x00002B15 | 在 QOS 提供程序特定缓冲区中发现一个无效的波形丢弃模式对象。 |
An invalid shape discard mode object was found in the QOS provider specific buffer. |
| 0x00002B16 | 在 QOS 提供程序特定缓冲区中发现一个无效的成形速率对象。 |
An invalid shaping rate object was found in the QOS provider-specific buffer. |
| 0x00002B17 | 在 QOS 提供程序特定缓冲区中发现一个保留的策略因素。 |
A reserved policy element was found in the QOS provider-specific buffer. |
| 0x00002B18 | 不能安全地知道这样的主机。 |
No such host is known securely. |
| 0x00002B19 | 无法添加基于名称的 IPSEC 策略。 |
Name based IPSEC policy could not be added. |
| 0x000032C8 | 指定的快速模式策略已存在。 |
The specified quick mode policy already exists. |
| 0x000032C9 | 找不到指定的快速模式策略。 |
The specified quick mode policy was not found. |
| 0x000032CA | 指定的快速模式策略正在使用中。 |
The specified quick mode policy is being used. |
| 0x000032CB | 指定的主要模式策略已存在。 |
The specified main mode policy already exists. |
| 0x000032CC | 找不到指定的主要模式策略。 |
The specified main mode policy was not found |
| 0x000032CD | 指定的主要模式策略正在使用中。 |
The specified main mode policy is being used. |
| 0x000032CE | 指定的主要模式筛选器已存在。 |
The specified main mode filter already exists. |
| 0x000032CF | 找不到指定的主要模式筛选器。 |
The specified main mode filter was not found. |
| 0x000032D0 | 指定的传输模式筛选器已存在。 |
The specified transport mode filter already exists. |
| 0x000032D1 | 指定的传输模式筛选器不存在。 |
The specified transport mode filter does not exist. |
| 0x000032D2 | 指定的主要模式身份验证列表存在。 |
The specified main mode authentication list exists. |
| 0x000032D3 | 找不到指定的主要模式身份验证列表。 |
The specified main mode authentication list was not found. |
| 0x000032D4 | 指定的主模式身份验证列表正在使用中。 |
The specified main mode authentication list is being used. |
| 0x000032D5 | 找不到指定的默认主要模式策略。 |
The specified default main mode policy was not found. |
| 0x000032D6 | 找不到指定的默认主模式身份验证列表。 |
The specified default main mode authentication list was not found. |
| 0x000032D7 | 找不到指定的默认快速模式策略。 |
The specified default quick mode policy was not found. |
| 0x000032D8 | 存在指定的隧道模式筛选器。 |
The specified tunnel mode filter exists. |
| 0x000032D9 | 找不到指定的隧道模式筛选器。 |
The specified tunnel mode filter was not found. |
| 0x000032DA | 主要模式筛选器正挂起删除。 |
The Main Mode filter is pending deletion. |
| 0x000032DB | 传输筛选器正挂起删除。 |
The transport filter is pending deletion. |
| 0x000032DC | 隧道筛选器正挂起删除。 |
The tunnel filter is pending deletion. |
| 0x000032DD | 主要模式策略正挂起删除。 |
The Main Mode policy is pending deletion. |
| 0x000032DE | 主要模式身份验证绑定正挂起删除。 |
The Main Mode authentication bundle is pending deletion. |
| 0x000032DF | 快速模式策略正挂起删除。 |
The Quick Mode policy is pending deletion. |
| 0x000032E0 | 成功地添加了主模式策略，但是不支持部分请求的提供。 |
The Main Mode policy was successfully added, but some of the requested offers are not supported. |
| 0x000032E1 | 成功地添加了快速模式策略，但是不支持部分请求的提供。 |
The Quick Mode policy was successfully added, but some of the requested offers are not supported. |
| 0x000035E8 | ERROR_IPSEC_IKE_NEG_STATUS_BEGIN |
ERROR_IPSEC_IKE_NEG_STATUS_BEGIN |
| 0x000035E9 | IKE 身份验证凭证不可接受 |
IKE authentication credentials are unacceptable |
| 0x000035EA | IKE 安全属性不可接受 |
IKE security attributes are unacceptable |
| 0x000035EB | IKE 协商正在进行中 |
IKE Negotiation in progress |
| 0x000035EC | 一般性处理错误 |
General processing error |
| 0x000035ED | 协商超时 |
Negotiation timed out |
| 0x000035EE | IKE 无法找到有效的计算机证书。请联系你的网络安全管理员，了解有关在相关的证书存储中安装有效证书。 |
IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store. |
| 0x000035EF | 完成建立之前，IKE SA 已被对等机删除 |
IKE SA deleted by peer before establishment completed |
| 0x000035F0 | 完成建立之前，IKE SA 已被删除 |
IKE SA deleted before establishment completed |
| 0x000035F1 | 协商请求在队列中时间太长 |
Negotiation request sat in Queue too long |
| 0x000035F5 | 对等机没有响应 |
No response from peer |
| 0x000035F6 | 协商所花时间太长 |
Negotiation took too long |
| 0x000035F8 | 出现了未知错误 |
Unknown error occurred |
| 0x000035F9 | 证书吊销检查失败 |
Certificate Revocation Check failed |
| 0x000035FA | 无效的证书密钥用法 |
Invalid certificate key usage |
| 0x000035FB | 无效的证书类型 |
Invalid certificate type |
| 0x000035FC | 由于使用的计算机证书无专用密钥，因此 IKE 协商失败。IPsec 证书要求私钥。请联系你的网络安全管理员，了解有关使用具有专用密钥的证书进行替换。 |
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. |
| 0x000035FD | 检测到同时重新生成的密钥。 |
Simultaneous rekeys were detected. |
| 0x000035FE | Diffie-Helman 计算失败 |
Failure in Diffie-Hellman computation |
| 0x000035FF | 不知道如何处理临界负载 |
Don't know how to process critical payload |
| 0x00003600 | 无效的标头 |
Invalid header |
| 0x00003601 | 没有配置策略 |
No policy configured |
| 0x00003602 | 未能确认签名 |
Failed to verify signature |
| 0x00003603 | 无法使用 kerberos 进行身份验证 |
Failed to authenticate using Kerberos |
| 0x00003604 | 对等机的证书没有公钥 |
Peer's certificate did not have a public key |
| 0x00003605 | 处理 error 负载时的错误 |
Error processing error payload |
| 0x00003606 | 处理 SA 负载时的错误 |
Error processing SA payload |
| 0x00003607 | 处理 Proposal 负载时的错误 |
Error processing Proposal payload |
| 0x00003608 | 处理 Transform 负载时的错误 |
Error processing Transform payload |
| 0x00003609 | 处理 KE 负载时的错误 |
Error processing KE payload |
| 0x0000360A | 处理 ID 负载时的错误 |
Error processing ID payload |
| 0x0000360B | 处理 Cert 负载时的错误 |
Error processing Cert payload |
| 0x0000360C | 处理 Certificate Request 负载时的错误 |
Error processing Certificate Request payload |
| 0x0000360D | 处理哈希负载时的错误 |
Error processing Hash payload |
| 0x0000360E | 处理 Signature 负载时的错误 |
Error processing Signature payload |
| 0x0000360F | 处理 Nonce 负载时的错误 |
Error processing Nonce payload |
| 0x00003610 | 处理 Notify 负载时的错误 |
Error processing Notify payload |
| 0x00003611 | 处理 Delete 负载时的错误 |
Error processing Delete Payload |
| 0x00003612 | 处理 VendorId 负载时的错误 |
Error processing VendorId payload |
| 0x00003613 | 收到了无效负载 |
Invalid payload received |
| 0x00003614 | 加载了软件 SA |
Soft SA loaded |
| 0x00003615 | 软件 SA 被拆散 |
Soft SA torn down |
| 0x00003616 | 收到了无效 cookie。 |
Invalid cookie received. |
| 0x00003617 | 对等机未能发送有效的计算机证书 |
Peer failed to send valid machine certificate |
| 0x00003618 | 对等机证书的证书吊销检查没有成功 |
Certification Revocation check of peer's certificate failed |
| 0x00003619 | 新策略使旧策略形成的 SA 无效 |
New policy invalidated SAs formed with old policy |
| 0x0000361A | 没有可用的主模式 IKE 策略。 |
There is no available Main Mode IKE policy. |
| 0x0000361B | 启用 TCB 特权失败。 |
Failed to enabled TCB privilege. |
| 0x0000361C | 加载 SECURITY.DLL 失败。 |
Failed to load SECURITY.DLL. |
| 0x0000361D | 未能从 SSPI 取得安全函数表调度地址。 |
Failed to obtain security function table dispatch address from SSPI. |
| 0x0000361E | 未能查询 Kerberos 包以取得最大令牌尺寸。 |
Failed to query Kerberos package to obtain max token size. |
| 0x0000361F | 未能为 ISAKMP/ERROR_IPSEC_IKE 服务获取 Kerberos 服务器凭证。Kerberos 身份验证无法运行。很可能是因为没有域成员身份。如果你的计算机是工作组的成员，这是正常的。 |
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. |
| 0x00003620 | 未能确定 ISAKMP/ERROR_IPSEC_IKE 服务(QueryCredentialsAttributes)的 SSPI 主要名称。 |
Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes). |
| 0x00003621 | 无法从 Ipsec 驱动程序为入站的 SA 获取新的 SPI。造成这种问题最常见的原因是，驱动程序没有正确的筛选器。请检查策略来验证筛选器。 |
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. |
| 0x00003622 | 给出的筛选无效 |
Given filter is invalid |
| 0x00003623 | 内存分配失败。 |
Memory allocation failed. |
| 0x00003624 | 无法将安全关联添加到 IPSec 驱动程序。造成这种问题最常见的原因是，IKE 协商花的时间太长。如果该问题继续存在，请减少造成错误的计算机上的负荷。 |
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. |
| 0x00003625 | 无效策略 |
Invalid policy |
| 0x00003626 | 无效 DOI |
Invalid DOI |
| 0x00003627 | 无效情况 |
Invalid situation |
| 0x00003628 | Diffie-Hellman 故障 |
Diffie-Hellman failure |
| 0x00003629 | 无效的 Diffie-Hellman 组 |
Invalid Diffie-Hellman group |
| 0x0000362A | 加密有效负载的错误 |
Error encrypting payload |
| 0x0000362B | 解密有效负载的错误 |
Error decrypting payload |
| 0x0000362C | 策略匹配错误 |
Policy match error |
| 0x0000362D | 不受支持的 ID |
Unsupported ID |
| 0x0000362E | 哈希验证没有成功 |
Hash verification failed |
| 0x0000362F | 无效哈希算法 |
Invalid hash algorithm |
| 0x00003630 | 无效哈希大小 |
Invalid hash size |
| 0x00003631 | 无效的加密算法 |
Invalid encryption algorithm |
| 0x00003632 | 无效的身份验证算法 |
Invalid authentication algorithm |
| 0x00003633 | 无效的证书签名 |
Invalid certificate signature |
| 0x00003634 | 加载失败 |
Load failed |
| 0x00003635 | 通过 RPC 调用删除的 |
Deleted via RPC call |
| 0x00003636 | 为执行重新初始化而创建的临时状态。这不是一个真正的故障。 |
Temporary state created to perform reinitialization. This is not a real failure. |
| 0x00003637 | 在响应方寿命通知里收到的寿命值低于 Windows 2000 配置的最小值。请整理对等机上的策略。 |
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. |
| 0x00003638 | 接收人无法处理标头中指定的 IKE 版本。 |
The recipient cannot handle version of IKE specified in the header. |
| 0x00003639 | 对于配置的安全要求来说，证书里的密钥长度太小。 |
Key length in certificate is too small for configured security requirements. |
| 0x0000363A | 超过了对等机的已建立的 MM SA 最大数值。 |
Max number of established MM SAs to peer exceeded. |
| 0x0000363B | IKE 收到一个停用协商的策略。 |
IKE received a policy that disables negotiation. |
| 0x0000363C | 已达到主模式的最大快速模式限制。将启动新的主模式。 |
Reached maximum quick mode limit for the main mode. New main mode will be started. |
| 0x0000363D | 主模式 SA 生存时间已过期，或对等机发送了主模式删除。 |
Main mode SA lifetime expired or peer sent a main mode delete. |
| 0x0000363E | 认为主模式 SA 无效，因为对等机停止响应。 |
Main mode SA assumed to be invalid because peer stopped responding. |
| 0x0000363F | 证书未链接到 IPsec 策略中受信任的根。 |
Certificate doesn't chain to a trusted root in IPsec policy. |
| 0x00003640 | 接收到意外消息 ID。 |
Received unexpected message ID. |
| 0x00003641 | 接收到无效的身份验证提供服务。 |
Received invalid authentication offers. |
| 0x00003642 | 已将 DoS cookie 通知发送到起始程序。 |
Sent DoS cookie notify to initiator. |
| 0x00003643 | IKE 服务正在关闭。 |
IKE service is shutting down. |
| 0x00003644 | 无法验证 CGA 地址和证书是否已绑定。 |
Could not verify binding between CGA address and certificate. |
| 0x00003645 | 处理 NatOA 负载时出错。 |
Error processing NatOA payload. |
| 0x00003646 | 主模式的参数对于此快速模式无效。 |
Parameters of the main mode are invalid for this quick mode. |
| 0x00003647 | IPsec 驱动程序已使快速模式 SA 过期。 |
Quick mode SA was expired by IPsec driver. |
| 0x00003648 | 检测到过多动态添加的 IKEEXT 筛选器。 |
Too many dynamically added IKEEXT filters were detected. |
| 0x00003649 | ERROR_IPSEC_IKE_NEG_STATUS_END |
ERROR_IPSEC_IKE_NEG_STATUS_END |
| 0x0000364A | NAP 重新身份验证成功且必须删除虚拟 NAP IkeV2 隧道。 |
NAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel. |
| 0x0000364B | 在隧道模式下将内部 IP 地址分配给发起程序时出错。 |
Error in assigning inner IP address to initiator in tunnel mode. |
| 0x0000364C | 缺少要求配置的负载。 |
Require configuration payload missing. |
| 0x0000364D | 正在进行以发出连接的安全主体身份运行的协商 |
A negotiation running as the security principle who issued the connection is in progress |
| 0x0000364E | 由于 IKEv1/AuthIP 共存取消检查，SA 被删除。 |
SA was deleted due to IKEv1/AuthIP co-existence suppress check. |
| 0x0000364F | 由于对等 IP 地址速率限制，传入 SA 请求被删除。 |
Incoming SA request was dropped due to peer IP address rate limiting. |
| 0x00003650 | 对等不支持 MOBIKE。 |
Peer does not support MOBIKE. |
| 0x00003651 | 未授权建立 SA。 |
SA establishment is not authorized. |
| 0x00003652 | 未授权建立 SA，因为缺乏足够强的基于 PKINIT 的凭据。 |
SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. |
| 0x00003653 | 未授权建立 SA。可能需要输入更新的凭据或其他凭据(如智能卡)。 |
SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard. |
| 0x00003654 | 未授权建立 SA，因为没有足够强的基于 PKINIT 的凭据。这可能与 SA 的证书到帐户映射失败有关。 |
SA 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. |
| 0x00003655 | ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END |
ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END |
| 0x00003656 | 数据包中的 SPI 与有效的 IPSec SA 不匹配。 |
The SPI in the packet does not match a valid IPsec SA. |
| 0x00003657 | 生存时间已过期的 IPSec SA 接收到数据包。 |
Packet was received on an IPsec SA whose lifetime has expired. |
| 0x00003658 | IPSec SA 接收到与数据包特征不匹配的数据包。 |
Packet was received on an IPsec SA that does not match the packet characteristics. |
| 0x00003659 | 数据包序列号重播检查失败。 |
Packet sequence number replay check failed. |
| 0x0000365A | 数据包中 IPSec 的头和/或尾无效。 |
IPsec header and/or trailer in the packet is invalid. |
| 0x0000365B | IPSec 完整性检查失败。 |
IPsec integrity check failed. |
| 0x0000365C | IPSec 丢弃了一个明文数据包。 |
IPsec dropped a clear text packet. |
| 0x0000365D | IPSec 已丢弃已验证防火墙模式下的传入 ESP 数据包。此丢弃是良性的。 |
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign. |
| 0x0000365E | 由于 DoS 节流，IPSec 已丢弃数据包。 |
IPsec dropped a packet due to DoS throttling. |
| 0x00003665 | IPSec DoS 保护符合一个显式阻止规则。 |
IPsec DoS Protection matched an explicit block rule. |
| 0x00003666 | IPSec DoS 保护收到一个禁止的 IPSec 特定多播数据包。 |
IPsec DoS Protection received an IPsec specific multicast packet which is not allowed. |
| 0x00003667 | IPSec DoS 保护收到的数据包格式错误。 |
IPsec DoS Protection received an incorrectly formatted packet. |
| 0x00003668 | IPSec DoS 保护查找状态失败。 |
IPsec DoS Protection failed to look up state. |
| 0x00003669 | IPSec DoS 保护创建状态失败，因为已达到策略允许的最大条目数。 |
IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached. |
| 0x0000366A | IPSec DoS 保护收到策略禁止的密钥模块的 IPSec 协商数据包。 |
IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. |
| 0x0000366B | IPSec DoS 保护尚未启用。 |
IPsec DoS Protection has not been enabled. |
| 0x0000366C | IPSec DoS 保护创建每个内部 IP 速率极限队列失败，因为已达到策略允许的最大队列数。 |
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. |
| 0x000036B0 | 申请的节不存在于激活上下文。 |
The requested section was not present in the activation context. |
| 0x000036B1 | 应用程序无法启动，因为应用程序的并行配置不正确。有关详细信息，请参阅应用程序事件日志，或使用命令行 sxstrace.exe 工具。 |
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. |
| 0x000036B2 | 应用程序绑定数据格式无效。 |
The application binding data format is invalid. |
| 0x000036B3 | 参照的程序集没有安装在系统上。 |
The referenced assembly is not installed on your system. |
| 0x000036B4 | 清单文件没有以要求的标记和格式信息开始。 |
The manifest file does not begin with the required tag and format information. |
| 0x000036B5 | 清单文件包含多个语法错误。 |
The manifest file contains one or more syntax errors. |
| 0x000036B6 | 应用程序试图激活禁用的激活上下文。 |
The application attempted to activate a disabled activation context. |
| 0x000036B7 | 在活动的激活上下文中找不到任何查找密钥。 |
The requested lookup key was not found in any active activation context. |
| 0x000036B8 | 应用程序要求的组件版本同另一个活动的组件有冲突。 |
A component version required by the application conflicts with another component version already active. |
| 0x000036B9 | 要求激活上下文部分的类型与使用的查询 API 不匹配。 |
The type requested activation context section does not match the query API used. |
| 0x000036BA | 由于系统资源缺乏，要求为当前执行的线程禁用独立的激活。 |
Lack of system resources has required isolated activation to be disabled for the current thread of execution. |
| 0x000036BB | 已设置进程默认激活上下文，因此设置失败。 |
An attempt to set the process default activation context failed because the process default activation context was already set. |
| 0x000036BC | 不能识别指定的编码组标识符。 |
The encoding group identifier specified is not recognized. |
| 0x000036BD | 不能识别申请的编码。 |
The encoding requested is not recognized. |
| 0x000036BE | 清单中参考一个无效的 URI。 |
The manifest contains a reference to an invalid URI. |
| 0x000036BF | 应用程序的清单中参考一个没安装的从属汇编 |
The application manifest contains a reference to a dependent assembly which is not installed |
| 0x000036C0 | 应用程序所用的汇编的清单参考一个没安装的从属汇编 |
The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed |
| 0x000036C1 | 清单中包含无效汇编身份的属性。 |
The manifest contains an attribute for the assembly identity which is not valid. |
| 0x000036C2 | 清单中没有所要求的汇编元素的默认命名空间规格。 |
The manifest is missing the required default namespace specification on the assembly element. |
| 0x000036C3 | 清单中有汇编元素的默认命名空间，但是它的值不是\"urn:schemas-microsoft-com:asm.v1\". |
The manifest has a default namespace specified on the assembly element but its value is not \"urn:schemas-microsoft-com:asm.v1\". |
| 0x000036C4 | 要查明的专用清单已越过具有不受支持的重分析点的路径。 |
The private manifest probed has crossed a path with an unsupported reparse point. |
| 0x000036C5 | 至少有两个被应用程序清单直接或间接引用的组件具有同名的文件。 |
Two or more components referenced directly or indirectly by the application manifest have files by the same name. |
| 0x000036C6 | 至少有两个被应用程序清单直接或间接引用的组件具有同名的窗口类。 |
Two or more components referenced directly or indirectly by the application manifest have window classes with the same name. |
| 0x000036C7 | 至少有两个被应用程序清单直接或间接引用的组件具有相同的 COM 服务器 CLSID。 |
Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs. |
| 0x000036C8 | 至少有两个被应用程序清单直接或间接引用的组件具有相同 COM 接口 IID 的代理程序。 |
Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs. |
| 0x000036C9 | 至少有两个被应用程序清单直接或间接引用的组件具有相同的 COM 类型库 TLBID。 |
Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs. |
| 0x000036CA | 至少有两个被应用程序清单直接或间接引用的组件具有相同的 COM ProgID。 |
Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs. |
| 0x000036CB | 至少有两个被应用程序清单直接或间接引用的组件是不被允许的同一个组件的不同版本。 |
Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted. |
| 0x000036CC | 组件的文件跟组件清单中的验证信息不匹配。 |
A component's file does not match the verification information present in the component manifest. |
| 0x000036CD | 策略清单含有至少一个语法错误。 |
The policy manifest contains one or more syntax errors. |
| 0x000036CE | 清单分析错误 : 需要字符串程序文字，但找不到左引号。 |
Manifest Parse Error : A string literal was expected, but no opening quote character was found. |
| 0x000036CF | 清单分析错误 : 注释中所用的语法不正确。 |
Manifest Parse Error : Incorrect syntax was used in a comment. |
| 0x000036D0 | 清单分析错误 : 名称的起始字符无效。 |
Manifest Parse Error : A name was started with an invalid character. |
| 0x000036D1 | 清单分析错误 : 名称含有无效字符。 |
Manifest Parse Error : A name contained an invalid character. |
| 0x000036D2 | 清单分析错误 : 字符串含有无效字符。 |
Manifest Parse Error : A string literal contained an invalid character. |
| 0x000036D3 | 清单分析错误 : xml 声明的语法无效。 |
Manifest Parse Error : Invalid syntax for an xml declaration. |
| 0x000036D4 | 清单分析错误 : 在文本内容中找到一个无效字符。 |
Manifest Parse Error : An Invalid character was found in text content. |
| 0x000036D5 | 清单分析错误 : 找不到必需的空白区域。 |
Manifest Parse Error : Required white space was missing. |
| 0x000036D6 | 清单分析错误 : 需要带字符 ''。 |
Manifest Parse Error : The character '' was expected. |
| 0x000036D7 | 清单分析错误 : 需要带一个分号字符。 |
Manifest Parse Error : A semi colon character was expected. |
| 0x000036D8 | 清单分析错误 : 括号不平衡。 |
Manifest Parse Error : Unbalanced parentheses. |
| 0x000036D9 | 清单分析错误 : 内部错误。 |
Manifest Parse Error : Internal error. |
| 0x000036DA | 清单分析错误 : 此位置不允许有空白区域。 |
Manifest Parse Error : Whitespace is not allowed at this location. |
| 0x000036DB | 清单分析错误 : 在当前加密的无效状态下达到了文件结尾。 |
Manifest Parse Error : End of file reached in invalid state for current encoding. |
| 0x000036DC | 清单分析错误 : 找不到括号。 |
Manifest Parse Error : Missing parenthesis. |
| 0x000036DD | 清单分析错误 : 找不到右引号(\\' 或 \\\")字符。 |
Manifest Parse Error : A single or double closing quote character (\\' or \\\") is missing. |
| 0x000036DE | 清单分析错误 : 一个名称中不允许多个冒号。 |
Manifest Parse Error : Multiple colons are not allowed in a name. |
| 0x000036DF | 清单分析错误 : 对于十进制数字无效的字符。 |
Manifest Parse Error : Invalid character for decimal digit. |
| 0x000036E0 | 清单分析错误 : 对于十六进制数字无效的字符。 |
Manifest Parse Error : Invalid character for hexadecimal digit. |
| 0x000036E1 | 清单分析错误 : 对于这个平台无效的 unicode 字符值。 |
Manifest Parse Error : Invalid unicode character value for this platform. |
| 0x000036E2 | 清单分析错误 : 要求带空白区域或 '?'。 |
Manifest Parse Error : Expecting whitespace or '?'. |
| 0x000036E3 | 清单分析错误 : 此位置不允许结束标记。 |
Manifest Parse Error : End tag was not expected at this location. |
| 0x000036E4 | 清单分析错误 : 下列标记没有关闭: %1。 |
Manifest Parse Error : The following tags were not closed: %1. |
| 0x000036E5 | 清单分析错误 : 重复属性。 |
Manifest Parse Error : Duplicate attribute. |
| 0x000036E6 | 清单分析错误 : 在 XML 文档中只允许一个最高层元素。 |
Manifest Parse Error : Only one top level element is allowed in an XML document. |
| 0x000036E7 | 清单分析错误 : 文档的最高层无效。 |
Manifest Parse Error : Invalid at the top level of the document. |
| 0x000036E8 | 清单分析错误 : 无效的 xml 声明。 |
Manifest Parse Error : Invalid xml declaration. |
| 0x000036E9 | 清单分析错误 : XML 文档必须有一个最高层元素。 |
Manifest Parse Error : XML document must have a top level element. |
| 0x000036EA | 清单分析错误 : 异常的文件结尾。 |
Manifest Parse Error : Unexpected end of file. |
| 0x000036EB | 清单分析错误 : 无法在内部子集的标记声明内使用参数实体。 |
Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset. |
| 0x000036EC | 清单分析错误 : 没有关闭元素。 |
Manifest Parse Error : Element was not closed. |
| 0x000036ED | 清单分析错误 : 结尾元素没有字符 ''。 |
Manifest Parse Error : End element was missing the character ''. |
| 0x000036EE | 清单分析错误 : 字符串没有关闭。 |
Manifest Parse Error : A string literal was not closed. |
| 0x000036EF | 清单分析错误 : 注释没有关闭。 |
Manifest Parse Error : A comment was not closed. |
| 0x000036F0 | 清单分析错误 : 声明没有关闭。 |
Manifest Parse Error : A declaration was not closed. |
| 0x000036F1 | 清单分析错误 : CDATA 节没有关闭。 |
Manifest Parse Error : A CDATA section was not closed. |
| 0x000036F2 | 清单分析错误 : 命名空间前缀不能以保留字符串 \"xml\" 打头。 |
Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string \"xml\". |
| 0x000036F3 | 清单分析错误 : 系统不支持指定的加密。 |
Manifest Parse Error : System does not support the specified encoding. |
| 0x000036F4 | 清单分析错误 : 不支持从当前加密切换到指定的加密。 |
Manifest Parse Error : Switch from current encoding to specified encoding not supported. |
| 0x000036F5 | 清单分析错误 : 名称 'xml' 是保留的，必须是小写。 |
Manifest Parse Error : The name 'xml' is reserved and must be lower case. |
| 0x000036F6 | 清单分析错误 : 独立属性必须带有 'yes' 或 'no' 值。 |
Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'. |
| 0x000036F7 | 清单分析错误 : 独立属性不能用在外部实体中。 |
Manifest Parse Error : The standalone attribute cannot be used in external entities. |
| 0x000036F8 | 清单分析错误 : 无效的版本编号。 |
Manifest Parse Error : Invalid version number. |
| 0x000036F9 | 清单分析错误 : 属性和属性值之间没有等于号。 |
Manifest Parse Error : Missing equals sign between attribute and attribute value. |
| 0x000036FA | 汇编保护错误 : 无法恢复指定的汇编。 |
Assembly Protection Error : Unable to recover the specified assembly. |
| 0x000036FB | 汇编保护错误 : 汇编的公钥太短，不允许。 |
Assembly Protection Error : The public key for an assembly was too short to be allowed. |
| 0x000036FC | 汇编保护错误 : 汇编的目录无效，或者跟汇编的清单不匹配。 |
Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest. |
| 0x000036FD | 无法将 HRESULT 转换成相应的 Win32 错误代码。 |
An HRESULT could not be translated to a corresponding Win32 error code. |
| 0x000036FE | 汇编保护错误 : 找不到汇编的目录。 |
Assembly Protection Error : The catalog for an assembly is missing. |
| 0x000036FF | 提供的汇编身份丢失在上下文中必须存在的一个或多个属性。 |
The supplied assembly identity is missing one or more attributes which must be present in this context. |
| 0x00003700 | 提供的汇编身份有一个或多个属性名称包含在 XML 名称中不允许使用的字符。 |
The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names. |
| 0x00003701 | 找不到引用的汇编。 |
The referenced assembly could not be found. |
| 0x00003702 | 激活上下文激活堆栈损坏，该堆栈用于执行运行的线程。 |
The activation context activation stack for the running thread of execution is corrupt. |
| 0x00003703 | 此进程或线程的应用程序隔离无程序已经损坏。 |
The application isolation metadata for this process or thread has become corrupt. |
| 0x00003704 | 正被停用的激活上下文不是最近激活的。 |
The activation context being deactivated is not the most recently activated one. |
| 0x00003705 | 正被停用的激活上下文对于当前执行线程来说不是活动的。 |
The activation context being deactivated is not active for the current thread of execution. |
| 0x00003706 | 正被停用的激活上下文已被停用了。 |
The activation context being deactivated has already been deactivated. |
| 0x00003707 | 孤立设施使用的组件已经请求结束此进程。 |
A component used by the isolation facility has requested to terminate the process. |
| 0x00003708 | 内核模式组件正在释放激活上下文上的参照。 |
A kernel mode component is releasing a reference on an activation context. |
| 0x00003709 | 无法生成系统默认汇编的激活上下文。 |
The activation context of system default assembly could not be generated. |
| 0x0000370A | 标识中属性的值不在合法范围内。 |
The value of an attribute in an identity is not within the legal range. |
| 0x0000370B | 标识中属性的名称不在合法范围内。 |
The name of an attribute in an identity is not within the legal range. |
| 0x0000370C | 标识包含同一属性的两个定义。 |
An identity contains two definitions for the same attribute. |
| 0x0000370D | 标识字符串格式错误。这可能是因为尾部的逗号、两个以上未命名的属性、缺少属性名称或缺少属性值。 |
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. |
| 0x0000370E | 包含已本地化的可替换内容的字符串格式错误。美元符号($)后面不是左括号，或者找不到另一个美元符号或替代部分的右括号。 |
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. |
| 0x0000370F | 公钥令牌与指定的公钥不对应。 |
The public key token does not correspond to the public key specified. |
| 0x00003710 | 替换字符串不具有映射。 |
A substitution string had no mapping. |
| 0x00003711 | 在请求之前必须锁定组件。 |
The component must be locked before making the request. |
| 0x00003712 | 组件存储已损坏。 |
The component store has been corrupted. |
| 0x00003713 | 高级安装程序在安装或提供服务时失败。 |
An advanced installer failed during setup or servicing. |
| 0x00003714 | XML 声明中的字符编码与文档中使用的编码不匹配。 |
The character encoding in the XML declaration did not match the encoding used in the document. |
| 0x00003715 | 清单的标识相同，但其内容不同。 |
The identities of the manifests are identical but their contents are different. |
| 0x00003716 | 组件标识不同。 |
The component identities are different. |
| 0x00003717 | 程序集并非部署。 |
The assembly is not a deployment. |
| 0x00003718 | 该文件不是程序集的一部分。 |
The file is not a part of the assembly. |
| 0x00003719 | 清单大小超出允许的最大值。 |
The size of the manifest exceeds the maximum allowed. |
| 0x0000371A | 设置未注册。 |
The setting is not registered. |
| 0x0000371B | 一个或多个要求的事务成员不存在。 |
One or more required members of the transaction are not present. |
| 0x0000371C | SMI 基元安装程序在安装或服务过程中失败。 |
The SMI primitive installer failed during setup or servicing. |
| 0x0000371D | 可执行的通用命令返回一个指示失败的结果。 |
A generic command executable returned a result that indicates failure. |
| 0x0000371E | 某组件的清单中缺少文件验证信息。 |
A component is missing file verification information in its manifest. |
| 0x00003A98 | 指定的通道路径无效。 |
The specified channel path is invalid. |
| 0x00003A99 | 指定的队列无效。 |
The specified query is invalid. |
| 0x00003A9A | 资源中无法找到发布服务器上的元数据。 |
The publisher metadata cannot be found in the resource. |
| 0x00003A9B | 资源中找不到事件定义的模板(错误 = %1)。 |
The template for an event definition cannot be found in the resource (error = %1). |
| 0x00003A9C | 指定的发布服务器名称无效。 |
The specified publisher name is invalid. |
| 0x00003A9D | 发布服务器引发的事件数据与发布服务器清单中的事件模板定义不兼容。 |
The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest |
| 0x00003A9F | 无法找到指定的通道。请检查通道配置。 |
The specified channel could not be found. Check channel configuration. |
| 0x00003AA0 | 指定的 xml 文本格式错误。有关详细信息，请参阅扩展错误。 |
The specified xml text was not well-formed. See Extended Error for more details. |
| 0x00003AA1 | 调用方尝试订阅不允许的直接通道。直接通道的事件直接进入日志文件，无法订阅。 |
The 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. |
| 0x00003AA2 | 配置错误。 |
Configuration error. |
| 0x00003AA3 | 查询结果过时/无效。这可能是由于在创建查询结果后，日志被清除或已滚动。用户应该通过释放查询结果对象并重新发布查询来处理该代码。 |
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. |
| 0x00003AA4 | 查询结果目前处于无效位置。 |
Query result is currently at an invalid position. |
| 0x00003AA5 | 注册的 MSXML 不支持验证。 |
Registered MSXML doesn't support validation. |
| 0x00003AA6 | 如果表达式本身计算的结果是节点集并且在此前它不是其他范围运算更改的一部分，那么它的后面就只能跟范围运算更改。 |
An 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. |
| 0x00003AA7 | 无法根据不表示元素集的术语执行步骤操作。 |
Can't perform a step operation from a term that does not represent an element set. |
| 0x00003AA8 | 二进制运算符的左侧参数必须是属性、节点或变量右侧参数必须是常量。 |
Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants. |
| 0x00003AA9 | 步骤操作必须包括节点测试，或代数表达式(在是谓词的情况下)，根据此代数表达式，可以计算对前一个节点集所标识的节点集中的每个节点进行的测试。 |
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. |
| 0x00003AAA | 目前不支持这种数据类型。 |
This data type is currently unsupported. |
| 0x00003AAB | 在位置 %1!d! 发生语法错误 |
A syntax error occurred at position %1!d! |
| 0x00003AAC | 筛选器的执行不支持该运算符。 |
This operator is unsupported by this implementation of the filter. |
| 0x00003AAD | 遇到意料之外的令牌。 |
The token encountered was unexpected. |
| 0x00003AAE | 无法通过启用的直达信道执行该请求操作。执行请求操作之前必须首先禁用该信道。 |
The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation. |
| 0x00003AAF | 信道属性 %1!s! 包含无效值。该值类型无效，超出了有效范围，无法更新或者不受该类型信道的支持。 |
Channel 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. |
| 0x00003AB0 | 发布服务器属性 %1!s! 包含无效值。该值类型无效，超出了有效范围，无法更新或者不受该类型发布服务器的支持。 |
Publisher 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. |
| 0x00003AB1 | 无法激活该信道。 |
The channel fails to activate. |
| 0x00003AB2 | xpath 表达式超出所支持的复杂度。请将其进行简化或将其拆分为两个或更多的简单表达式。 |
The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple expressions. |
| 0x00003AB3 | 消息资源存在，但在字符串/消息表中找不到该消息 |
the message resource is present but the message is not found in the string/message table |
| 0x00003AB4 | 无法找到所需消息的消息 ID。 |
The message id for the desired message could not be found. |
| 0x00003AB5 | 无法找到插入索引(%1)的替换字符串。 |
The substitution string for insert index (%1) could not be found. |
| 0x00003AB6 | 无法找到参数引用(%1)的描述字符串。 |
The description string for parameter reference (%1) could not be found. |
| 0x00003AB7 | 已达到最大替换数。 |
The maximum number of replacements has been reached. |
| 0x00003AB8 | 无法找到事件 ID (%1)的事件定义。 |
The event definition could not be found for event id (%1). |
| 0x00003AB9 | 缺少所需消息的区域设置特定资源。 |
The locale specific resource for the desired message is not present. |
| 0x00003ABA | 资源太旧，无法兼容。 |
The resource is too old to be compatible. |
| 0x00003ABB | 资源太新，无法兼容。 |
The resource is too new to be compatible. |
| 0x00003ABC | 位于查询索引 %1!d! 处的通道无法打开。 |
The channel at index %1!d! of the query can't be opened. |
| 0x00003ABD | 该发布程序已禁用，其资源不可用。通常在卸载或升级发布程序过程中会出现这种情况。 |
The 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. |
| 0x00003ABE | 尝试创建一个超过其有效范围的数字类型。 |
Attempted to create a numeric type that is outside of its valid range. |
| 0x00003AE8 | 无法激活订阅。 |
The subscription fails to activate. |
| 0x00003AE9 | 订阅的日志处于禁用状态，无法将其用于转发事件。必须首先启用该日志才能激活订阅。 |
The 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. |
| 0x00003AEA | 将本地计算机的事件转发给自身时，订阅查询不能含有订阅的目标日志。 |
When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription. |
| 0x00003AEB | 用来保存凭据的凭据存储区已满。 |
The credential store that is used to save credentials is full. |
| 0x00003AEC | 无法在凭据存储区中找到此订阅使用的凭据。 |
The credential used by this subscription can't be found in credential store. |
| 0x00003AED | 未找到查询的任何活动通道。 |
No active channel is found for the query. |
| 0x00003AFC | 资源加载器找不到 MUI 文件。 |
The resource loader failed to find MUI file. |
| 0x00003AFD | 资源加载器未能加载 MUI 文件，因为文件未能通过验证。 |
The resource loader failed to load MUI file because the file fail to pass validation. |
| 0x00003AFE | RC 清单已被垃圾数据或不支持的版本损坏，或缺少必需的项目。 |
The RC Manifest is corrupted with garbage data or unsupported version or missing required item. |
| 0x00003AFF | RC 清单的区域性名称无效。 |
The RC Manifest has invalid culture name. |
| 0x00003B00 | RC 清单的 ultimatefallback 名称无效。 |
The RC Manifest has invalid ultimatefallback name. |
| 0x00003B01 | 资源加载器缓存没有已加载的 MUI 项。 |
The resource loader cache doesn't have loaded MUI entry. |
| 0x00003B02 | 用户已停止资源枚举。 |
User stopped resource enumeration. |
| 0x00003B03 | UI 语言安装失败。 |
UI language installation failed. |
| 0x00003B04 | 区域设置安装失败。 |
Locale installation failed. |
| 0x00003B06 | 资源没有默认值或中性值。 |
A resource does not have default or neutral value. |
| 0x00003B07 | 无效的 PRI 配置文件。 |
Invalid PRI config file. |
| 0x00003B08 | 文件类型无效。 |
Invalid file type. |
| 0x00003B09 | 未知的限定符。 |
Unknown qualifier. |
| 0x00003B0A | 无效的限定符值。 |
Invalid qualifier value. |
| 0x00003B0B | 未找到候选者。 |
No Candidate found. |
| 0x00003B0C | ResourceMap 或 NamedResource 具有没有默认资源或非特定区域性资源的项目。 |
The ResourceMap or NamedResource has an item that does not have default or neutral resource.. |
| 0x00003B0D | 无效的 ResourceCandidate 类型。 |
Invalid ResourceCandidate type. |
| 0x00003B0E | 重复的资源映射。 |
Duplicate Resource Map. |
| 0x00003B0F | 重复的条目。 |
Duplicate Entry. |
| 0x00003B10 | 无效的资源标识符。 |
Invalid Resource Identifier. |
| 0x00003B11 | 文件路径过长。 |
Filepath too long. |
| 0x00003B12 | 不受支持的目录类型。 |
Unsupported directory type. |
| 0x00003B16 | 无效的 PRI 文件。 |
Invalid PRI File. |
| 0x00003B17 | 找不到 NamedResource。 |
NamedResource Not Found. |
| 0x00003B1F | 未找到 ResourceMap。 |
ResourceMap Not Found. |
| 0x00003B20 | 不支持 MRT 配置文件类型。 |
Unsupported MRT profile type. |
| 0x00003B21 | 限定符运算符无效。 |
Invalid qualifier operator. |
| 0x00003B22 | 无法确定或未设置限定符值。 |
Unable to determine qualifier value or qualifier value has not been set. |
| 0x00003B23 | 在 PRI 文件中启用了自动合并。 |
Automerge is enabled in the PRI file. |
| 0x00003B24 | 为程序包定义了太多资源。 |
Too many resources defined for package. |
| 0x00003B25 | 无法使用资源文件执行合并操作。 |
Resource File can not be used for merge operation. |
| 0x00003B26 | 不能将 Load/UnloadPriFiles 用于资源包。 |
Load/UnloadPriFiles cannot be used with resource packages. |
| 0x00003B27 | 无法在没有 CoreWindow 的线程上创建资源上下文。 |
Resource Contexts may not be created on threads that do not have a CoreWindow. |
| 0x00003B28 | 已创建包含不同配置文件的单一资源管理器。 |
The singleton Resource Manager with different profile is already created. |
| 0x00003B29 | 系统组件无法执行给定的 API 操作 |
The system component cannot operate given API operation |
| 0x00003B2A | 资源直接引用了非默认的候选资源。 |
The resource is a direct reference to a non-default resource candidate. |
| 0x00003B2B | 已重新生成资源映射，因此查询字符串不再有效。 |
Resource Map has been re-generated and the query string is not valid anymore. |
| 0x00003B2C | 要合并的 PRI 文件的版本不兼容。 |
The PRI files to be merged have incompatible versions. |
| 0x00003B2D | 要合并的主要 PRI 文件不包含架构。 |
The primary PRI files to be merged does not contain a schema. |
| 0x00003B2E | 无法加载要合并的 PRI 文件之一。 |
Unable to load one of the PRI files to be merged. |
| 0x00003B2F | 无法将其中一个 PRI 文件添加到合并文件。 |
Unable to add one of the PRI files to the merged file. |
| 0x00003B30 | 无法创建合并 PRI 文件。 |
Unable to create the merged PRI file. |
| 0x00003B31 | 用于 PRI 文件合并的程序包必须全部来自同一程序包系列。 |
Packages for a PRI file merge must all be from the same package family. |
| 0x00003B32 | 用于 PRI 文件合并的程序包不能包含多个主程序包。 |
Packages for a PRI file merge must not include multiple main packages. |
| 0x00003B33 | 用于 PRI 文件合并的程序包不能包含捆绑包。 |
Packages for a PRI file merge must not include bundle packages. |
| 0x00003B34 | 用于 PRI 文件合并的程序包必须包含一个主程序包。 |
Packages for a PRI file merge must include one main package. |
| 0x00003B35 | 用于 PRI 文件合并的程序包必须至少包含一个资源包。 |
Packages for a PRI file merge must include at least one resource package. |
| 0x00003B36 | 为规范合并 PRI 文件提供了无效名称。 |
Invalid name supplied for a canonical merged PRI file. |
| 0x00003B60 | 监视器返回 DDC/CI 功能字符串，该字符串不符合 ACCESS.bus 3.0、DDC/CI 1.1 或 MCCS 2 修订版 1 规范。 |
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. |
| 0x00003B61 | 监视器的 VCP 版(0xDF) VCP 代码返回一个无效的版本值。 |
The monitor's VCP Version (0xDF) VCP code returned an invalid version value. |
| 0x00003B62 | 监视器不符合其声明支持的 MCCS 规范。 |
The monitor does not comply with the MCCS specification it claims to support. |
| 0x00003B63 | 监视器的 mccs_ver 功能中的 MMCS 版本与使用 VCP 版(0xDF) VCP 代码时报告的 MCCS 版本不匹配。 |
The 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. |
| 0x00003B64 | 监视器配置 API 仅用于支持 MCCS 1.0 规范、MCCS 2.0 规范或 MCCS 2.0 修订版 1 规范的监视器。 |
The 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. |
| 0x00003B65 | 发生内部监视器配置 API 错误。 |
An internal Monitor Configuration API error occurred. |
| 0x00003B66 | 监视器返回无效的监视器技术类型。CRT、等离子和 LCD (TFT)都是监视器技术类型的示例。这种错误表示监视器违反了 MCCS 2.0 规范或 MCCS 2.0 修订本 1 规范。 |
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. |
| 0x00003B67 | SetMonitorColorTemperature 的调用者指定了当前监视器不支持的色温。该错误表示此监视器违反了 MCCS 2.0 规范或 MCCS 2.0 修订版 1 规范。 |
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. |
| 0x00003B92 | 由于可能有多个不可辨别的设备与识别条件相匹配，无法识别所请求的系统设备。 |
The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. |
| 0x00003BC3 | 找不到请求的系统设备。 |
The requested system device cannot be found. |
| 0x00003BC4 | 在服务器上未对指定的哈希版本和哈希类型启用哈希生成。 |
Hash generation for the specified hash version and hash type is not enabled on the server. |
| 0x00003BC5 | 从服务器请求的哈希不可用或不再有效。 |
The hash requested from the server is not available or no longer valid. |
| 0x00003BD9 | 未注册用于管理指定中断的辅助中断控制器实例。 |
The secondary interrupt controller instance that manages the specified interrupt is not registered. |
| 0x00003BDA | GPIO 客户端驱动程序提供的信息无效。 |
The information supplied by the GPIO client driver is invalid. |
| 0x00003BDB | GPIO 客户端驱动程序指定的版本不受支持。 |
The version specified by the GPIO client driver is not supported. |
| 0x00003BDC | GPIO 客户端驱动程序提供的注册数据包无效。 |
The registration packet supplied by the GPIO client driver is not valid. |
| 0x00003BDD | 指定的句柄不支持请求的操作。 |
The requested operation is not suppported for the specified handle. |
| 0x00003BDE | 请求的连接模式与一个或多个指定的 PIN 上的现有模式冲突。 |
The requested connect mode conflicts with an existing mode on one or more of the specified pins. |
| 0x00003BDF | 请求取消屏蔽的中断未被屏蔽。 |
The interrupt requested to be unmasked is not masked. |
| 0x00003C28 | 无法成功完成请求的运行级别切换。 |
The requested run level switch cannot be completed successfully. |
| 0x00003C29 | 服务含有无效的运行级别设置。服务的运行级别不得高于从属服务的运行级别。 |
The service has an invalid run level setting. The run level for a servicemust not be higher than the run level of its dependent services. |
| 0x00003C2A | 无法成功完成请求的运行级别切换，因为在指定的超时时间内一个或多个服务将不会停止或重新启动。 |
The requested run level switch cannot be completed successfully sinceone or more services will not stop or restart within the specified timeout. |
| 0x00003C2B | 在指定的超时时间内，运行级别切换代理未响应。 |
A run level switch agent did not respond within the specified timeout. |
| 0x00003C2C | 运行级别切换当前正在进行。 |
A run level switch is currently in progress. |
| 0x00003C2D | 在运行级别切换的服务启动阶段，一个或多个服务无法启动。 |
One or more services failed to start during the service startup phase of a run level switch. |
| 0x00003C8D | 无法立即完成任务停止请求，原因是任务需要更多时间来关闭。 |
The task stop request cannot be completed immediately sincetask needs more time to shutdown. |
| 0x00003CF0 | 无法打开包。 |
Package could not be opened. |
| 0x00003CF1 | 找不到包。 |
Package was not found. |
| 0x00003CF2 | 包数据无效。 |
Package data is invalid. |
| 0x00003CF3 | 包无法进行更新、相关性或冲突验证。 |
Package failed updates, dependency or conflict validation. |
| 0x00003CF4 | 你计算机上的磁盘空间不足。请释放一些空间再重试。 |
There is not enough disk space on your computer. Please free up some space and try again. |
| 0x00003CF5 | 下载你的产品时出错。 |
There was a problem downloading your product. |
| 0x00003CF6 | 无法注册包。 |
Package could not be registered. |
| 0x00003CF7 | 无法取消注册包。 |
Package could not be unregistered. |
| 0x00003CF8 | 用户已取消安装请求。 |
User cancelled the install request. |
| 0x00003CF9 | 无法安装。请联系你的软件供应商。 |
Install failed. Please contact your software vendor. |
| 0x00003CFA | 无法卸载。请联系你的软件供应商。 |
Removal failed. Please contact your software vendor. |
| 0x00003CFB | 提供的程序包已安装，且禁止重新安装该程序包。请检查 AppXDeployment-Server 事件日志了解详细信息。 |
The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details. |
| 0x00003CFC | 无法启动此应用程序。请尝试重新安装应用程序以解决该问题。 |
The application cannot be started. Try reinstalling the application to fix the problem. |
| 0x00003CFD | 无法满足安装的先决条件。 |
A Prerequisite for an install could not be satisfied. |
| 0x00003CFE | 包存储库已损坏。 |
The package repository is corrupted. |
| 0x00003CFF | 要安装此应用程序，需要有 Windows 开发者许可证或启用旁加载的系统。 |
To install this application you need either a Windows developer license or a sideloading-enabled system. |
| 0x00003D00 | 无法启动应用程序，因为该程序当前正在更新。 |
The application cannot be started because it is currently updating. |
| 0x00003D01 | 策略已阻止程序包部署操作。请与你的系统管理员联系。 |
The package deployment operation is blocked by policy. Please contact your system administrator. |
| 0x00003D02 | 无法安装程序包，原因是它修改的资源当前正在使用中。 |
The package could not be installed because resources it modifies are currently in use. |
| 0x00003D03 | 无法恢复程序包，原因是恢复所需的数据已损坏。 |
The package could not be recovered because necessary data for recovery have been corrupted. |
| 0x00003D04 | 签名无效。若要在开发人员模式下注册，AppxSignature.p7x 和 AppxBlockMap.xml 必须有效或应该不存在。 |
The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present. |
| 0x00003D05 | 删除程序包先前已有的应用程序数据时出错。 |
An error occurred while deleting the package's previously existing application data. |
| 0x00003D06 | 无法安装此程序包，因为已安装该程序包的更高版本。 |
The package could not be installed because a higher version of this package is already installed. |
| 0x00003D07 | 在系统二进制文件中检测到错误。请尝试恢复电脑以解决该问题。 |
An error in a system binary was detected. Try refreshing the PC to fix the problem. |
| 0x00003D08 | 在系统上检测到损坏的 CLR NGEN 二进制文件。 |
A corrupted CLR NGEN binary was detected on the system. |
| 0x00003D09 | 无法恢复操作，原因是恢复所需的数据已损坏。 |
The operation could not be resumed because necessary data for recovery have been corrupted. |
| 0x00003D0A | 无法安装该程序包，因为 Windows 防火墙服务未运行。请启用 Windows 防火墙服务并重试。 |
The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again. |
| 0x00003D0B | 包移动失败。 |
Package move failed. |
| 0x00003D0C | 部署操作失败，因为卷不是空的。 |
The deployment operation failed because the volume is not empty. |
| 0x00003D0D | 部署操作失败，因为卷处于脱机状态。 |
The deployment operation failed because the volume is offline. |
| 0x00003D0E | 由于指定的卷已损坏，部署操作失败。 |
The deployment operation failed because the specified volume is corrupt. |
| 0x00003D0F | 由于指定的应用程序需要先注册，部署操作失败。 |
The deployment operation failed because the specified application needs to be registered first. |
| 0x00003D10 | 部署操作失败，因为该程序包针对的是错误的处理器体系结构。 |
The deployment operation failed because the package targets the wrong processor architecture. |
| 0x00003D11 | 已达到此设备上允许的开发人员旁加载程序包的最大数量。请卸载旁加载程序包，然后重试。 |
You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again. |
| 0x00003D12 | 需要主要应用程序包才能安装此可选程序包。请先安装主程序包，然后重试。 |
A main app package is required to install this optional package. Install the main package first and try again. |
| 0x00003D13 | 此文件系统不支持该应用程序包类型 |
This app package type is not supported on this filesystem |
| 0x00003D14 | 程序包移动操作将被阻止，直到应用程序完成流式传输 |
Package move operation is blocked until the application has finished streaming |
| 0x00003D15 | 主应用包或另一个可选应用包的应用程序 ID 与此可选包相同。请更改可选包的应用程序 ID 以避免冲突。 |
A main or another optional app package has the same application ID as this optional package. Change the application ID for the optional package to avoid conflicts. |
| 0x00003D16 | 保持该暂存会话，以允许优先处理另一个暂存操作。 |
This staging session has been held to allow another staging operation to be prioritized. |
| 0x00003D17 | 无法更新相关设置，因为更新后的设置无效。必须同时更新相关设置中的所有包。 |
A related set cannot be updated because the updated set is invalid. All packages in the related set must be updated at the same time. |
| 0x00003D18 | 拥有一个 FullTrust 入口点的可选程序包要求主程序包具备 runFullTrust 功能。 |
An optional package with a FullTrust entry point requires the main package to have the runFullTrust capability. |
| 0x00003D54 | 该进程没有程序包标识符。 |
The process has no package identity. |
| 0x00003D55 | 程序包运行时信息已损坏。 |
The package runtime information is corrupted. |
| 0x00003D56 | 程序包标识符已损坏。 |
The package identity is corrupted. |
| 0x00003D57 | 进程没有应用程序标识。 |
The process has no application identity. |
| 0x00003D58 | 无法读取一个或多个 AppModel 运行时组策略值。有关 AppModel 运行时事件日志的内容，请与系统管理员联系。 |
One 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. |
| 0x00003D59 | 一个或多个 AppModel 运行时组策略值无效。有关 AppModel 运行时事件日志的内容，请与系统管理员联系。 |
One or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log. |
| 0x00003D5A | 包当前不可用。 |
The package is currently not available. |
| 0x00003DB8 | 无法加载状态存储。 |
Loading the state store failed. |
| 0x00003DB9 | 无法检索应用程序的状态版本。 |
Retrieving the state version for the application failed. |
| 0x00003DBA | 无法设置应用程序的状态版本。 |
Setting the state version for the application failed. |
| 0x00003DBB | 无法重置应用程序的结构状态。 |
Resetting the structured state of the application failed. |
| 0x00003DBC | 状态管理器无法打开容器。 |
State Manager failed to open the container. |
| 0x00003DBD | 状态管理器无法创建容器。 |
State Manager failed to create the container. |
| 0x00003DBE | 状态管理器无法删除容器。 |
State Manager failed to delete the container. |
| 0x00003DBF | 状态管理器无法读取设置。 |
State Manager failed to read the setting. |
| 0x00003DC0 | 状态管理器无法写入设置。 |
State Manager failed to write the setting. |
| 0x00003DC1 | 状态管理器无法删除设置。 |
State Manager failed to delete the setting. |
| 0x00003DC2 | 状态管理器无法查询设置。 |
State Manager failed to query the setting. |
| 0x00003DC3 | 状态管理器无法读取复合设置。 |
State Manager failed to read the composite setting. |
| 0x00003DC4 | 状态管理器无法写入复合设置。 |
State Manager failed to write the composite setting. |
| 0x00003DC5 | 状态管理器无法枚举容器。 |
State Manager failed to enumerate the containers. |
| 0x00003DC6 | 状态管理器无法枚举设置。 |
State Manager failed to enumerate the settings. |
| 0x00003DC7 | 状态管理器复合设置值的大小已超出限制。 |
The size of the state manager composite setting value has exceeded the limit. |
| 0x00003DC8 | 状态管理器设置值的大小已超出限制。 |
The size of the state manager setting value has exceeded the limit. |
| 0x00003DC9 | 状态管理器设置名称的长度已超出限制。 |
The length of the state manager setting name has exceeded the limit. |
| 0x00003DCA | 状态管理器容器名称的长度已超出限制。 |
The length of the state manager container name has exceeded the limit. |
| 0x00003DE1 | 无法在调用者的应用程序类型上下文中使用此 API。 |
This API cannot be used in the context of the caller's application type. |
| 0x00003DF5 | 这台电脑没有此应用程序或产品的有效许可。 |
This PC does not have a valid license for the application or product. |
| 0x00003DF6 | 经过身份验证的用户没有此应用程序或产品的有效许可。 |
The authenticated user does not have a valid license for the application or product. |
| 0x00003DF7 | 与此许可证有关的电子商务交易仍在等待验证。 |
The commerce transaction associated with this license is still pending verification. |
| 0x00003DF8 | 此用户的许可证已被吊销。 |
The license has been revoked for this user. |
| 0x00030200 | 文件被转换成复合文件格式。 |
The underlying file was converted to compound file format. |
| 0x00030201 | 该存储操作应当等到有更多的数据时再进行操作。 |
The storage operation should block until more data is available. |
| 0x00030202 | 应当立即重试该存储操作。 |
The storage operation should retry immediately. |
| 0x00030203 | 已通知的事件记录将不会影响存储操作。 |
The notified event sink will not influence the storage operation. |
| 0x00030204 | 多重打开造成无法合并。(确认成功)。 |
Multiple opens prevent consolidated. (commit succeeded). |
| 0x00030205 | 存储文件的合并失败。(确认成功)。 |
Consolidation of the storage file failed. (commit succeeded). |
| 0x00030206 | 存储文件的合并不适当。(确认成功)。 |
Consolidation of the storage file is inappropriate. (commit succeeded). |
| 0x00030207 | 该设备需要重启电源。(确认成功)。 |
The device needs to be power cycled. (commit succeeded). |
| 0x00040000 | 使用注册表数据库提供请求的信息 |
Use the registry database to provide the requested information |
| 0x00040001 | 成功，但是静态 |
Success, but static |
| 0x00040002 | Macintosh 剪贴板格式 |
Macintosh clipboard format |
| 0x00040100 | 拖放成功 |
Successful drop took place |
| 0x00040101 | 取消拖动操作 |
Drag-drop operation canceled |
| 0x00040102 | 使用默认光标 |
Use the default cursor |
| 0x00040130 | 数据有相同的 FORMATETC |
Data has same FORMATETC |
| 0x00040140 | 查看已冻结 |
View is already frozen |
| 0x00040170 | 未支持 FORMATETC |
FORMATETC not supported |
| 0x00040171 | 相同的缓存 |
Same cache |
| 0x00040172 | 相同的缓存未更新 |
Some cache(s) not updated |
| 0x00040180 | OLE 对象动词无效 |
Invalid verb for OLE object |
| 0x00040181 | 操作编号有效，但是操作当前无法完成 |
Verb number is valid but verb cannot be done now |
| 0x00040182 | 传递了无效的窗口句柄 |
Invalid window handle passed |
| 0x000401A0 | 信息太长，某些部分在显示前必须截断 |
Message is too long; some of it had to be truncated before displaying |
| 0x000401C0 | 无法将 OLESTREAM 转换成 IStorage |
Unable to convert OLESTREAM to IStorage |
| 0x000401E2 | Moniker 缩减成自己本身 |
Moniker reduced to itself |
| 0x000401E4 | 共同前缀是这个标记 |
Common prefix is this moniker |
| 0x000401E5 | 共同前缀是输入标记 |
Common prefix is input moniker |
| 0x000401E6 | 共同前缀是这两个标记 |
Common prefix is both monikers |
| 0x000401E7 | 标记已注册在运行中的对象表中 |
Moniker is already registered in running object table |
| 0x00040200 | 事件能调用一些但不是所有的订户 |
An event was able to invoke some but not all of the subscribers |
| 0x00040202 | 事件被传递，但没有订户 |
An event was delivered but there were no subscribers |
| 0x00040252 | 平板电脑墨迹错误代码。字符串被截断 |
TabletPC inking error code. String was truncated |
| 0x00040253 | 平板电脑墨迹错误代码。识别或定型已中断 |
TabletPC inking error code. Recognition or training was interrupted |
| 0x00040254 | 平板电脑墨迹错误代码。未对识别器进行个性化更新，因为未找到定型数据 |
TabletPC inking error code. No personalization update to the recognizer because no training data found |
| 0x00041300 | 任务准备在下次计划的时间运行。 |
The task is ready to run at its next scheduled time. |
| 0x00041301 | 正在运行任务。 |
The task is currently running. |
| 0x00041302 | 由于已被停用，任务不会在计划的时间运行。 |
The task will not run at the scheduled times because it has been disabled. |
| 0x00041303 | 任务尚未运行。 |
The task has not yet run. |
| 0x00041304 | 没有为这个任务计划的运行操作了。 |
There are no more runs scheduled for this task. |
| 0x00041305 | 至少有一个运行这个任务所需的属性尚未设置。 |
One or more of the properties that are needed to run this task on a schedule have not been set. |
| 0x00041306 | 任务的最后一次运行被用户终止。 |
The last run of the task was terminated by the user. |
| 0x00041307 | 任务没有触发器，或者现有触发器已被停用或尚未设置。 |
Either the task has no triggers or the existing triggers are disabled or not set. |
| 0x00041308 | 事件触发器没有设定的运行时间。 |
Event triggers don't have set run times. |
| 0x0004131B | 任务已注册，但不是所有指定的触发器都将启动该任务，请参阅任务计划程序事件日志了解详细信息。 |
The task is registered, but not all specified triggers will start the task, check task scheduler event log for detailed information. |
| 0x0004131C | 任务已注册，但无法启动。该任务主体需要启用批登录特权。 |
The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal. |
| 0x00041325 | 任务计划程序服务要求运行任务。 |
The Task Scheduler service has asked the task to run. |
| 0x0004D000 | 指定了一个异步操作。该操作已经开始，但是还不知道它的结果。 |
An asynchronous operation was specified. The operation has begun, but its outcome is not known yet. |
| 0x0004D001 | XACT_S_DEFECT |
XACT_S_DEFECT |
| 0x0004D002 | 调用该方法成功，因为此事务为只读的。 |
The method call succeeded because the transaction was read-only. |
| 0x0004D003 | 成功中止此事务。然而，这是一个协调的事务，并且列入资源的某些数字被彻底中止，因为它们不能支持中止-保留语义 |
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 |
| 0x0004D004 | 此调用过程中没有任何更改，但是接收器需要再看一次是否有其他接收器做了进一步更改。 |
No changes were made during this call, but the sink wants another chance to look if any other sinks make further changes. |
| 0x0004D005 | 接收器满意并希望办理事务。在此调用过程中，一个或多个资源有更改。 |
The sink is content and wishes the transaction to proceed. Changes were made to one or more resources during this call. |
| 0x0004D006 | 接收器是暂时的并希望办理事务，但是如果在此回车后其他事件接收器有其他更改，那么这个接收器希望再看一次 |
The 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 |
| 0x0004D007 | 该事务被成功中止。但是此中止是不保留的。 |
The transaction was successfully aborted. However, the abort was non-retaining. |
| 0x0004D008 | 正在进行一个中止操作。 |
An abort operation was already in progress. |
| 0x0004D009 | 资源管理器执行了此事务的单步确认。 |
The resource manager has performed a single-phase commit of the transaction. |
| 0x0004D00A | 本地事务尚未中止。 |
The local transaction has not aborted. |
| 0x0004D010 | 资源管理器已申请作为该事务的协调器(上一个资源管理器)。 |
The resource manager has requested to be the coordinator (last resource manager) for the transaction. |
| 0x00080012 | 并不是所有需求的接口都存在。 |
Not all the requested interfaces were available |
| 0x00080013 | 缓存中找不到指定的计算机名。 |
The specified machine name was not found in the cache. |
| 0x00090312 | 函数成功结束，但必须再次调用以完成上下文 |
The function completed successfully, but must be called again to complete the context |
| 0x00090313 | 函数成功结束，但必须调用 CompleteToken |
The function completed successfully, but CompleteToken must be called |
| 0x00090314 | 函数成功结束，但必须调用 CompleteToken 和该函数才能完成上下文 |
The function completed successfully, but both CompleteToken and this function must be called to complete the context |
| 0x00090315 | 登录已完成，但没有可用的网络权限。以本地已知信息登录。 |
The logon was completed, but no network authority was available. The logon was made using locally known information |
| 0x00090320 | 提供的凭证不完全，因此无法验证。其他信息可以从上下文返回。 |
The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context. |
| 0x00090321 | 必须与对等机重新协商上下文数据。 |
The context data must be renegotiated with the peer. |
| 0x00090323 | 没有与这个上下文相关的 LSA 模式上下文。 |
There is no LSA mode context associated with this context. |
| 0x0009035C | 用户在进行身份验证之前必须执行签名操作。 |
A signature operation must be performed before the user can authenticate. |
| 0x00090360 | 收件人拒绝重新商议请求。 |
The recipient rejected the renegotiation request. |
| 0x00090364 | 返回的缓冲区仅为消息的一个片段。需要返回更多的片段。 |
The returned buffer is only a fragment of the message. More fragments need to be returned. |
| 0x00090366 | 该函数已成功完成，但必须再次调用以完成上下文。可能使用了预先启动。 |
The function completed successfully, but must be called again to complete the context. Early start can be used. |
| 0x00090368 | 已调用异步 SSPI 例程，工作有待完成。 |
An asynchronous SSPI routine has been called and the work is pending completion. |
| 0x00091012 | 受保护的数据需要重新受保护。 |
The protected data needs to be re-protected. |
| 0x001B0000 | 已连接调试程序。 |
Debugger was attached. |
| 0x001B0001 | 已上载报告。 |
Report was uploaded. |
| 0x001B0002 | 已将报告排入队列。 |
Report was queued. |
| 0x001B0003 | 已禁用报告。 |
Reporting was disabled. |
| 0x001B0004 | 已临时暂停报告。 |
Reporting was temporarily suspended. |
| 0x001B0005 | 由于禁用了排队，报告未排入队列。 |
Report was not queued to queueing being disabled. |
| 0x001B0006 | 已上载报告，但由于禁用了存档而未存档。 |
Report was uploaded, but not archived due to archiving being disabled. |
| 0x001B0007 | 已成功将报告拆分为一个异步操作。 |
Reporting was successfully spun off as an asynchronous operation. |
| 0x001B0008 | 已处理声明。 |
The assertion was handled. |
| 0x001B0009 | 已处理声明并将其添加到永久忽略列表中。 |
The assertion was handled and added to a permanent ignore list. |
| 0x001B000A | 已将声明作为未处理的声明恢复。 |
The assertion was resumed as unhandled. |
| 0x001B000B | 已限制报告。 |
Report was throttled. |
| 0x001B000C | 已使用 Cab 上载报告。 |
Report was uploaded with cab. |
| 0x001F0001 | 由筛选器完成 IO。 |
The IO was completed by a filter. |
| 0x00261001 | 无法获取监视器描述符。 |
Monitor descriptor could not be obtained. |
| 0x00261002 | 此版本不支持已获取的监视器描述符的格式。 |
Format of the obtained monitor descriptor is not supported by this release. |
| 0x00262307 | 没有任何模式固定在指定 VidPN 源/目标上。 |
No mode is pinned on the specified VidPN source/target. |
| 0x0026231E | 指定的模式集没有为它的一种模式指定首选项。 |
Specified mode set does not specify preference for one of its modes. |
| 0x0026234B | 指定的数据集(例如，模式集、频率范围集、描述符集和拓扑等)为空。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty. |
| 0x0026234C | 指定的数据集(例如，模式集、频率范围集、描述符集和拓扑等)不包含任何其他元素。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements. |
| 0x00262351 | 指定的内容转换没有固定在指定的 VidPN 当前路径上。 |
Specified content transformation is not pinned on the specified VidPN present path. |
| 0x00263005 | {已返回 GDI 重定向表面}已返回顶级窗口的 GDI 重定向表面。 |
{GDI redirection surface was returned}GDI redirection surface of the top level window was returned. |
| 0x00263008 | {GDI 重定向表面在其他适配器上或在系统内存中。请通过 GDI 执行 blt}GDI 重定向表面在其他适配器上或在系统内存中。请通过 GDI 执行 blt。 |
{GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI}GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI. |
| 0x0027000D | 证书存储中已存在证书。 |
A certificate is already present in the cert store. |
| 0x00270258 | 已启动应用商店而不是指定的应用，因为该应用的程序包处于无效状态。 |
The Store was launched instead of the specified app because the app's package was in an invalid state. |
| 0x00270259 | 此应用无法启动，但已使用对话框处理该错误。 |
This app failed to launch, but the error was handled with a dialog. |
| 0x00300100 | 将忽略属性值。 |
Property value will be ignored. |
| 0x00340001 | 该请求稍后将通过 NDIS 状态指示来完成。 |
The request will be completed later by NDIS status indication. |
| 0x00350059 | 设备有已放弃的挂起页面请求。 |
The device had pending page requests which were discarded. |
| 0x003C0105 | 无法在此系统上执行疑难解答程序包。 |
The troubleshooting pack cannot be executed on this system. |
| 0x003D0000 | 正在异步完成函数调用。 |
The function call is completing asynchronously. |
| 0x003D0001 | 通道上没有更多可用的消息。 |
There are no more messages available on the channel. |
| 0x00630001 | 图表数据已创建。 |
The graph data was created. |
| 0x00630002 | 没有更多的事件数据。 |
There is not more event data. |
| 0x00630005 | 没有连接。 |
No connectivity. |
| 0x00630006 | 已经为成员。 |
Already a member. |
| 0x00632000 | 图表已经连接。 |
The graph is already connect. |
| 0x00636000 | 订阅已存在。 |
The subscription already exists. |
| 0x00E70001 | 驱动程序已删除该存储池。应该更新对象缓存。 |
The storage pool was deleted by the driver. The object cache should be updated. |
| 0x087A0001 | 演示操作对用户不可见。 |
The Present operation was invisible to the user. |
| 0x087A0002 | 部分演示操作对用户不可见 |
The Present operation was partially invisible to the user. |
| 0x087A0004 | 驱动程序正在请求 DXGI 运行时不使用共享资源来与桌面窗口管理器通信。 |
The driver is requesting that the DXGI runtime not use shared resources to communicate with the Desktop Window Manager. |
| 0x087A0005 | 演示操作不可见，原因是 Windows 会话已切换到另一个桌面 (例如使用 ctrl-alt-del)。 |
The Present operation was not visible because the Windows session has switched to another desktop (for example, ctrl-alt-del). |
| 0x087A0006 | 演示操作不可见，原因是目标监视器已用于其他用途。 |
The Present operation was not visible because the target monitor was being used for some other purpose. |
| 0x087A0007 | 演示操作不可见，原因是显示模式已更改。DXGI 将重新尝试演示。 |
The Present operation was not visible because the display mode changed. DXGI will have re-attempted the presentation. |
| 0x087A0008 | 演示操作不可见，原因是此时另一个 Direct3D 设备正在尝试采用全屏幕模式。 |
The Present operation was not visible because another Direct3D device was attempting to take fullscreen mode at the time. |
| 0x087A0009 | 交换链已变为不堵塞。 |
The swapchain has become unoccluded. |
| 0x087A000A | 适配器没有所需资源的访问权限来完成 Desktop Duplication Present() 调用，需要再次进行 Present() 调用 |
The adapter did not have access to the required resources to complete the Desktop Duplication Present() call, the Present() call needs to be made again |
| 0x087A002F | “呈现”操作已成功，但调用程序应该在下次执行 V-sync 时再次呈现，即使内容没有任何更改也是如此。 |
The present succeeded but the caller should present again on the next V-sync, even if there are no changes to the content. |
| 0x4026200A | 指定的缓冲区不足以包含整个请求的数据集。填充的部分数据已达到缓冲区的大小。调用方需要根据部分写入缓冲区的内容指定的大小来提供缓冲区(特定于接口)。 |
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). |
| 0x40262201 | 跳过 DMA 缓冲区引用的分配准备。 |
Skip preparation of allocations referenced by the DMA buffer. |
| 0x4026242F | 无法可靠地检测到是否存在子设备。 |
Child device presence was not reliably detected. |
| 0x40262437 | 启动主链接适配器已被暂时延迟。 |
Starting the leadlink adapter has been deferred temporarily. |
| 0x40262439 | 在同一轮询级别上为子级轮询显示适配器过于频繁。 |
The display adapter is being polled for children too frequently at the same polling level. |
| 0x4026243A | 启动适配器的操作已经被暂时延迟。 |
Starting the adapter has been deferred temporarily. |
| 0x4026243C | 我们可以依赖于驱动程序返回的子设备状态。 |
We can depend on the child device presence returned by the driver. |
| 0x80000001 | 尚未实现 |
Not implemented |
| 0x80000002 | 内存已用完 |
Ran out of memory |
| 0x80000003 | 一个或数个参数无效 |
One or more arguments are invalid |
| 0x80000004 | 不支持此接口 |
No such interface supported |
| 0x80000005 | 无效指针 |
Invalid pointer |
| 0x80000006 | 无效句柄 |
Invalid handle |
| 0x80000007 | 已中止操作 |
Operation aborted |
| 0x80000008 | 未指定的错误 |
Unspecified error |
| 0x80000009 | 一般性拒绝访问错误 |
General access denied error |
| 0x8000000A | 完成该操作所需的数据还不可使用。 |
The data necessary to complete this operation is not yet available. |
| 0x8000000B | 该操作尝试访问的数据超出了有效范围 |
The operation attempted to access data outside the valid range |
| 0x8000000C | 并发或交错操作更改了对象的状态，使此操作无效。 |
A concurrent or interleaved operation changed the state of the object, invalidating this operation. |
| 0x8000000D | 请求了非法的状态更改。 |
An illegal state change was requested. |
| 0x8000000E | 在意外的时间调用了方法。 |
A method was called at an unexpected time. |
| 0x8000000F | 元数据文件中找不到类型名称或命名空间。 |
Typename or Namespace was not found in metadata file. |
| 0x80000010 | 名称为现有的命名空间，而不是类型名称。 |
Name is an existing namespace rather than a typename. |
| 0x80000011 | 类型名称的格式无效。 |
Typename has an invalid format. |
| 0x80000012 | 元数据文件无效或损坏。 |
Metadata file is invalid or corrupted. |
| 0x80000013 | 该对象已关闭。 |
The object has been closed. |
| 0x80000014 | 在写入操作期间只有一个线程可以访问对象。 |
Only one thread may access the object during a write operation. |
| 0x80000015 | 在更改通知期间禁止任何操作。 |
Operation is prohibited during change notification. |
| 0x80000016 | 无法找到与此错误代码关联的文本。 |
The text associated with this error code could not be found. |
| 0x80000017 | 非 Null 字符串已终止。 |
String not null terminated. |
| 0x80000018 | 某个委派在分配时未获得许可。 |
A delegate was assigned when not allowed. |
| 0x80000019 | 某个异步操作没有正常启动。 |
An async operation was not properly started. |
| 0x8000001A | 应用程序正在退出，无法为该请求提供服务 |
The application is exiting and cannot service this request |
| 0x8000001B | 应用程序视图正在退出，无法为该请求提供服务 |
The application view is exiting and cannot service this request |
| 0x8000001C | 对象必须支持 IAgileObject 接口 |
The object must support the IAgileObject interface |
| 0x8000001D | 不支持从 MTA 中激活单线程类 |
Activating a single-threaded class from MTA is not supported |
| 0x8000001E | 已提交对象。 |
The object has been committed. |
| 0x8000001F | 对某个 ASTA 的 COM 调用被阻止，因为调用链是在另一个 ASTA 中生成或通过它传递的。此调用模式易于导致死锁，并且单元调用控制不允许使用此调用模式。 |
A 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. |
| 0x80004006 | 线程本地存储故障 |
Thread local storage failure |
| 0x80004007 | 取得共享内存分配器故障 |
Get shared memory allocator failure |
| 0x80004008 | 取得内存分配器故障 |
Get memory allocator failure |
| 0x80004009 | 无法初始化类缓存 |
Unable to initialize class cache |
| 0x8000400A | 无法初始化 RPC 服务 |
Unable to initialize RPC services |
| 0x8000400B | 无法设置线程本地存储通道控制 |
Cannot set thread local storage channel control |
| 0x8000400C | 无法分配线程本地存储通道控制 |
Could not allocate thread local storage channel control |
| 0x8000400D | 无法接受用户提供的内存分配器 |
The user supplied memory allocator is unacceptable |
| 0x8000400E | OLE 服务多用户终端运行程序已存在 |
The OLE service mutex already exists |
| 0x8000400F | OLE 服务文件映射已存在 |
The OLE service file mapping already exists |
| 0x80004010 | 无法映射 OLE 服务的文件视图 |
Unable to map view of file for OLE service |
| 0x80004011 | 未能启动 OLE 服务 |
Failure attempting to launch OLE service |
| 0x80004012 | 运行单一线程时试图再次调用 CoInitialize |
There was an attempt to call CoInitialize a second time while single threaded |
| 0x80004013 | 远程激活是必需的，但不被允许 |
A Remote activation was necessary but was not allowed |
| 0x80004014 | 远程激活是必需的，但所提供的服务器名无效 |
A Remote activation was necessary but the server name provided was invalid |
| 0x80004015 | 此类是作为跟调用程序不同的安全 id 运行的 |
The class is configured to run as a security id different from the caller |
| 0x80004016 | 已停用需要 DDE 窗口的 Ole1 服务使用 |
Use of Ole1 services requiring DDE windows is disabled |
| 0x80004017 | RunAs 的格式必须是\\或只是 |
A RunAs specification must be \\ or simply |
| 0x80004018 | 无法开始服务器进程。路径名称可能不正确。 |
The server process could not be started. The pathname may be incorrect. |
| 0x80004019 | 无法按配置标识启动服务器进程。路径名称可能不正确或不可使用。 |
The server process could not be started as the configured identity. The pathname may be incorrect or unavailable. |
| 0x8000401A | 因为配置标识不正确，系统无法开始服务器进程。请检查用户名和密码。 |
The server process could not be started because the configured identity is incorrect. Check the username and password. |
| 0x8000401B | 客户端没有启动服务器的许可。 |
The client is not allowed to launch this server. |
| 0x8000401C | 不能启动提供这个服务器的服务。 |
The service providing this server could not be started. |
| 0x8000401D | 此计算机无法与提供服务器的计算机进行通信。 |
This computer was unable to communicate with the computer providing the server. |
| 0x8000401E | 服务器启动之后没有响应。 |
The server did not respond after being launched. |
| 0x8000401F | 这台服务器的注册信息不一致或不完全。 |
The registration information for this server is inconsistent or incomplete. |
| 0x80004020 | 这个接口的注册信息不一致或不完全。 |
The registration information for this interface is inconsistent or incomplete. |
| 0x80004021 | 操作不被支持。 |
The operation attempted is not supported. |
| 0x80004022 | 必须加载一个 dll。 |
A dll must be loaded. |
| 0x80004023 | 遇到一个 Microsoft 软件安装程序错误。 |
A Microsoft Software Installer error was encountered. |
| 0x80004024 | 指定的激活不能在指定的客户端上下文中发生。 |
The specified activation could not occur in the client context as specified. |
| 0x80004025 | 已暂停服务器上的激活。 |
Activations on the server are paused. |
| 0x80004026 | 没有暂停服务器上的激活。 |
Activations on the server are not paused. |
| 0x80004027 | 已禁用包含此组件或包含此组件的应用程序。 |
The component or application containing the component has been disabled. |
| 0x80004028 | 公用语言运行时间不可用 |
The common language runtime is not available |
| 0x80004029 | 线程池拒绝了提交的异步工作。 |
The thread-pool rejected the submitted asynchronous work. |
| 0x8000402A | 服务器已经启动，但是没有及时完成初始化。 |
The server started, but did not finish initializing in a timely fashion. |
| 0x8000402B | 因为 IObjectControl.Activate 内部没有 COM+ 安全上下文无法完成调用。 |
Unable to complete the call since there is no COM+ security context inside IObjectControl.Activate. |
| 0x80004030 | 提供的跟踪程序配置无效 |
The provided tracker configuration is invalid |
| 0x80004031 | 提供的线程池配置无效 |
The provided thread pool configuration is invalid |
| 0x80004032 | 提供的并列配置无效 |
The provided side-by-side configuration is invalid |
| 0x80004033 | 在安全协商中获得的服务器主要名(SPN)格式不正确。 |
The server principal name (SPN) obtained during security negotiation is malformed. |
| 0x80004034 | 调用方无法撤消单元关闭前的单个单元注册。 |
The caller failed to revoke a per-apartment registration before apartment shutdown. |
| 0x80004035 | 此对象已被存根管理器断开，因为存在外部客户端。 |
The object has been rundown by the stub manager while there are external clients. |
| 0x8000FFFF | 灾难性故障 |
Catastrophic failure |
| 0x80010001 | 被呼叫方拒绝接收呼叫。 |
Call was rejected by callee. |
| 0x80010002 | 消息筛选器取消了调用。 |
Call was canceled by the message filter. |
| 0x80010003 | 调用方正在调度一个任务间的 SendMessage 调用，因而无法通过 PostMessage 调用。 |
The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage. |
| 0x80010004 | 调用方正在调度一个异步调用，且无法替此调用创建传出调用。 |
The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call. |
| 0x80010005 | 在消息筛选器里时，不可对外调用。 |
It is illegal to call out while inside message filter. |
| 0x80010006 | 这个连接已终止或处于伪状态，因此无法继续使用。其他连接仍然有效。 |
The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid. |
| 0x80010007 | 被呼叫方(服务器[不是服务器应用程序])不可用并已消失。所有连接均无效。呼叫可能已执行。 |
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. |
| 0x80010008 | 呼叫方(客户端)在被呼叫方(服务器)处理呼叫时消失。 |
The caller (client) disappeared while the callee (server) was processing a call. |
| 0x80010009 | 带有经过整理的参数数据的数据包不正确。 |
The data packet with the marshalled parameter data is incorrect. |
| 0x8001000A | 未能正确传输呼叫。消息队列已满，在发送后没有清空。 |
The call was not transmitted properly; the message queue was full and was not emptied after yielding. |
| 0x8001000B | 客户端(呼叫方)无法整理参数数据 - 内存不足，等等。 |
The client (caller) cannot marshall the parameter data - low memory, etc. |
| 0x8001000C | 客户端(呼叫方)无法打乱返回数据 - 内存不足，等等。 |
The client (caller) cannot unmarshall the return data - low memory, etc. |
| 0x8001000D | 服务器(被呼叫方)无法整理返回数据 - 内存不足，等等。 |
The server (callee) cannot marshall the return data - low memory, etc. |
| 0x8001000E | 服务器(被呼叫方)无法打乱参数数据 - 内存不足，等等。 |
The server (callee) cannot unmarshall the parameter data - low memory, etc. |
| 0x8001000F | 接收的数据无效；可能是服务器或客户端数据。 |
Received data is invalid; could be server or client data. |
| 0x80010010 | 某个特定参数无效，无法整理(或打乱)。 |
A particular parameter is invalid and cannot be (un)marshalled. |
| 0x80010011 | DDE 对话中，同一信道上没有第二个传出的呼叫。 |
There is no second outgoing call on same channel in DDE conversation. |
| 0x80010012 | 被呼叫方(服务器 [不是服务器应用程序])不可用并已消失。所有连接均无效。没有执行呼叫。 |
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute. |
| 0x80010101 | 无法分配某些需要的资源(内存、事件...) |
Could not allocate some required resource (memory, events, ...) |
| 0x80010102 | 在单一线程模式下，试图在一个以上线程上进行呼叫。 |
Attempted to make calls on more than one thread in single threaded mode. |
| 0x80010103 | 请求的接口没有在服务器对象上注册。 |
The requested interface is not registered on the server object. |
| 0x80010104 | RPC 无法呼叫服务器，或者无法返回呼叫服务器的结果。 |
RPC could not call the server or could not return the results of calling the server. |
| 0x80010105 | 服务器出现意外情况。 |
The server threw an exception. |
| 0x80010106 | 无法在设置线程模式后对其加以更改。 |
Cannot change thread mode after it is set. |
| 0x80010107 | 服务器上不存在调用的方法。 |
The method called does not exist on the server. |
| 0x80010108 | 被调用的对象已与其客户端断开连接。 |
The object invoked has disconnected from its clients. |
| 0x80010109 | 被调用的对象决定不立即处理这个调用。请稍后重试。 |
The object invoked chose not to process the call now. Try again later. |
| 0x8001010A | 消息筛选器显示应用程序正在使用中。 |
The message filter indicated that the application is busy. |
| 0x8001010B | 消息筛选器拒绝这个调用。 |
The message filter rejected the call. |
| 0x8001010C | 用无效数据调用了一个调用控制接口。 |
A call control interfaces was called with invalid data. |
| 0x8001010D | 因为应用程序正在发送一个输入同步呼叫，所以无法执行传出的呼叫。 |
An outgoing call cannot be made since the application is dispatching an input-synchronous call. |
| 0x8001010E | 应用程序调用一个已为另一线程整理的接口。 |
The application called an interface that was marshalled for a different thread. |
| 0x8001010F | 在当前的线程上尚未调用 CoInitialize。 |
CoInitialize has not been called on the current thread. |
| 0x80010110 | 客户端计算机上的 OLE 版本与服务器上的 OLE 版本不一致。 |
The version of OLE on the client and server machines does not match. |
| 0x80010111 | OLE 接收到一个标头无效的包。 |
OLE received a packet with an invalid header. |
| 0x80010112 | OLE 接收到一个扩展名无效的包。 |
OLE received a packet with an invalid extension. |
| 0x80010113 | 所要求的对象或接口不存在。 |
The requested object or interface does not exist. |
| 0x80010114 | 所要求的对象不存在。 |
The requested object does not exist. |
| 0x80010115 | OLE 已发送请求，正在等待答复。 |
OLE has sent a request and is waiting for a reply. |
| 0x80010116 | OLE 在重试请求之前正在等待答复。 |
OLE is waiting before retrying a request. |
| 0x80010117 | 调用结束后，无法访问调用上下文。 |
Call context cannot be accessed after call completed. |
| 0x80010118 | 不支持模拟不安全调用。 |
Impersonate on unsecure calls is not supported. |
| 0x80010119 | 在整理或打乱任何接口之前，必须初始化安全机制。一旦初始化，不能再作更改。 |
Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized. |
| 0x8001011A | 这台计算机上没有安装安全软件包，或者该用户尚未登录，或者客户端与服务器之间没有兼容的安全软件包。 |
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. |
| 0x8001011C | 在该进程中不允许远程调用。 |
Remote calls are not allowed for this process. |
| 0x8001011D | 排列的接口数据包(OBJREF)的格式无效或未知。 |
The marshaled interface data packet (OBJREF) has an invalid or unknown format. |
| 0x8001011E | 没有与这个调用相关的上下文。这发生在一些自定义整理的调用中和客户端调用中。 |
No context is associated with this call. This happens for some custom marshalled calls and on the client side of the call. |
| 0x80010120 | 没有需要等候的同步对象。 |
There are no synchronize objects to wait on. |
| 0x80010121 | 需要从服务器得到完整的使用者颁发者链 SSL 主要名称。 |
Full subject issuer chain SSL principal name expected from the server. |
| 0x80010122 | 主要名称不是有效的 MSSTD 名称。 |
Principal name is not a valid MSSTD name. |
| 0x80010123 | 无法模拟 DCOM 客户端 |
Unable to impersonate DCOM client |
| 0x80010124 | 无法获取服务器的安全上下文 |
Unable to obtain server's security context |
| 0x80010125 | 无法打开当前线程的访问令牌 |
Unable to open the access token of the current thread |
| 0x80010126 | 无法从访问令牌获取用户信息 |
Unable to obtain user info from an access token |
| 0x80010127 | 调用 IAccessControl::IsAccessPermitted 的客户端不是提供给方法的被信任方 |
The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method |
| 0x80010128 | 无法获得客户端的安全覆盖层 |
Unable to obtain the client's security blanket |
| 0x80010129 | 无法在安全描述符中设置自由选择的 ACL |
Unable to set a discretionary ACL into a security descriptor |
| 0x8001012A | 系统函数 AccessCheck 返回了 false |
The system function, AccessCheck, returned false |
| 0x8001012B | NetAccessDel 或 NetAccessAdd 返回了一个错误代码。 |
Either NetAccessDel or NetAccessAdd returned an error code. |
| 0x8001012C | 用户提供的一个被信任方字符串不符合 \\ 语法，而且不是 \"*\" 字符串 |
One of the trustee strings provided by the user did not conform to the \\ syntax and it was not the \"*\" string |
| 0x8001012D | 该用户提供的一个安全标识符无效 |
One of the security identifiers provided by the user was invalid |
| 0x8001012E | 无法将一个宽字符被信任方字符串转换成一个多字节被信任方字符串 |
Unable to convert a wide character trustee string to a multibyte trustee string |
| 0x8001012F | 不能找到和用户提供的被信任方字符串相对应的安全标识符 |
Unable to find a security identifier that corresponds to a trustee string provided by the user |
| 0x80010130 | 系统函数 LookupAccountSID 失败 |
The system function, LookupAccountSID, failed |
| 0x80010131 | 不能找到和用户提供的安全标识符相对应的被信任方名称 |
Unable to find a trustee name that corresponds to a security identifier provided by the user |
| 0x80010132 | 系统函数 LookupAccountName 失败 |
The system function, LookupAccountName, failed |
| 0x80010133 | 无法设置或重置序列化句柄 |
Unable to set or reset a serialization handle |
| 0x80010134 | 无法获取 Windows 目录 |
Unable to obtain the Windows directory |
| 0x80010135 | 路径太长 |
Path too long |
| 0x80010136 | 无法生成 uuid。 |
Unable to generate a uuid. |
| 0x80010137 | 无法创建文件 |
Unable to create file |
| 0x80010138 | 无法关闭串行化句柄或文件句柄。 |
Unable to close a serialization handle or a file handle. |
| 0x80010139 | ACL 中的 ACE 数目超过系统限制。 |
The number of ACEs in an ACL exceeds the system limit. |
| 0x8001013A | 在流中，不是所有的 DENY_ACCESS ACE 都安排在 GRANT_ACCESS ACE 之前。 |
Not all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream. |
| 0x8001013B | IAccessControl 的这种执行方法不支持流中的 ACL 格式的版本。 |
The version of ACL format in the stream is not supported by this implementation of IAccessControl |
| 0x8001013C | 无法打开服务器进程的访问令牌 |
Unable to open the access token of the server process |
| 0x8001013D | 无法解码用户提供的流中的 ACL |
Unable to decode the ACL in the stream provided by the user |
| 0x8001013F | COM IAccessControl 对象没有初始化 |
The COM IAccessControl object is not initialized |
| 0x80010140 | 停用了“调用取消” |
Call Cancellation is disabled |
| 0x80020001 | 未知接口。 |
Unknown interface. |
| 0x80020003 | 找不到成员。 |
Member not found. |
| 0x80020004 | 找不到参数。 |
Parameter not found. |
| 0x80020005 | 类型不匹配。 |
Type mismatch. |
| 0x80020006 | 未知名称。 |
Unknown name. |
| 0x80020007 | 没有命名的参数。 |
No named arguments. |
| 0x80020008 | 不正确的变量类型。 |
Bad variable type. |
| 0x80020009 | 发生意外。 |
Exception occurred. |
| 0x8002000A | 超出当前范围。 |
Out of present range. |
| 0x8002000C | 未知语言。 |
Unknown language. |
| 0x8002000D | 内存已锁定。 |
Memory is locked. |
| 0x8002000E | 无效的参数数目。 |
Invalid number of parameters. |
| 0x8002000F | 非选择性的参数。 |
Parameter not optional. |
| 0x80020010 | 无效的被呼叫方。 |
Invalid callee. |
| 0x80020011 | 不支持集合。 |
Does not support a collection. |
| 0x80020012 | 除数为零。 |
Division by zero. |
| 0x80020013 | 缓冲区太小 |
Buffer too small |
| 0x80028016 | 缓冲区太小。 |
Buffer too small. |
| 0x80028017 | 记录中没有定义域名。 |
Field name not defined in the record. |
| 0x80028018 | 格式太旧或是类型库无效。 |
Old format or invalid type library. |
| 0x8002801C | 访问 OLE 注册表的错误。 |
Error accessing the OLE registry. |
| 0x8002801D | 库没有注册。 |
Library not registered. |
| 0x80028027 | 绑定到未知类型。 |
Bound to unknown type. |
| 0x80028028 | 没有采纳合格名称。 |
Qualified name disallowed. |
| 0x80028029 | 无效的正向引用，或是引用到未编译的类型。 |
Invalid forward reference, or reference to uncompiled type. |
| 0x8002802C | 不确定的名称。 |
Ambiguous name. |
| 0x8002802D | 库中已有此名称。 |
Name already exists in the library. |
| 0x8002802E | 未知的 LCID。 |
Unknown LCID. |
| 0x8002802F | 在指定的 DLL 中没有定义函数。 |
Function not defined in specified DLL. |
| 0x800288BD | 模块类型不适于这项操作。 |
Wrong module kind for the operation. |
| 0x800288C5 | 大小不能超过 64K。 |
Size may not exceed 64K. |
| 0x800288C6 | 继承性分层中存在重复 ID。 |
Duplicate ID in inheritance hierarchy. |
| 0x800288CF | 标准 OLE hmember 中不正确的继承深度。 |
Incorrect inheritance depth in standard OLE hmember. |
| 0x80028CA1 | 参数数目无效。 |
Invalid number of arguments. |
| 0x80028CA2 | I/O 错误。 |
I/O Error. |
| 0x80028CA3 | 创建唯一的 tmp 文件时出错。 |
Error creating unique tmp file. |
| 0x80029C4A | 加载类型库/DLL 时出错。 |
Error loading type library/DLL. |
| 0x80029C83 | 不一致的属性函数。 |
Inconsistent property functions. |
| 0x80029C84 | 类型/模块之间的循环依赖关系。 |
Circular dependency between types/modules. |
| 0x80030001 | 无法执行请求的操作。 |
Unable to perform requested operation. |
| 0x80030002 | 找不到 %1。 |
%1 could not be found. |
| 0x80030003 | 找不到路径 %1。 |
The path %1 could not be found. |
| 0x80030004 | 资源不足，无法打开另一个文件。 |
There are insufficient resources to open another file. |
| 0x80030006 | 尝试在无效的对象上运行操作。 |
Attempted an operation on an invalid object. |
| 0x80030008 | 可用内存不足，无法完成操作。 |
There is insufficient memory available to complete operation. |
| 0x80030009 | 无效的指针错误。 |
Invalid pointer error. |
| 0x80030012 | 没有其他可返回的项目。 |
There are no more entries to return. |
| 0x80030013 | 磁盘有写入保护。 |
Disk is write-protected. |
| 0x80030019 | 执行搜索操作时出错。 |
An error occurred during a seek operation. |
| 0x8003001D | 执行写入操作时发生磁盘错误。 |
A disk error occurred during a write operation. |
| 0x8003001E | 执行读取操作时发生磁盘错误。 |
A disk error occurred during a read operation. |
| 0x80030020 | 发生共享冲突。 |
A share violation has occurred. |
| 0x80030021 | 发生锁定冲突。 |
A lock violation has occurred. |
| 0x80030050 | %1 已经存在。 |
%1 already exists. |
| 0x80030057 | 无效参数错误。 |
Invalid parameter error. |
| 0x80030070 | 磁盘空间不足，无法完成操作。 |
There is insufficient disk space to complete operation. |
| 0x800300F0 | 将非简单属性写入简单属性集是不合法的。 |
Illegal write of non-simple property to simple property set. |
| 0x800300FA | API 调用退出异常。 |
An API call exited abnormally. |
| 0x800300FB | 文件 %1 不是有效的复合文件。 |
The file %1 is not a valid compound file. |
| 0x800300FC | 名称 %1 无效。 |
The name %1 is not valid. |
| 0x800300FD | 发生了意外错误。 |
An unexpected error occurred. |
| 0x800300FE | 没有执行这个函数。 |
That function is not implemented. |
| 0x800300FF | 无效标志错误。 |
Invalid flag error. |
| 0x80030100 | 试图使用一个已在使用中的对象。 |
Attempted to use an object that is busy. |
| 0x80030101 | 自上次确认之后，存储已经更改。 |
The storage has been changed since the last commit. |
| 0x80030102 | 试图使用一个已不复存在的对象。 |
Attempted to use an object that has ceased to exist. |
| 0x80030103 | 无法保存。 |
Can't save. |
| 0x80030104 | 复合文件 %1 是用版本不兼容的存储产生的。 |
The compound file %1 was produced with an incompatible version of storage. |
| 0x80030105 | 复合文件 %1 是用版本较新的存储产生的。 |
The compound file %1 was produced with a newer version of storage. |
| 0x80030106 | 此项操作需要 share.exe 或类似程序。 |
Share.exe or equivalent is required for operation. |
| 0x80030107 | 非文件基础存储上的无效操作调用。 |
Illegal operation called on non-file based storage. |
| 0x80030108 | 扩展安排对象上的无效操作调用。 |
Illegal operation called on object with extant marshallings. |
| 0x80030109 | docfile 已被损坏。 |
The docfile has been corrupted. |
| 0x80030110 | OLE32.DLL 被加载到错误地址上。 |
OLE32.DLL has been loaded at the wrong address. |
| 0x80030111 | 该复合文件对目前的执行来讲太大 |
The compound file is too large for the current implementation |
| 0x80030112 | 该复合文件不是用 STGM_SIMPLE 标识创建的 |
The compound file was not created with the STGM_SIMPLE flag |
| 0x80030201 | 中止文件下载的操作不正常。该文件不完整。 |
The file download was aborted abnormally. The file is incomplete. |
| 0x80030202 | 已终止文件下载。 |
The file download has been terminated. |
| 0x80030208 | 指定的固件插槽无效。 |
The specified firmware slot is invalid. |
| 0x80030209 | 指定的固件映像无效。 |
The specified firmware image is invalid. |
| 0x8003020A | 存储设备没有响应。 |
The storage device is unresponsive. |
| 0x80030305 | 一般复制保护错误。 |
Generic Copy Protection Error. |
| 0x80030306 | 复制保护错误 - DVD CSS 身份验证失败。 |
Copy Protection Error - DVD CSS Authentication failed. |
| 0x80030307 | 复制保护错误 - 所给的扇区没有有效的 CSS 密钥。 |
Copy Protection Error - The given sector does not have a valid CSS key. |
| 0x80030308 | 复制保护错误 - 没有建立 DVD 会话密钥。 |
Copy Protection Error - DVD session key not established. |
| 0x80030309 | 复制保护错误 - 由于文件已经过加密，读取没有成功。 |
Copy Protection Error - The read failed because the sector is encrypted. |
| 0x8003030A | 复制保护错误 - 当前 DVD 区域跟驱动器的区域设置不对应。 |
Copy Protection Error - The current DVD's region does not correspond to the region setting of the drive. |
| 0x8003030B | 复制保护错误 - 驱动器的区域设置可能是永久的，或者用户重置的次数已用尽。 |
Copy Protection Error - The drive's region setting may be permanent or the number of user resets has been exhausted. |
| 0x80040000 | 无效的 OLEVERB 结构 |
Invalid OLEVERB structure |
| 0x80040001 | 无效的咨询标志 |
Invalid advise flags |
| 0x80040002 | 因为找不到关联数据，无法再枚举 |
Can't enumerate any more, because the associated data is missing |
| 0x80040003 | 这项操作不接受建议 |
This implementation doesn't take advises |
| 0x80040004 | 这个连接 ID 没有连接 |
There is no connection for this connection ID |
| 0x80040005 | 需要运行此对象，以便进行这项操作 |
Need to run the object to perform this operation |
| 0x80040006 | 没有高速缓存可供操作 |
There is no cache to operate on |
| 0x80040007 | 未初始化的对象 |
Uninitialized object |
| 0x80040008 | 链接对象的源类已更改 |
Linked object's source class has changed |
| 0x80040009 | 无法取得对象的标记 |
Not able to get the moniker of the object |
| 0x8004000A | 无法绑定到源 |
Not able to bind to the source |
| 0x8004000B | 对象为静态；不允许此项操作 |
Object is static; operation not allowed |
| 0x8004000C | 用户退出了保存对话框 |
User canceled out of save dialog |
| 0x8004000D | 无效的矩形 |
Invalid rectangle |
| 0x8004000E | 对于初始化的 ole2.dll 而言，compobj.dll 的版本太旧 |
compobj.dll is too old for the ole2.dll initialized |
| 0x8004000F | 无效的窗口句柄 |
Invalid window handle |
| 0x80040010 | 对象不在任何就地活动状态 |
Object is not in any of the inplace active states |
| 0x80040011 | 无法转换对象 |
Not able to convert object |
| 0x80040012 | 因为尚未给予对象存储，所以无法运行操作 |
Not able to perform the operation because object is not given storage yet |
| 0x80040064 | 无效的 FORMATETC 结构 |
Invalid FORMATETC structure |
| 0x80040065 | 无效的 DVTARGETDEVICE 结构 |
Invalid DVTARGETDEVICE structure |
| 0x80040066 | 无效的 STDGMEDIUM 结构 |
Invalid STDGMEDIUM structure |
| 0x80040067 | 无效的 STATDATA 结构 |
Invalid STATDATA structure |
| 0x80040068 | 无效的 lindex |
Invalid lindex |
| 0x80040069 | 无效的 tymed |
Invalid tymed |
| 0x8004006A | 无效的剪贴板格式 |
Invalid clipboard format |
| 0x8004006B | 无效的平面形状 |
Invalid aspect(s) |
| 0x8004006C | DVTARGETDEVICE 结构的 tdSize 参数无效 |
tdSize parameter of the DVTARGETDEVICE structure is invalid |
| 0x8004006D | 对象不支持 IViewObject 接口 |
Object doesn't support IViewObject interface |
| 0x80040100 | 试图吊销一个未注册的拖放目标 |
Trying to revoke a drop target that has not been registered |
| 0x80040101 | 这个窗口已被注册成拖放目标 |
This window has already been registered as a drop target |
| 0x80040103 | 拖动操作已在进行中 |
A drag operation is already in progress |
| 0x80040110 | 类不支持聚合(或类对象为远程对象) |
Class does not support aggregation (or class object is remote) |
| 0x80040111 | ClassFactory 无法供应请求的类 |
ClassFactory cannot supply requested class |
| 0x80040112 | 类未授权使用 |
Class is not licensed for use |
| 0x80040140 | 绘制视图时出错 |
Error drawing view |
| 0x80040150 | 无法从注册表读取项 |
Could not read key from registry |
| 0x80040151 | 无法向注册表写入项 |
Could not write key to registry |
| 0x80040152 | 注册表中找不到这个项 |
Could not find the key in the registry |
| 0x80040153 | 无效的注册表值 |
Invalid value for registry |
| 0x80040154 | 没有注册类 |
Class not registered |
| 0x80040155 | 没有注册接口 |
Interface not registered |
| 0x80040156 | 线程模式项无效 |
Threading model entry is not valid |
| 0x80040157 | 在程序包中注册违反了程序包特定的策略 |
A registration in a package violates package-specific policies |
| 0x80040160 | CATID 不存在 |
CATID does not exist |
| 0x80040161 | 找不到描述 |
Description not found |
| 0x80040164 | Active Directory 中的软件安装数据中没有符合这个标准的软件包。 |
No package in the software installation data in the Active Directory meets this criteria. |
| 0x80040165 | 删除这个项目将中断 Active Directory 中的软件安装数据的参考完整性。 |
Deleting this will break the referential integrity of the software installation data in the Active Directory. |
| 0x80040166 | Active Directory 中的软件安装数据中找不到这种 CLSID。 |
The CLSID was not found in the software installation data in the Active Directory. |
| 0x80040167 | Active Directory 中的软件安装数据已损坏。 |
The software installation data in the Active Directory is corrupt. |
| 0x80040168 | Active Directory 中没有软件安装数据。 |
There is no software installation data in the Active Directory. |
| 0x80040169 | Active Directory 中没有软件安装数据对象。 |
There is no software installation data object in the Active Directory. |
| 0x8004016A | Active Directory 中的软件安装数据对象已存在。 |
The software installation data object in the Active Directory already exists. |
| 0x8004016B | Active Directory 中的软件安装数据路径不正确。 |
The path to the software installation data in the Active Directory is not correct. |
| 0x8004016C | 网络错误中断了操作。 |
A network error interrupted the operation. |
| 0x8004016D | 这个对象的大小将超过了管理员设定的最大值。 |
The size of this object exceeds the maximum size set by the Administrator. |
| 0x8004016E | Active Directory 中的软件安装数据架构与要求的架构不匹配。 |
The schema for the software installation data in the Active Directory does not match the required schema. |
| 0x8004016F | Active Directory 中的软件安装数据中出现一个错误。 |
An error occurred in the software installation data in the Active Directory. |
| 0x80040170 | 没有更新缓存 |
Cache not updated |
| 0x80040180 | OLE 对象没有动词 |
No verbs for OLE object |
| 0x800401A0 | 无法使用撤消功能 |
Undo is not available |
| 0x800401A1 | 工具没有可用空间 |
Space for tools is not available |
| 0x800401C0 | OLESTREAM Get 方法失败 |
OLESTREAM Get method failed |
| 0x800401C1 | OLESTREAM Put 方法失败 |
OLESTREAM Put method failed |
| 0x800401C2 | OLESTREAM 的内容格式不正确 |
Contents of the OLESTREAM not in correct format |
| 0x800401C3 | 将位图转换成 DIB 时，某个 Windows GDI 调用出错 |
There was an error in a Windows GDI call while converting the bitmap to a DIB |
| 0x800401C4 | IStorage 的内容格式不正确 |
Contents of the IStorage not in correct format |
| 0x800401C5 | IStorage 的内容缺少一个标准流 |
Contents of IStorage is missing one of the standard streams |
| 0x800401C6 | 将 DIB 转换成位图时，某个 Windows GDI 调用出错。 |
There was an error in a Windows GDI call while converting the DIB to a bitmap. |
| 0x800401D0 | OpenClipboard 失败 |
OpenClipboard Failed |
| 0x800401D1 | EmptyClipboard 失败 |
EmptyClipboard Failed |
| 0x800401D2 | SetClipboard 失败 |
SetClipboard Failed |
| 0x800401D3 | 剪贴板上的数据无效 |
Data on clipboard is invalid |
| 0x800401D4 | CloseClipboard 失败 |
CloseClipboard Failed |
| 0x800401E0 | 需要手动连接标记 |
Moniker needs to be connected manually |
| 0x800401E1 | 操作已超过期限 |
Operation exceeded deadline |
| 0x800401E2 | 标记必须是常规的 |
Moniker needs to be generic |
| 0x800401E3 | 操作无法使用 |
Operation unavailable |
| 0x800401E4 | 无效的语法 |
Invalid syntax |
| 0x800401E5 | 没有供标记使用的对象 |
No object for moniker |
| 0x800401E6 | 文件的扩展名不正确 |
Bad extension for file |
| 0x800401E7 | 中介操作失败 |
Intermediate operation failed |
| 0x800401E8 | 标记不可绑定 |
Moniker is not bindable |
| 0x800401E9 | 标记并未绑定 |
Moniker is not bound |
| 0x800401EA | 标记无法打开文件 |
Moniker cannot open file |
| 0x800401EB | 需要用户输入才能完成操作 |
User input required for operation to succeed |
| 0x800401EC | 标记类没有逆命题 |
Moniker class has no inverse |
| 0x800401ED | 标记没有引用存储 |
Moniker does not refer to storage |
| 0x800401EE | 没有共同前缀 |
No common prefix |
| 0x800401EF | 无法枚举标记 |
Moniker could not be enumerated |
| 0x800401F0 | 尚未调用 CoInitialize。 |
CoInitialize has not been called. |
| 0x800401F1 | 已调用 CoInitialize。 |
CoInitialize has already been called. |
| 0x800401F2 | 无法判别对象类 |
Class of object cannot be determined |
| 0x800401F3 | 无效的类字符串 |
Invalid class string |
| 0x800401F4 | 无效的接口字符串 |
Invalid interface string |
| 0x800401F5 | 找不到应用程序 |
Application not found |
| 0x800401F6 | 应用程序无法多次运行 |
Application cannot be run more than once |
| 0x800401F7 | 应用程序中有个错误 |
Some error in application program |
| 0x800401F8 | 找不到类的 DLL |
DLL for class not found |
| 0x800401F9 | DLL 中出错 |
Error in the DLL |
| 0x800401FA | 应用程序的 OS 或 OS 版本不正确 |
Wrong OS or OS version for application |
| 0x800401FB | 没有注册对象 |
Object is not registered |
| 0x800401FC | 对象已注册 |
Object is already registered |
| 0x800401FD | 对象没有连接到服务器 |
Object is not connected to server |
| 0x800401FE | 应用程序已启动，但未注册类工厂 |
Application was launched but it didn't register a class factory |
| 0x800401FF | 对象已被释放 |
Object has been released |
| 0x80040201 | 事件无法调用任何订户 |
An event was unable to invoke any of the subscribers |
| 0x80040203 | 评估查询字符串时，出现了一个语法错误 |
A syntax error occurred trying to evaluate a query string |
| 0x80040204 | 在查询字符串中使用了一个无效的作用域名 |
An invalid field name was used in a query string |
| 0x80040205 | 提出了一个意外的意外现象 |
An unexpected exception was raised |
| 0x80040206 | 检测到意外的内部错误 |
An unexpected internal error was detected |
| 0x80040207 | 每用户订阅上的所有者 SID 不存在 |
The owner SID on a per-user subscription doesn't exist |
| 0x80040208 | 用户提供的组件或订户引发了一个意外情况 |
A user-supplied component or subscriber raised an exception |
| 0x80040209 | 接口的方法太多，无法从中启用事件 |
An interface has too many methods to fire events from |
| 0x8004020A | 如果其事件类不存在，则无法储存订阅 |
A subscription cannot be stored unless its event class already exists |
| 0x8004020B | 不是所有请求的对象都能被删除 |
Not all the objects requested could be removed |
| 0x8004020C | 该操作需要 COM+，但尚未安装 |
COM+ is required for this operation, but is not installed |
| 0x8004020D | 无法修改或删除不是 COM+ Admin SDK 所添加的对象 |
Cannot modify or delete an object that was not added using the COM+ Admin SDK |
| 0x8004020E | 无法修改或删除由 COM+ Admin SDK 所添加的对象 |
Cannot modify or delete an object that was added using the COM+ Admin SDK |
| 0x8004020F | 此订阅的事件类所在的分区无效。 |
The event class for this subscription is in an invalid partition |
| 0x80040210 | PerUser 订阅的所有者没有登录到指定的系统。 |
The owner of the PerUser subscription is not logged on to the system specified |
| 0x80040212 | 平板电脑墨迹错误代码。无默认平板电脑 |
TabletPC inking error code. No default tablet |
| 0x80040219 | 平板电脑墨迹错误代码。指定的输入矩形无效 |
TabletPC inking error code. An invalid input rectangle was specified |
| 0x8004021B | 平板电脑墨迹错误代码。指定的属性未知 |
TabletPC inking error code. Unknown property specified |
| 0x80040222 | 平板电脑墨迹错误代码。已删除 Stroke 对象 |
TabletPC inking error code. The stroke object was deleted |
| 0x80040223 | 平板电脑墨迹错误代码。初始化失败 |
TabletPC inking error code. Initialization failure |
| 0x80040232 | 平板电脑墨迹错误代码。未提供操作所需的数据 |
TabletPC inking error code. The data required for the operation was not supplied |
| 0x80040233 | 平板电脑墨迹错误代码。数据包说明无效 |
TabletPC inking error code. Invalid packet description |
| 0x80040235 | 平板电脑墨迹错误代码。未注册手写识别器 |
TabletPC inking error code. There are no handwriting recognizers registered |
| 0x80040236 | 平板电脑墨迹错误代码。用户无权读取识别器信息 |
TabletPC inking error code. User does not have the necessary rights to read recognizer information |
| 0x80040237 | 平板电脑墨迹错误代码。调用 API 的顺序错误 |
TabletPC inking error code. API calls were made in an incorrect order |
| 0x80040238 | 平板电脑墨迹错误代码。队列已满 |
TabletPC inking error code. Queue is full |
| 0x80040239 | 平板电脑墨迹错误代码。多次调用 RtpEnabled |
TabletPC inking error code. RtpEnabled called multiple times |
| 0x8004023A | 平板电脑墨迹错误代码。识别器返回的数据无效 |
TabletPC inking error code. A recognizer returned invalid data |
| 0x80040241 | 平板电脑墨迹错误代码。未找到该属性，或者识别器不支持该属性 |
TabletPC inking error code. The property was not found, or supported by the recognizer |
| 0x80041309 | 找不到触发器。 |
Trigger not found. |
| 0x8004130A | 运行这个任务所需的属性中至少有一个尚未设置。 |
One or more of the properties that are needed to run this task have not been set. |
| 0x8004130B | 没有此任务的实例在运行。 |
There is no running instance of the task. |
| 0x8004130C | 这台计算机没有安装任务计划程序服务。 |
The Task Scheduler Service is not installed on this computer. |
| 0x8004130D | 无法打开任务对象。 |
The task object could not be opened. |
| 0x8004130E | 对象是无效任务对象，或者不是任务对象。 |
The object is either an invalid task object or is not a task object. |
| 0x8004130F | 在任务计划程序安全数据库中找不到指示的任务的帐户信息。 |
No account information could be found in the Task Scheduler security database for the task indicated. |
| 0x80041310 | 无法建立指定的帐户。 |
Unable to establish existence of the account specified. |
| 0x80041311 | 任务计划程序安全数据库已损坏；已重置数据库。 |
Corruption was detected in the Task Scheduler security database; the database has been reset. |
| 0x80041312 | 只能在 Windows NT 上使用任务计划程序安全服务。 |
Task Scheduler security services are available only on Windows NT. |
| 0x80041313 | 任务对象版本不受支持或无效。 |
The task object version is either unsupported or invalid. |
| 0x80041314 | 任务是用不受支持的帐户设置和运行时间选项的组合配置的。 |
The task has been configured with an unsupported combination of account settings and run time options. |
| 0x80041315 | 任务计划程序服务没有运行。 |
The Task Scheduler Service is not running. |
| 0x80041316 | 任务 XML 包含意外节点。 |
The task XML contains an unexpected node. |
| 0x80041317 | 任务 XML 包含来自意外命名空间的元素或属性。 |
The task XML contains an element or attribute from an unexpected namespace. |
| 0x80041318 | 任务 XML 包含格式不正确或超出范围的值。 |
The task XML contains a value which is incorrectly formatted or out of range. |
| 0x80041319 | 任务 XML 缺少个所需元素或属性。 |
The task XML is missing a required element or attribute. |
| 0x8004131A | 任务 XML 格式错误。 |
The task XML is malformed. |
| 0x8004131D | 任务 XML 包含过多同一类型的节点。 |
The task XML contains too many nodes of the same type. |
| 0x8004131E | 无法在触发器结束之后启动该任务。 |
The task cannot be started after the trigger's end boundary. |
| 0x8004131F | 这个任务的一个实例已经运行。 |
An instance of this task is already running. |
| 0x80041320 | 由于用户未登录，因此将不会运行该任务。 |
The task will not run because the user is not logged on. |
| 0x80041321 | 该任务映像已损坏或已篡改。 |
The task image is corrupt or has been tampered with. |
| 0x80041322 | 任务计划程序服务不可用。 |
The Task Scheduler service is not available. |
| 0x80041323 | 该任务计划程序服务太忙，无法处理你的请求。请稍后再试。 |
The Task Scheduler service is too busy to handle your request. Please try again later. |
| 0x80041324 | 任务计划程序服务试图运行该任务，但由于任务定义中的限制之一，该任务未运行。 |
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. |
| 0x80041326 | 任务被禁用。 |
The task is disabled. |
| 0x80041327 | 该任务的某些属性与以前版本的 Windows 不兼容。 |
The task has properties that are not compatible with previous versions of Windows. |
| 0x80041328 | 由于任务设置，无法根据需要启动该任务。 |
The task settings do not allow the task to start on demand. |
| 0x80041329 | 任务正在使用的属性组合与计划引擎不兼容。 |
The combination of properties that task is using is not compatible with the scheduling engine. |
| 0x80041330 | 此任务定义使用的功能已弃用。 |
The task definition uses a deprecated feature. |
| 0x8004D000 | 已将另一单一阶段资源管理器列入此事务处理。 |
Another single phase resource manager has already been enlisted in this transaction. |
| 0x8004D001 | 不支持保留的确认或中止 |
A retaining commit or abort is not supported |
| 0x8004D002 | 未知原因导致确认事务处理失败。已中止事务处理。 |
The transaction failed to commit for an unknown reason. The transaction was aborted. |
| 0x8004D003 | 由于调用应用程序不会启动此事务处理，无法在此事务处理对象上调用确认。 |
Cannot call commit on this transaction object because the calling application did not initiate the transaction. |
| 0x8004D004 | 没有确认，此资源试探性地中止了。 |
Instead of committing, the resource heuristically aborted. |
| 0x8004D005 | 没有中止，此资源试探性地确认了。 |
Instead of aborting, the resource heuristically committed. |
| 0x8004D006 | 有些资源状态被确认了，其他的被中止了，似乎是试探性的决定。 |
Some of the states of the resource were committed while others were aborted, likely because of heuristic decisions. |
| 0x8004D007 | 有些资源状态可能被确认了，其他的可能被中止了，似乎是试探性的决定。 |
Some of the states of the resource may have been committed while others may have been aborted, likely because of heuristic decisions. |
| 0x8004D008 | 该申请的孤立层无效或不受支持。 |
The requested isolation level is not valid or supported. |
| 0x8004D009 | 事务管理器不支持这个方法的异步操作。 |
The transaction manager doesn't support an asynchronous operation for this method. |
| 0x8004D00A | 无法在事务中登记。 |
Unable to enlist in the transaction. |
| 0x8004D00B | 此事务执行不能支持申请的保留确认面上的孤立保留语义和中止界限，或者 isoFlags 不等于零。 |
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. |
| 0x8004D00C | 当前没有资源与这个登记有关联 |
There is no resource presently associated with this enlistment |
| 0x8004D00D | 由于至少一个资源管理器里的乐观并发控制失败，该事务没有确认。 |
The transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers. |
| 0x8004D00E | 此事务已明地或暗地被确认或中止 |
The transaction has already been implicitly or explicitly committed or aborted |
| 0x8004D00F | 指定了无效的标记组合 |
An invalid combination of flags was specified |
| 0x8004D010 | 该资源管理器 ID 与此事务或事务管理器无关。 |
The resource manager id is not associated with this transaction or the transaction manager. |
| 0x8004D011 | 在错误的状态里调用此方法 |
This method was called in the wrong state |
| 0x8004D012 | 指定的工作单位跟资源管理器所预期的工作单位不匹配。 |
The indicated unit of work does not match the unit of work expected by the resource manager. |
| 0x8004D013 | 事务中的登记已经存在。 |
An enlistment in a transaction already exists. |
| 0x8004D014 | 找不到此事务的导入对象。 |
An import object for the transaction could not be found. |
| 0x8004D015 | 此事务 cookie 无效。 |
The transaction cookie is invalid. |
| 0x8004D016 | 此事务状态有疑问。发生通信失败，或这是事务管理器或资源管理器失败 |
The transaction status is in doubt. A communication failure occurred, or a transaction manager or resource manager has failed |
| 0x8004D017 | 指定了一个超时时间，但它不被支持。 |
A time-out was specified, but time-outs are not supported. |
| 0x8004D018 | 申请的操作已在进行事务处理。 |
The requested operation is already in progress for the transaction. |
| 0x8004D019 | 事务已被中止。 |
The transaction has already been aborted. |
| 0x8004D01A | 事务管理器返回一日志的错误。 |
The Transaction Manager returned a log full error. |
| 0x8004D01B | 事务管理器不可用。 |
The Transaction Manager is not available. |
| 0x8004D01C | 失去了与事务管理器的连接。 |
A connection with the transaction manager was lost. |
| 0x8004D01D | 拒绝了与事务管理器建立连接的申请。 |
A request to establish a connection with the transaction manager was denied. |
| 0x8004D01E | 资源管理器列入以决定事务状态超时。 |
Resource manager reenlistment to determine transaction status timed out. |
| 0x8004D01F | 该事务管理器未能与另一 TIP 事务管理器建立连接。 |
This transaction manager failed to establish a connection with another TIP transaction manager. |
| 0x8004D020 | 该事务管理器与另一 TIP 事务管理器遇到一个协议错误。 |
This transaction manager encountered a protocol error with another TIP transaction manager. |
| 0x8004D021 | 该事务管理器无法传播来自另一 TIP 事务管理器的事务。 |
This transaction manager could not propagate a transaction from another TIP transaction manager. |
| 0x8004D022 | 目标计算机上的事务管理器不可用。 |
The Transaction Manager on the destination machine is not available. |
| 0x8004D023 | 该事务管理器已经禁止了它对 TIP 的支持。 |
The Transaction Manager has disabled its support for TIP. |
| 0x8004D024 | 该事务管理器已经禁止了它对远程/网络事务的支持。 |
The transaction manager has disabled its support for remote/network transactions. |
| 0x8004D025 | 该伙伴事务管理器已经禁止了它对远程/网络事务的支持。 |
The partner transaction manager has disabled its support for remote/network transactions. |
| 0x8004D026 | 该事务管理器已经禁止了它对 XA 事务的支持。 |
The transaction manager has disabled its support for XA transactions. |
| 0x8004D027 | MSDTC 无法读取配置信息。 |
MSDTC was unable to read its configuration information. |
| 0x8004D028 | MSDTC 无法加载 dtc proxy dll。 |
MSDTC was unable to load the dtc proxy dll. |
| 0x8004D029 | 本地事务已经中止。 |
The local transaction has aborted. |
| 0x8004D02A | 由于通信问题，MSDTC 事务管理器无法将事务推送至目标事务管理器。可能原因如下: 存在防火墙并且没有 MSDTC 进程的例外、两台计算机根据其 NetBIOS 名称无法找到彼此，或未对于两个事务管理器之一启用网络事务支持。 |
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. |
| 0x8004D02B | 由于通信问题，MSDTC 事务管理器无法从源事务管理器提取事务。可能原因如下: 存在防火墙并且没有 MSDTC 进程的例外、两台计算机根据其 NetBIOS 名称无法找到彼此，或未对于两个事务管理器之一启用网络事务支持。 |
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. |
| 0x8004D02C | MSDTC 事务管理器已禁用了它对 SNA LU 6.2 事务的支持。 |
The MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions. |
| 0x8004D080 | XACT_E_CLERKNOTFOUND |
XACT_E_CLERKNOTFOUND |
| 0x8004D081 | XACT_E_CLERKEXISTS |
XACT_E_CLERKEXISTS |
| 0x8004D082 | XACT_E_RECOVERYINPROGRESS |
XACT_E_RECOVERYINPROGRESS |
| 0x8004D083 | XACT_E_TRANSACTIONCLOSED |
XACT_E_TRANSACTIONCLOSED |
| 0x8004D084 | XACT_E_INVALIDLSN |
XACT_E_INVALIDLSN |
| 0x8004D085 | XACT_E_REPLAYREQUEST |
XACT_E_REPLAYREQUEST |
| 0x8004D100 | 连接到指定事务协调器的请求被拒绝。 |
The request to connect to the specified transaction coordinator was denied. |
| 0x8004D101 | 已达到指定事务的最大登记数目。 |
The maximum number of enlistments for the specified transaction has been reached. |
| 0x8004D102 | 具有相同标识符的资源管理器已使用指定事务协调器进行注册。 |
A resource manager with the same identifier is already registered with the specified transaction coordinator. |
| 0x8004D103 | 给定的准备请求不能进行单相优化。 |
The prepare request given was not eligible for single phase optimizations. |
| 0x8004D104 | 已为给定的资源管理器调用 RecoveryComplete。 |
RecoveryComplete has already been called for the given resource manager. |
| 0x8004D105 | 当前协议状态的接口调用不正确。 |
The interface call made was incorrect for the current state of the protocol. |
| 0x8004D106 | XA 资源的 xa_open 调用失败。 |
xa_open call failed for the XA resource. |
| 0x8004D107 | XA 资源的 xa_recover 调用失败。 |
xa_recover call failed for the XA resource. |
| 0x8004D108 | 无法找到指定的逻辑工作单元。 |
The Logical Unit of Work specified cannot be found. |
| 0x8004D109 | 指定的逻辑工作单元已存在。 |
The specified Logical Unit of Work already exists. |
| 0x8004D10A | 从属创建失败。未连接指定的逻辑工作单元。 |
Subordinate creation failed. The specified Logical Unit of Work was not connected. |
| 0x8004D10B | 具有给定标识符的事务已存在。 |
A transaction with the given identifier already exists. |
| 0x8004D10C | 资源使用中。 |
The resource is in use. |
| 0x8004D10D | LU 恢复过程停止。 |
The LU Recovery process is down. |
| 0x8004D10E | 远程会话丢失。 |
The remote session was lost. |
| 0x8004D10F | 当前正在恢复资源。 |
The resource is currently recovering. |
| 0x8004D110 | 驱动恢复时存在不匹配。 |
There was a mismatch in driving recovery. |
| 0x8004D111 | XA 资源发生错误。 |
An error occurred with the XA resource. |
| 0x8004E002 | 根事务要确认，但事务中止了操作 |
The root transaction wanted to commit, but transaction aborted |
| 0x8004E003 | 对 COM+ 组件进行了方法调用，但该组件有一个已被中止的或正在被中止的事务。 |
You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting. |
| 0x8004E004 | 没有 MTS 对象上下文 |
There is no MTS object context |
| 0x8004E005 | 此组件配置为使用同步而且此方法调用将导致发生死锁。 |
The component is configured to use synchronization and this method call would cause a deadlock to occur. |
| 0x8004E006 | 该组件是被配置来使用同步的，并且线程超出了等待进入上下文的时间。 |
The component is configured to use synchronization and a thread has timed out waiting to enter the context. |
| 0x8004E007 | 对 COM+ 组件进行了方法调用，但该组件有一个已被确认或中止的事务。 |
You made a method call on a COM+ component that has a transaction that has already committed or aborted. |
| 0x8004E00C | 指定的角色不是为应用程序所配置的 |
The specified role was not configured for the application |
| 0x8004E00F | COM+ 无法与 Microsoft 分布式事务协调程序交谈 |
COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator |
| 0x8004E021 | 在 COM+ 激活过程中，出现了一个意外错误。 |
An unexpected error occurred during COM+ Activation. |
| 0x8004E022 | COM+ 激活没有成功。有关详细信息，请检查事件日志 |
COM+ Activation failed. Check the event log for more information |
| 0x8004E023 | 由于目录或配置错误，COM+ 激活没有成功。 |
COM+ Activation failed due to a catalog or configuration error. |
| 0x8004E024 | 由于激活没有在指定的时间内完成，COM+ 激活没有成功。 |
COM+ activation failed because the activation could not be completed in the specified amount of time. |
| 0x8004E025 | 由于初始化功能失败，COM+ 激活没有成功。有关详细信息，请检查事件日志。 |
COM+ Activation failed because an initialization function failed. Check the event log for more information. |
| 0x8004E026 | 请求的操作要求 JIT 在当前上下文中，但 JIT 不在其中 |
The requested operation requires that JIT be in the current context and it is not |
| 0x8004E027 | 请求的操作要求当前上下文有一个事务，但当前上下文没有 |
The requested operation requires that the current context have a Transaction, and it does not |
| 0x8004E028 | 安装到 COM+ 应用程序中后，组件线程模式已经更改。请重新安装组件。 |
The components threading model has changed after install into a COM+ Application. Please re-install component. |
| 0x8004E029 | IIS 内部不可用。启动同 IIS 的工作。 |
IIS intrinsics not available. Start your work with IIS. |
| 0x8004E02A | 读写 cookie 失败。 |
An attempt to write a cookie failed. |
| 0x8004E02B | 使用数据库时产生数据库特定错误。 |
An attempt to use a database generated a database specific error. |
| 0x8004E02C | 创建的 COM+ 组件必须使用对象池才能工作。 |
The COM+ component you created must use object pooling to work. |
| 0x8004E02D | 创建的 COM+ 组件必须使用对象构造才能正常工作。 |
The COM+ component you created must use object construction to work correctly. |
| 0x8004E02E | COM+ 组件要求同步，但没有这样配置。 |
The COM+ component requires synchronization, and it is not configured for it. |
| 0x8004E02F | 在创建的 COM+ 组件的 TxIsolation 层次属性比事务根组件的 TxIsolationLevel 更强。创建失败。 |
The TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the \"root\" component for the transaction. The creation failed. |
| 0x8004E030 | 组件试图在 EnterTransactionScope 调用和 ExitTransactionScope 调用之间执行交叉上下文调用。这是不允许的操作。在事务作用域内部无法执行交叉上下文调用。 |
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. |
| 0x8004E031 | 组件已调用 EnterTransactionScope，但是在返回前没有对 ExitTransactionScope 执行相应的调用。 |
The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning. |
| 0x80072EE1 | 无法分配更多的 Internet 句柄 |
No more Internet handles can be allocated |
| 0x80072EE2 | 操作超时 |
The operation timed out |
| 0x80072EE3 | 服务器返回已扩展的信息 |
The server returned extended information |
| 0x80072EE4 | Microsoft Internet 扩展中发生内部错误 |
An internal error occurred in the Microsoft Internet extensions |
| 0x80072EE5 | URL 无效 |
The URL is invalid |
| 0x80072EE6 | URL 未使用可识别的协议 |
The URL does not use a recognized protocol |
| 0x80072EE7 | 无法解析服务器的名称或地址 |
The server name or address could not be resolved |
| 0x80072EE8 | 找不到具有所需功能的协议 |
A protocol with the required capabilities was not found |
| 0x80072EE9 | 选项无效 |
The option is invalid |
| 0x80072EEA | 选项类型的长度不正确 |
The length is incorrect for the option type |
| 0x80072EEB | 无法设置选项值 |
The option value cannot be set |
| 0x80072EEC | 已关闭 Microsoft Internet 扩展支持 |
Microsoft Internet Extension support has been shut down |
| 0x80072EED | 用户名无效 |
The user name was not allowed |
| 0x80072EEE | 密码无效 |
The password was not allowed |
| 0x80072EEF | 已拒绝登录申请 |
The login request was denied |
| 0x80072EF0 | 请求的操作无效 |
The requested operation is invalid |
| 0x80072EF1 | 已取消操作 |
The operation has been canceled |
| 0x80072EF2 | 为申请的操作提供的句柄存在类型错误 |
The supplied handle is the wrong type for the requested operation |
| 0x80072EF3 | 所请求操作的句柄存在状态错误 |
The handle is in the wrong state for the requested operation |
| 0x80072EF4 | 无法在代理会话上提出请求 |
The request cannot be made on a Proxy session |
| 0x80072EF5 | 找不到注册表值 |
The registry value could not be found |
| 0x80072EF6 | 注册表参数不正确 |
The registry parameter is incorrect |
| 0x80072EF7 | 无法直接访问 Internet |
Direct Internet access is not available |
| 0x80072EF8 | 未提供上下文值 |
No context value was supplied |
| 0x80072EF9 | 未提供状态的回拨 |
No status callback was supplied |
| 0x80072EFA | 还有一些请求未处理 |
There are outstanding requests |
| 0x80072EFB | 该信息格式不正确 |
The information format is incorrect |
| 0x80072EFC | 找不到请求的项目 |
The requested item could not be found |
| 0x80072EFD | 无法与服务器建立连接 |
A connection with the server could not be established |
| 0x80072EFE | 与服务器的连接意外终止 |
The connection with the server was terminated abnormally |
| 0x80072EFF | 与服务器的连接被重置 |
The connection with the server was reset |
| 0x80072F00 | 必须重试该操作 |
The action must be retried |
| 0x80072F01 | 代理请求无效 |
The proxy request is invalid |
| 0x80072F02 | 完成该操作需要用户交互 |
User interaction is required to complete the operation |
| 0x80072F04 | 该句柄已存在 |
The handle already exists |
| 0x80072F05 | 证书中的日期无效或已过期 |
The date in the certificate is invalid or has expired |
| 0x80072F06 | 证书中的主机名无效或不匹配 |
The host name in the certificate is invalid or does not match |
| 0x80072F07 | 重定向请求会将不安全连接更改为安全连接 |
A redirect request will change a non-secure to a secure connection |
| 0x80072F08 | 重定向请求会将安全连接更改为不安全连接 |
A redirect request will change a secure to a non-secure connection |
| 0x80072F09 | 安全连接和不安全连接的混合 |
Mixed secure and non-secure connections |
| 0x80072F0A | 更改为不安全投递 |
Changing to non-secure post |
| 0x80072F0B | 数据正在通过不安全连接投递 |
Data is being posted on a non-secure connection |
| 0x80072F0C | 需要提供证书才能完成客户端身份验证 |
A certificate is required to complete client authentication |
| 0x80072F0D | 证书颁发机构无效或不正确 |
The certificate authority is invalid or incorrect |
| 0x80072F0E | 未正确安装客户端身份验证 |
Client authentication has not been correctly installed |
| 0x80072F0F | Wininet 异步线程中发生错误。你可能需要重新启动 |
An error has occurred in a Wininet asynchronous thread. You may need to restart |
| 0x80072F10 | 协议纲要在重定向操作中已发生更改 |
The protocol scheme has changed during a redirect operaiton |
| 0x80072F11 | 存在等待重试的操作 |
There are operations awaiting retry |
| 0x80072F13 | 没有新的缓存容器 |
There are no new cache containers |
| 0x80072F14 | 安全区域检查表明必须重试该操作 |
A security zone check indicates the operation must be retried |
| 0x80072F17 | SSL 证书包含错误。 |
The SSL certificate contains errors. |
| 0x80072F19 | 无法连接到吊销服务器，或者未能获得最终响应。 |
It was not possible to connect to the revocation server or a definitive response could not be obtained. |
| 0x80072F76 | 找不到请求的标头 |
The requested header was not found |
| 0x80072F77 | 服务器不支持请求的协议级别 |
The server does not support the requested protocol level |
| 0x80072F78 | 服务器返回无效或未识别的响应 |
The server returned an invalid or unrecognized response |
| 0x80072F79 | 提供的 HTTP 标头无效 |
The supplied HTTP header is invalid |
| 0x80072F7A | HTTP 标头请求无效 |
The request for a HTTP header is invalid |
| 0x80072F7B | HTTP 标头已经存在 |
The HTTP header already exists |
| 0x80072F7C | HTTP 重定向请求失败 |
The HTTP redirect request failed |
| 0x80072F7D | 安全通道支持出错 |
An error occurred in the secure channel support |
| 0x80072F7E | 无法将文件写入缓存 |
The file could not be written to the cache |
| 0x80072F7F | 未正确安装 TCP/IP 协议 |
The TCP/IP protocol is not installed properly |
| 0x80072F80 | 未重定向 HTTP 请求 |
The HTTP request was not redirected |
| 0x80072F81 | 来自服务器的一个 Cookie 必须由用户确认 |
A cookie from the server must be confirmed by the user |
| 0x80072F82 | 来自服务器的一个 Cookie 已被拒绝 |
A cookie from the server has been declined acceptance |
| 0x80072F83 | 计算机网络连接已断开 |
The computer is disconnected from the network |
| 0x80072F84 | 服务器无法访问 |
The server is unreachable |
| 0x80072F85 | 代理服务器无法访问 |
The proxy server is unreachable |
| 0x80072F86 | 代理服务器自动配置脚本出错 |
The proxy auto-configuration script is in error |
| 0x80072F87 | 无法下载代理服务器自动配置脚本文件 |
Could not download the proxy auto-configuration script file |
| 0x80072F88 | HTTP 重定向请求必须由用户确认 |
The HTTP redirect request must be confirmed by the user |
| 0x80072F89 | 提供的证书无效 |
The supplied certificate is invalid |
| 0x80072F8A | 提供的证书已被吊销 |
The supplied certificate has been revoked |
| 0x80072F8B | 由于已启用文件共享功能，因此拨号功能无效。如果需要进行安全检查，便会请求使拨号功能无效。 |
The Dialup failed because file sharing was turned on and a failure was requested if security check was needed |
| 0x80072F8C | 尚未初始化 WinINet API |
Initialization of the WinINet API has not occurred |
| 0x80072F8E | 登录失败，客户端应向用户显示实体正文 |
Login failed and the client should display the entity body to the user |
| 0x80072F8F | 内容解码失败 |
Content decoding has failed |
| 0x80080001 | 未能创建类对象 |
Attempt to create a class object failed |
| 0x80080002 | OLE 服务无法绑定对象 |
OLE service could not bind object |
| 0x80080003 | RPC 与 OLE 服务通信失败 |
RPC communication failed with OLE service |
| 0x80080004 | 错误的对象路径 |
Bad path to object |
| 0x80080005 | 服务器运行失败 |
Server execution failed |
| 0x80080006 | OLE 服务无法与对象服务器通信 |
OLE service could not communicate with the object server |
| 0x80080007 | 标记路径无法正常化 |
Moniker path could not be normalized |
| 0x80080008 | 当 OLE 服务与对象服务器通讯时，后者已经停止 |
Object server is stopping when OLE service contacts it |
| 0x80080009 | 指定了无效的根块指针 |
An invalid root block pointer was specified |
| 0x80080010 | 分配链含有无效的链接指针 |
An allocation chain contained an invalid link pointer |
| 0x80080011 | 请求的分配值太大 |
The requested allocation size was too large |
| 0x80080015 | 激活要求在 CLSID 密钥下面有显示名称。 |
The activation requires a display name to be present under the CLSID key. |
| 0x80080016 | 激活要求应用程序的 RunAs 值为 Activate As Activator。 |
The activation requires that the RunAs value for the application is Activate As Activator. |
| 0x80080017 | 未将类配置为支持提升的激活。 |
The class is not configured to support Elevated activation. |
| 0x80080200 | Appx 包 API 遇到内部错误。 |
Appx packaging API has encountered an internal error. |
| 0x80080201 | 该文件不是有效的 Appx 包，原因是其内容是交错的。 |
The file is not a valid Appx package because its contents are interleaved. |
| 0x80080202 | 该文件不是有效的 Appx 包，原因是它包含 OPC 关系。 |
The file is not a valid Appx package because it contains OPC relationships. |
| 0x80080203 | 该文件不是有效的 Appx 程序包，原因是它缺少清单或块映射，或在存在代码完整性文件时缺少签名文件。 |
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. |
| 0x80080204 | Appx 包的清单无效。 |
The Appx package's manifest is invalid. |
| 0x80080205 | Appx 包的块映射无效。 |
The Appx package's block map is invalid. |
| 0x80080206 | 无法读取 Appx 包的内容，原因是它已损坏。 |
The Appx package's content cannot be read because it is corrupt. |
| 0x80080207 | 计算所得的块哈希值与块映射中存储的哈希值不相符。 |
The computed hash value of the block does not match the one stored in the block map. |
| 0x80080208 | 请求的字节范围转换为块的字节范围时超过 4GB。 |
The requested byte range is over 4GB when translated to byte range of blocks. |
| 0x80080209 | 用于对程序包签名的 SIP_SUBJECTINFO 结构不包含所需的数据。 |
The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data. |
| 0x8008020A | 用于加密或解密程序包的 APPX_KEY_INFO 结构包含无效数据。 |
The APPX_KEY_INFO structure used to encrypt or decrypt the package contains invalid data. |
| 0x8008020B | Appx 程序包的内容组映射无效。 |
The Appx package's content group map is invalid. |
| 0x80080300 | 后台任务未真正激活。 |
The background task activation is spurious. |
| 0x80090001 | 不正确的 UID。 |
Bad UID. |
| 0x80090002 | 不正确的哈希算法。 |
Bad Hash. |
| 0x80090003 | 不正确的项。 |
Bad Key. |
| 0x80090004 | 不正确的长度。 |
Bad Length. |
| 0x80090005 | 不正确的数据。 |
Bad Data. |
| 0x80090006 | 无效签名。 |
Invalid Signature. |
| 0x80090007 | 不正确的提供程序版本。 |
Bad Version of provider. |
| 0x80090008 | 指定的算法无效。 |
Invalid algorithm specified. |
| 0x80090009 | 指定的标记无效。 |
Invalid flags specified. |
| 0x8009000A | 指定的类型无效。 |
Invalid type specified. |
| 0x8009000B | 该项不适于在指定状态下使用。 |
Key not valid for use in specified state. |
| 0x8009000C | 哈希不适于在指定状态下使用。 |
Hash not valid for use in specified state. |
| 0x8009000D | 该项不存在。 |
Key does not exist. |
| 0x8009000E | 内存不足，无法操作。 |
Insufficient memory available for the operation. |
| 0x80090011 | 找不到对象。 |
Object was not found. |
| 0x80090012 | 数据已被加密。 |
Data already encrypted. |
| 0x80090013 | 指定了无效的提供程序。 |
Invalid provider specified. |
| 0x80090014 | 指定了无效的提供程序类型。 |
Invalid provider type specified. |
| 0x80090015 | 提供程序公钥无效。 |
Provider's public key is invalid. |
| 0x80090016 | 密钥集不存在。 |
Keyset does not exist |
| 0x80090017 | 提供程序类型未被定义。 |
Provider type not defined. |
| 0x80090018 | 所注册的提供程序类型是无效的。 |
Provider type as registered is invalid. |
| 0x80090019 | 该密钥集未被定义。 |
The keyset is not defined. |
| 0x8009001A | 所注册的密钥集无效。 |
Keyset as registered is invalid. |
| 0x8009001B | 提供程序的类型与注册的值不相配。 |
Provider type does not match registered value. |
| 0x8009001C | 数字签名文件已损坏。 |
The digital signature file is corrupt. |
| 0x8009001D | 提供程序 DLL 未能正确初始化。 |
Provider DLL failed to initialize correctly. |
| 0x8009001E | 无法找到提供程序 DLL。 |
Provider DLL could not be found. |
| 0x8009001F | 无效的密钥集参数。 |
The Keyset parameter is invalid. |
| 0x80090021 | 发生了基本错误。 |
A base error occurred. |
| 0x80090022 | 因为获取的上下文是无声的，提供程序不能执行操作。 |
Provider could not perform the action since the context was acquired as silent. |
| 0x80090023 | 安全标志没有存储空间给一个额外的容器。 |
The security token does not have storage space available for an additional container. |
| 0x80090024 | 用户的配置文件是临时配置文件。 |
The profile for the user is a temporary profile. |
| 0x80090025 | 由于 CSP 使用固定参数，无法设置密钥参数。 |
The key parameters could not be set because the CSP uses fixed parameters. |
| 0x80090026 | 提供的句柄无效。 |
The supplied handle is invalid. |
| 0x80090028 | 为函数提供的缓冲区过小。 |
The buffer supplied to a function was too small. |
| 0x8009002B | 提供的缓冲区重叠不正确。 |
The supplied buffers overlap incorrectly. |
| 0x8009002C | 无法解密指定的数据。 |
The specified data could not be decrypted. |
| 0x8009002D | 内部一致性检查失败。 |
An internal consistency check failed. |
| 0x8009002E | 这个操作要求用户输入。 |
This operation requires input from the user. |
| 0x8009002F | 加密提供程序不支持 HMAC。 |
The cryptographic provider does not support HMAC. |
| 0x80090030 | 此加密提供程序所需的设备尚未准备就绪。 |
The device that is required by this cryptographic provider is not ready for use. |
| 0x80090031 | 已触发字典式攻击缓解操作，并且提供程序忽略了提供的授权。 |
The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider. |
| 0x80090032 | 对提供的数据进行验证使完整性或签名验证失败。 |
The validation of the provided data failed the integrity or signature validation. |
| 0x80090033 | 密码不正确。 |
Incorrect password. |
| 0x80090034 | 加密失败。 |
Encryption failed. |
| 0x80090035 | 在该平台上找不到此加密提供程序所需的设备 |
The device that is required by this cryptographic provider is not found on this platform. |
| 0x80090036 | 用户取消了操作。 |
The action was cancelled by the user. |
| 0x80090037 | 密码不再有效，必须更改。 |
The password is no longer valid and must be changed. |
| 0x80090038 | 无法通过终端服务器客户端会话完成该操作。 |
The operation cannot be completed from Terminal Server client sessions. |
| 0x80090300 | 内存不足，无法完成请求 |
Not enough memory is available to complete this request |
| 0x80090301 | 指定的句柄无效 |
The handle specified is invalid |
| 0x80090302 | 要求的函数不受支持 |
The function requested is not supported |
| 0x80090303 | 指定的目标未知或无法达到 |
The specified target is unknown or unreachable |
| 0x80090304 | 无法连接到本地安全机构 |
The Local Security Authority cannot be contacted |
| 0x80090305 | 要求的安全包不存在 |
The requested security package does not exist |
| 0x80090306 | 呼叫方不是所要求凭证的所有者 |
The caller is not the owner of the desired credentials |
| 0x80090307 | 安全包未能初始化，不能安装 |
The security package failed to initialize, and cannot be installed |
| 0x80090308 | 给函数提供的标志无效 |
The token supplied to the function is invalid |
| 0x80090309 | 安全包无法整理登录缓冲区，因此登录没有成功 |
The security package is not able to marshall the logon buffer, so the logon attempt has failed |
| 0x8009030A | 安全包不支持每消息“质量保护” |
The per-message Quality of Protection is not supported by the security package |
| 0x8009030B | 安全上下文不允许模拟客户端 |
The security context does not allow impersonation of the client |
| 0x8009030C | 登录没有成功 |
The logon attempt failed |
| 0x8009030D | 没有识别提供给安全包的凭证 |
The credentials supplied to the package were not recognized |
| 0x8009030E | 安全包中没有可用的凭证 |
No credentials are available in the security package |
| 0x8009030F | 为验证提供的消息或签名已被更改 |
The message or signature supplied for verification has been altered |
| 0x80090310 | 为验证提供的消息顺序不对 |
The message supplied for verification is out of sequence |
| 0x80090311 | 无法为身份验证与颁发机构取得联系。 |
No authority could be contacted for authentication. |
| 0x80090318 | 提供的消息不完整。无法验证签名。 |
The supplied message is incomplete. The signature was not verified. |
| 0x80090320 | 提供的凭证不完整，无法验证。无法初始化上下文。 |
The credentials supplied were not complete, and could not be verified. The context could not be initialized. |
| 0x80090321 | 提供给函数的缓冲区太小。 |
The buffers supplied to a function was too small. |
| 0x80090322 | 目标主要名称不正确。 |
The target principal name is incorrect. |
| 0x80090324 | 客户端和服务器计算机上的时钟是不一致的。 |
The clocks on the client and server machines are skewed. |
| 0x80090325 | 证书链是由不受信任的颁发机构颁发的。 |
The certificate chain was issued by an authority that is not trusted. |
| 0x80090326 | 接收到的消息异常，或格式不正确。 |
The message received was unexpected or badly formatted. |
| 0x80090327 | 处理证书时，出现了一个未知错误。 |
An unknown error occurred while processing the certificate. |
| 0x80090328 | 收到的证书已过期。 |
The received certificate has expired. |
| 0x80090329 | 无法加密指定的数据。 |
The specified data could not be encrypted. |
| 0x80090331 | 因为算法不同，客户端和服务器无法通信。 |
The client and server cannot communicate, because they do not possess a common algorithm. |
| 0x80090332 | 由于在请求的服务质量中有故障(如，相互身份验证或委派)，无法建立安全上下文。 |
The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation). |
| 0x80090333 | 在上下文完成之前，已删除安全性上下文。这被认为是登录失败。 |
A security context was deleted before the context was completed. This is considered a logon failure. |
| 0x80090334 | 客户端正在协商上下文。服务器要求用户对用户，但没有发送 TGT 应答。 |
The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply. |
| 0x80090335 | 由于本地计算机没有任何 IP 地址，无法完成请求的任务。 |
Unable to accomplish the requested task because the local machine does not have any IP addresses. |
| 0x80090336 | 提供的凭据句柄同与安全上下文相关联的凭据不匹配。 |
The supplied credential handle does not match the credential associated with the security context. |
| 0x80090337 | 由于要求的程序不可用，加密系统或校验和函数无效。 |
The crypto system or checksum function is invalid because a required function is unavailable. |
| 0x80090338 | 超出了最大票证参照数。 |
The number of maximum ticket referrals has been exceeded. |
| 0x80090339 | 本地计算机必须是 Kerberos KDC (域控制器)；而它不是。 |
The local machine must be a Kerberos KDC (domain controller) and it is not. |
| 0x8009033A | 安全协商的另一端要求较强的加密，但本地计算机不支持。 |
The other end of the security negotiation is requires strong crypto but it is not supported on the local machine. |
| 0x8009033B | KDC 应答包含不止一个主要名称。 |
The KDC reply contained more than one principal name. |
| 0x8009033C | 应能在 PA 数据中找到使用的 etype 类型的信息，但找不到。 |
Expected to find PA data for a hint of what etype to use, but it was not found. |
| 0x8009033D | 客户端证书不包含有效的 UPN，或与登录请求中的客户端名称不匹配。请与管理员联系。 |
The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator. |
| 0x8009033E | 要求智能卡登录，但没有使用。 |
Smartcard logon is required and was not used. |
| 0x80090340 | 向 KDC 发送了无效的请求。 |
An invalid request was sent to the KDC. |
| 0x80090341 | KDC 无法为要求的服务生成参照。 |
The KDC was unable to generate a referral for the service requested. |
| 0x80090342 | KDC 不支持请求的加密类型。 |
The encryption type requested is not supported by the KDC. |
| 0x80090343 | Kerberos 包中存在不受支持的预身份验证机制。 |
An unsupported preauthentication mechanism was presented to the Kerberos package. |
| 0x80090345 | 请求的操作无法完成。此计算机必须为委派而被信任，并且当前用户帐户必须配置以允许委派。 |
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. |
| 0x80090346 | 客户端提供的 SSPI 通道绑定不正确。 |
Client's supplied SSPI channel bindings were incorrect. |
| 0x80090347 | 收到的证书被映射到多个帐户。 |
The received certificate was mapped to multiple accounts. |
| 0x80090348 | SEC_E_NO_KERB_KEY |
SEC_E_NO_KERB_KEY |
| 0x80090349 | 证书对于请求用法无效。 |
The certificate is not valid for the requested usage. |
| 0x80090351 | 用于身份验证的智能卡证书已经吊销。请与你的系统管理员联系。事件日志中可能有额外的信息。 |
The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log. |
| 0x80090352 | 在处理用于身份验证的智能卡证书时，检测到一个不受信任的证书颁发机构。请与系统管理员联系。 |
An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator. |
| 0x80090353 | 无法确定用于身份验证的智能卡证书的吊销状态。请与系统管理员联系。 |
The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator. |
| 0x80090354 | 用于身份验证的智能卡证书不被信任。请与系统管理员联系。 |
The smartcard certificate used for authentication was not trusted. Please contact your system administrator. |
| 0x80090355 | 用于身份验证的智能卡证书已经过期。请与系统管理员联系。 |
The smartcard certificate used for authentication has expired. Please contact your system administrator. |
| 0x80090356 | Kerberos 子系统遇到错误。用于用户协议请求服务的域控制器不支持用户的服务。 |
The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user. |
| 0x80090357 | 此服务器已经尝试为服务器领域之外的目标进行 Kerberos 约束委派请求。不支持此操作，并且指出允许此服务器上的错误配置委派到列表。请与管理员联系。 |
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. |
| 0x80090358 | 无法决定用于智能卡身份验证的域控制器证书的吊销状态。系统事件日志中有其他信息。请与你的系统管理员联系。 |
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. |
| 0x80090359 | 处理用于身份验证的域控制器证书时检测到不受信任的证书颁发机构。系统事件日志中有其他信息。请与系统管理员联系。 |
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. |
| 0x8009035A | 用于智能卡登录的域控制器证书已经过期。请与你的系统管理员联系并提供系统事件日志的内容。 |
The domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log. |
| 0x8009035B | 用于智能卡登录的域控制器证书已经被吊销。请与你的系统管理员联系并提供系统事件日志的内容。 |
The domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log. |
| 0x8009035D | 传递到函数的一个或多个参数无效。 |
One or more of the parameters passed to the function was invalid. |
| 0x8009035E | 客户端策略不允许向目标服务器委派凭据。 |
Client policy does not allow credential delegation to target server. |
| 0x8009035F | 客户端策略不允许向使用 NLTM 唯一身份验证的目标服务器委派凭据。 |
Client policy does not allow credential delegation to target server with NLTM only authentication. |
| 0x80090361 | 要求的安全上下文不存在。 |
The required security context does not exist. |
| 0x80090362 | 尝试使用关联证书时，PKU2U 协议出现错误。 |
The PKU2U protocol encountered an error while attempting to utilize the associated certificates. |
| 0x80090363 | 无法验证服务器计算机的标识。 |
The identity of the server computer could not be verified. |
| 0x80090365 | 仅允许 https 方案。 |
Only https scheme is allowed. |
| 0x80090367 | 在客户端和服务器之间不存在公用应用程序协议。应用程序协议协商失败。 |
No common application protocol exists between the client and the server. Application protocol negotiation failed. |
| 0x80090369 | 你不能使用这种格式的用户 ID 登录。请尝试改用你的电子邮件地址。 |
You can't sign in with a user ID in this format. Try using your email address instead. |
| 0x80091001 | 在进行加密消息操作时出错。 |
An error occurred while performing an operation on a cryptographic message. |
| 0x80091002 | 未知的加密算法。 |
Unknown cryptographic algorithm. |
| 0x80091003 | 对象标识符格式不对。 |
The object identifier is poorly formatted. |
| 0x80091004 | 无效的加密消息类型。 |
Invalid cryptographic message type. |
| 0x80091005 | 异常的加密消息编码。 |
Unexpected cryptographic message encoding. |
| 0x80091006 | 加密消息没有包含预期的验证属性。 |
The cryptographic message does not contain an expected authenticated attribute. |
| 0x80091007 | 哈希数值不正确。 |
The hash value is not correct. |
| 0x80091008 | 索引数值无效。 |
The index value is not valid. |
| 0x80091009 | 已解密加密消息的内容。 |
The content of the cryptographic message has already been decrypted. |
| 0x8009100A | 尚未解密加密消息的内容。 |
The content of the cryptographic message has not been decrypted yet. |
| 0x8009100B | 封装数据消息不包含指定的接收者。 |
The enveloped-data message does not contain the specified recipient. |
| 0x8009100C | 无效的控件类型。 |
Invalid control type. |
| 0x8009100D | 无效的颁发者和/或序列号。 |
Invalid issuer and/or serial number. |
| 0x8009100E | 找不到原始签名者。 |
Cannot find the original signer. |
| 0x8009100F | 加密消息不包含所有请求的属性。 |
The cryptographic message does not contain all of the requested attributes. |
| 0x80091010 | 流程式加密信息还未准备好返回数据。 |
The streamed cryptographic message is not ready to return data. |
| 0x80091011 | 流程式加密消息需要更多数据才能完成解码。 |
The streamed cryptographic message requires more data to complete the decode operation. |
| 0x80092001 | 指定的用于输出数据的长度不够大。 |
The length specified for the output data was insufficient. |
| 0x80092002 | 在编码或解码时出错。 |
An error occurred during encode or decode operation. |
| 0x80092003 | 在读取或写入文件时出错。 |
An error occurred while reading or writing to a file. |
| 0x80092004 | 找不到对象或属性。 |
Cannot find object or property. |
| 0x80092005 | 对象或属性已经存在。 |
The object or property already exists. |
| 0x80092006 | 没有为存储或对象指定提供程序。 |
No provider was specified for the store or object. |
| 0x80092007 | 指定的证书已自签名。 |
The specified certificate is self signed. |
| 0x80092008 | 上一个证书或 CRL 上下文已删除。 |
The previous certificate or CRL context was deleted. |
| 0x80092009 | 找不到申请的对象。 |
Cannot find the requested object. |
| 0x8009200A | 证书没有参照私钥的属性。 |
The certificate does not have a property that references a private key. |
| 0x8009200B | 找不到解密的证书和私钥。 |
Cannot find the certificate and private key for decryption. |
| 0x8009200C | 找不到可用于解密的证书和私钥。 |
Cannot find the certificate and private key to use for decryption. |
| 0x8009200D | 不是一个加密消息或加密消息的格式不正确。 |
Not a cryptographic message or the cryptographic message is not formatted correctly. |
| 0x8009200E | 经过签名的加密消息没有签名者以进行索引。 |
The signed cryptographic message does not have a signer for the specified signer index. |
| 0x8009200F | 最终关闭将挂起，直到进一步释放或关闭。 |
Final closure is pending until additional frees or closes. |
| 0x80092010 | 证书已被吊销。 |
The certificate is revoked. |
| 0x80092011 | 找不到 Dll 或导出的函数来验证吊销。 |
No Dll or exported function was found to verify revocation. |
| 0x80092012 | 吊销功能无法检查证书是否吊销。 |
The revocation function was unable to check revocation for the certificate. |
| 0x80092013 | 由于吊销服务器已脱机，吊销功能无法检查吊销。 |
The revocation function was unable to check revocation because the revocation server was offline. |
| 0x80092014 | 证书不在吊销服务器的数据库中。 |
The certificate is not in the revocation server's database. |
| 0x80092020 | 此字符串包含一个非数字字符。 |
The string contains a non-numeric character. |
| 0x80092021 | 此字符串包含一个不可打印的字符。 |
The string contains a non-printable character. |
| 0x80092022 | 此字符串包含一个不在 7 位 ASCII 码字符集内的字符。 |
The string contains a character not in the 7 bit ASCII character set. |
| 0x80092023 | 字符串包含一个无效的 X500 名称属性项，oid，值或分隔字符。 |
The string contains an invalid X500 name attribute key, oid, value or delimiter. |
| 0x80092024 | CERT_NAME_VALUE 的 dwValueType 不是字符串。它很可能是 CERT_RDN_ENCODED_BLOB 或 CERT_RDN_OCTET_STRING。 |
The 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. |
| 0x80092025 | Put 操作无法继续。文件需要重调大小。不过目前已经有一个签名。你必须完成完整签名操作。 |
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. |
| 0x80092026 | 由于本地安全选项设置，加密操作已经失败。 |
The cryptographic operation failed due to a local security option setting. |
| 0x80092027 | 找不到 DLL 或导出函数来验证主题使用。 |
No DLL or exported function was found to verify subject usage. |
| 0x80092028 | 被调用的函数无法进行主题的使用检查。 |
The called function was unable to do a usage check on the subject. |
| 0x80092029 | 因为服务器脱机，被调用的函数无法完成使用检查。 |
Since the server was offline, the called function was unable to complete the usage check. |
| 0x8009202A | 在证书信任列表(CTL)中找不到使用者。 |
The subject was not found in a Certificate Trust List (CTL). |
| 0x8009202B | 加密消息或证书信任列表的签名者都不可信任。 |
None of the signers of the cryptographic message or certificate trust list is trusted. |
| 0x8009202C | 找不到公钥的算法参数。 |
The public key's algorithm parameters are missing. |
| 0x8009202D | 使用具有给定名称的对象定位器基础结构无法定位对象。 |
An object could not be located using the object locator infrastructure with the given name. |
| 0x80093000 | OSS 证书编码/解码错误代码请查看 asn1code.h 了解 OSS 运行时错误的定义。OSS 错误值以 CRYPT_E_OSS_ERROR 为偏移值。 |
OSS Certificate encode/decode error code baseSee asn1code.h for a definition of the OSS runtime errors. The OSS error values are offset by CRYPT_E_OSS_ERROR. |
| 0x80093001 | OSS ASN.1 错误: 输出缓冲区太小。 |
OSS ASN.1 Error: Output Buffer is too small. |
| 0x80093002 | OSS ASN.1 错误: 符号整数被当作无符号整数编码。 |
OSS ASN.1 Error: Signed integer is encoded as a unsigned integer. |
| 0x80093003 | OSS ASN.1 错误: 未知的 ASN.1 数据类型。 |
OSS ASN.1 Error: Unknown ASN.1 data type. |
| 0x80093004 | OSS ASN.1 错误: 输出缓冲区太小，经过解码的数据被缩短。 |
OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated. |
| 0x80093005 | OSS ASN.1 错误: 无效数据。 |
OSS ASN.1 Error: Invalid data. |
| 0x80093006 | OSS ASN.1 错误: 无效参数。 |
OSS ASN.1 Error: Invalid argument. |
| 0x80093007 | OSS ASN.1 错误: 编码/解码版本不匹配。 |
OSS ASN.1 Error: Encode/Decode version mismatch. |
| 0x80093008 | OSS ASN.1 错误: 内存不足。 |
OSS ASN.1 Error: Out of memory. |
| 0x80093009 | OSS ASN.1 错误: 编码/解码错误。 |
OSS ASN.1 Error: Encode/Decode Error. |
| 0x8009300A | OSS ASN.1 错误: 内部错误。 |
OSS ASN.1 Error: Internal Error. |
| 0x8009300D | OSS ASN.1 错误: 不受支持的 BER 不定长度编码。 |
OSS ASN.1 Error: Unsupported BER indefinite-length encoding. |
| 0x8009300E | OSS ASN.1 错误: 访问冲突。 |
OSS ASN.1 Error: Access violation. |
| 0x80093013 | OSS ASN.1 错误: 多线程冲突。 |
OSS ASN.1 Error: Multi-threading conflict. |
| 0x80093017 | OSS ASN.1 错误: 没有执行编码/解码功能。 |
OSS ASN.1 Error: Encode/Decode function not implemented. |
| 0x80093018 | OSS ASN.1 错误: 跟踪文件错误。 |
OSS ASN.1 Error: Trace file error. |
| 0x80093019 | OSS ASN.1 错误: 功能没有实现。 |
OSS ASN.1 Error: Function not implemented. |
| 0x8009301A | OSS ASN.1 错误: 程序链接错误。 |
OSS ASN.1 Error: Program link error. |
| 0x8009302D | OSS ASN.1 错误: 系统资源错误。 |
OSS ASN.1 Error: System resource error. |
| 0x80093100 | ASN1 证书编码/解码错误代码。ASN1 错误值以 CRYPT_E_ASN1_ERROR 为偏移值。 |
ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR. |
| 0x80093101 | ASN1 内部编码或解码错误。 |
ASN1 internal encode or decode error. |
| 0x80093102 | ASN1 异常的数据结尾。 |
ASN1 unexpected end of data. |
| 0x80093103 | ASN1 损坏的数据。 |
ASN1 corrupted data. |
| 0x80093104 | ASN1 值太大。 |
ASN1 value too large. |
| 0x80093105 | ASN1 违反了约束条件。 |
ASN1 constraint violated. |
| 0x80093106 | ASN1 内存不足。 |
ASN1 out of memory. |
| 0x80093107 | ASN1 缓冲区溢出。 |
ASN1 buffer overflow. |
| 0x80093108 | ASN1 这个 PDU 不支持该函数。 |
ASN1 function not supported for this PDU. |
| 0x80093109 | ASN1 函数调用的错误参数。 |
ASN1 bad arguments to function call. |
| 0x8009310A | ASN1 不正确的实值。 |
ASN1 bad real value. |
| 0x8009310B | ASN1 遇到了不正确的标记值。 |
ASN1 bad tag value met. |
| 0x8009310C | ASN1 不正确的选择值。 |
ASN1 bad choice value. |
| 0x8009310D | ASN1 不正确的加码规则。 |
ASN1 bad encoding rule. |
| 0x8009310E | ASN1 不正确的 unicode (UTF8)。 |
ASN1 bad unicode (UTF8). |
| 0x80093133 | ASN1 不正确的 PDU 类型。 |
ASN1 bad PDU type. |
| 0x80093134 | ASN1 尚未执行。 |
ASN1 not yet implemented. |
| 0x80093201 | ASN1 跳过了未知扩展名。 |
ASN1 skipped unknown extension(s). |
| 0x80093202 | ASN1 要求有数据结尾 |
ASN1 end of data expected |
| 0x80094001 | 请求主题名无效，或太长。 |
The request subject name is invalid or too long. |
| 0x80094002 | 请求不存在。 |
The request does not exist. |
| 0x80094003 | 请求的目前状态不允许此操作。 |
The request's current status does not allow this operation. |
| 0x80094004 | 要求的属性数值是空的。 |
The requested property value is empty. |
| 0x80094005 | 证书颁发机构的证书包含无效数据。 |
The certification authority's certificate contains invalid data. |
| 0x80094006 | 由于数据库还原操作，证书服务被暂停。 |
Certificate service has been suspended for a database restore operation. |
| 0x80094007 | 证书含有一个可能与旧的注册软件不兼容的经过编码的长度。 |
The certificate contains an encoded length that is potentially incompatible with older enrollment software. |
| 0x80094008 | 操作被拒绝。用户被分配了多个角色，但是证书颁发机构被配置成强制角色分隔。 |
The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation. |
| 0x80094009 | 操作被拒绝。它只能由允许管理当前申请者的证书的证书管理器执行。 |
The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester. |
| 0x8009400A | 不能将私钥存档。没有将证书颁发机构配置为将密钥存档。 |
Cannot archive private key. The certification authority is not configured for key archival. |
| 0x8009400B | 无法存档私钥。证书颁发机构无法确认至少一个密钥恢复证书。 |
Cannot archive private key. The certification authority could not verify one or more key recovery certificates. |
| 0x8009400C | 申请的格式不对。加密了的私钥必须处于最外签名内的未经身份验证的属性里。 |
The request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature. |
| 0x8009400D | 至少一个安全主体必须有管理此 CA 的权限。 |
At least one security principal must have the permission to manage this CA. |
| 0x8009400E | 请求含有一个无效续订证书属性。 |
The request contains an invalid renewal certificate attribute. |
| 0x8009400F | 试图打开证书颁发机构数据库会话，但已有太多的活动会话。可能需要配置服务器以允许附加的会话。 |
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. |
| 0x80094010 | 内存引用导致数据对齐错误。 |
A memory reference caused a data alignment fault. |
| 0x80094011 | 此证书颁发机构的权限不允许当前用户注册证书。 |
The permissions on this certification authority do not allow the current user to enroll for certificates. |
| 0x80094012 | 此证书模板上的权限不允许当前用户注册此类型的证书。 |
The permissions on the certificate template do not allow the current user to enroll for this type of certificate. |
| 0x80094013 | 联系的域控制器不支持签名 LDAP 流量。更新域控制器或配置证书服务以使用 SSL 访问 Active Directory。 |
The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access. |
| 0x80094014 | 证书管理器或 CA 管理员拒绝了该请求。 |
The request was denied by a certificate manager or CA administrator. |
| 0x80094015 | 找不到注册策略服务器。 |
An enrollment policy server cannot be located. |
| 0x80094016 | 签名算法或公钥长度不符合系统要求的最低强度。 |
A signature algorithm or public key length does not meet the system's minimum required strength. |
| 0x80094017 | 无法创建证明的密钥。此计算机或加密提供程序无法满足硬件要求以支持密钥证明。 |
Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation. |
| 0x80094018 | 未指定任何加密证书。 |
No encryption certificate was specified. |
| 0x80094800 | 这个 CA 不支持请求的证书模板。 |
The requested certificate template is not supported by this CA. |
| 0x80094801 | 请求不包含证书模板信息。 |
The request contains no certificate template information. |
| 0x80094802 | 请求包含矛盾的模板信息。 |
The request contains conflicting template information. |
| 0x80094803 | 请求缺少一个所需的使用者替换名称扩展。 |
The request is missing a required Subject Alternate name extension. |
| 0x80094804 | 请求缺少一个服务器存档所需的私钥。 |
The request is missing a required private key for archival by the server. |
| 0x80094805 | 请求缺少一个所需的 SMIME 功能扩展。 |
The request is missing a required SMIME capabilities extension. |
| 0x80094806 | 请求是代表一个使用者而不是一个调用方而执行的。证书模板必须配置为要求使用至少一个签名来对请求进行身份验证。 |
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. |
| 0x80094807 | 请求模板版本比支持的模板版本新。 |
The request template version is newer than the supported template version. |
| 0x80094808 | 模板缺少一个所需的签名策略属性。 |
The template is missing a required signature policy attribute. |
| 0x80094809 | 请求缺少所需的签名策略信息。 |
The request is missing required signature policy information. |
| 0x8009480A | 请求缺少至少一个所需的签名。 |
The request is missing one or more required signatures. |
| 0x8009480B | 至少一个签名没有包括所需的应用程序或颁发策略。请求缺少至少一个所需的有效签名。 |
One or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures. |
| 0x8009480C | 请求缺少至少一个所需的签名颁发策略。 |
The request is missing one or more required signature issuance policies. |
| 0x8009480D | UPN 名不可用，无法添加到使用者替换名称。 |
The UPN is unavailable and cannot be added to the Subject Alternate name. |
| 0x8009480E | Active Directory GUID 不可用，无法添加到使用者替换名称。 |
The Active Directory GUID is unavailable and cannot be added to the Subject Alternate name. |
| 0x8009480F | DNS 名不可用，无法添加到使用者替换名称。 |
The DNS name is unavailable and cannot be added to the Subject Alternate name. |
| 0x80094810 | 请求包括一个服务器用来存档的私钥，但密钥存档没有为指定的证书模板而启用。 |
The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template. |
| 0x80094811 | 公钥不符合指定的证书模板要求的最小值。 |
The public key does not meet the minimum size required by the specified certificate template. |
| 0x80094812 | 电子邮件名称不可用而且无法添加到使用者或使用者替换名称。 |
The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name. |
| 0x80094813 | 无法在此证书颁发机构找到一个或多个证书模板。 |
One or more certificate templates to be enabled on this certification authority could not be found. |
| 0x80094814 | 证书模板的续订期超过证书有效期。模板应该重新配置或者续订 CA 证书。 |
The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed. |
| 0x80094815 | 证书模板需要过多的 RA 签名。仅允许一个 RA 签名。 |
The certificate template requires too many RA signatures. Only one RA signature is allowed. |
| 0x80094816 | 证书模板要求使用相同的公钥进行续订，但是该请求使用了不同的公钥。 |
The certificate template requires renewal with the same public key, but the request uses a different public key. |
| 0x80094817 | 证书颁发机构无法解释或验证在请求中提供的认可密钥信息，或者这些信息不一致。 |
The certification authority cannot interpret or verify the endorsement key information supplied in the request, or the information is inconsistent. |
| 0x80094818 | 证书颁发机构无法验证证明标识密钥 ID 绑定。 |
The certification authority cannot validate the Attestation Identity Key Id Binding. |
| 0x80094819 | 证书颁发机构无法验证私钥证明数据。 |
The certification authority cannot validate the private key attestation data. |
| 0x8009481A | 请求不支持证书模板中定义的私钥证明。 |
The request does not support private key attestation as defined in the certificate template. |
| 0x8009481B | 请求公钥与私钥证明数据不一致。 |
The request public key is not consistent with the private key attestation data. |
| 0x8009481C | 无法验证私钥证明质询，因为加密证书已过期，或者证书或密钥不可用。 |
The private key attestation challenge cannot be validated because the encryption certificate has expired, or the certificate or key is unavailable. |
| 0x8009481D | 无法验证证明响应。证明响应异常或不正确。 |
The attestation response could not be validated. It is either unexpected or incorrect. |
| 0x8009481E | 在请求属性中检测不到有效的请求 ID，或提交的请求 ID 无效。 |
A valid Request ID was not detected in the request attributes, or an invalid one was submitted. |
| 0x80095000 | 无法导出密钥。 |
The key is not exportable. |
| 0x80095001 | 你不能将根 CA 证书添加到你的本地存储区。 |
You cannot add the root CA certificate into your local store. |
| 0x80095002 | 在响应中找不到密钥存档哈希属性。 |
The key archival hash attribute was not found in the response. |
| 0x80095003 | 在响应中找到了一个意外的密钥存档哈希属性。 |
An unexpected key archival hash attribute was found in the response. |
| 0x80095004 | 请求与响应之间存在一个不匹配的密钥存档哈希。 |
There is a key archival hash mismatch between the request and the response. |
| 0x80095005 | 签名证书不能包含 SMIME 扩展。 |
Signing certificate cannot include SMIME extension. |
| 0x80096001 | 验证信任关系时，系统层上出现了一个错误。 |
A system-level error occurred while verifying trust. |
| 0x80096002 | 消息签名者的证书无效，或找不到。 |
The certificate for the signer of the message is invalid or not found. |
| 0x80096003 | 其中一个副署无效。 |
One of the counter signatures was invalid. |
| 0x80096004 | 无法验证证书的签名。 |
The signature of the certificate cannot be verified. |
| 0x80096005 | 时间戳签名和/或证书无法验证或已损坏。 |
The timestamp signature and/or certificate could not be verified or is malformed. |
| 0x80096010 | 没有验证对象的数字签名。 |
The digital signature of the object did not verify. |
| 0x80096011 | 该对象的数字签名格式错误。有关技术细节，请参阅安全公告 MS13-098。 |
The digital signature of the object is malformed. For technical detail, see security bulletin MS13-098. |
| 0x80096019 | 尚未观察到证书的基本约束扩展。 |
A certificate's basic constraint extension has not been observed. |
| 0x8009601E | 证书不符合或包含 Authenticode(TM)财务扩展。 |
The certificate does not meet or contain the Authenticode(tm) financial extensions. |
| 0x80097001 | 试图引用适当范围外文件的一部分。 |
Tried to reference a part of the file outside the proper range. |
| 0x80097002 | 未能从文件检索对象。 |
Could not retrieve an object from the file. |
| 0x80097003 | 找不到文件中的标题表格。 |
Could not find the head table in the file. |
| 0x80097004 | 标题表格中的幻数不正确。 |
The magic number in the head table is incorrect. |
| 0x80097005 | 位移表格有不正确的数值。 |
The offset table has incorrect values. |
| 0x80097006 | 重复表格标签或标签没有按字母顺序排列。 |
Duplicate table tags or tags out of alphabetical order. |
| 0x80097007 | 表格不在长字边界上开始。 |
A table does not start on a long word boundary. |
| 0x80097008 | 标题信息后没有第一个表格。 |
First table does not appear after header information. |
| 0x80097009 | 两个或更多的表格有重叠现象。 |
Two or more tables overlap. |
| 0x8009700A | 表格之间的填充字节太多，或者填充字节不是 0。 |
Too many pad bytes between tables or pad bytes are not 0. |
| 0x8009700B | 文件太小，无法包含最后一个表格。 |
File is too small to contain the last table. |
| 0x8009700C | 表格检查和不正确。 |
A table checksum is incorrect. |
| 0x8009700D | 文件检查和不正确。 |
The file checksum is incorrect. |
| 0x80097010 | 签名没有正确的策略属性。 |
The signature does not have the correct attributes for the policy. |
| 0x80097011 | 文件没有通过提示检查。 |
The file did not pass the hints check. |
| 0x80097012 | 文件不是 OpenType 文件。 |
The file is not an OpenType file. |
| 0x80097013 | 文件操作失败(打开、映射、读取、写入)。 |
Failed on a file operation (open, map, read, write). |
| 0x80097014 | CryptoAPI 函数调用没有成功。 |
A call to a CryptoAPI function failed. |
| 0x80097015 | 文件中有一个错误的版本号。 |
There is a bad version number in the file. |
| 0x80097016 | DSIG 表格的结构不正确。 |
The structure of the DSIG table is incorrect. |
| 0x80097017 | 对部分固定表格的检查没有成功。 |
A check failed in a partially constant table. |
| 0x80097018 | 某种结构错误。 |
Some kind of structural error. |
| 0x80097019 | 请求的凭据要求确认。 |
The requested credential requires confirmation. |
| 0x800B0001 | 未知的信任提供程序。 |
Unknown trust provider. |
| 0x800B0002 | 指定的信任提供程序不支持该指定的信任验证操作。 |
The trust verification action specified is not supported by the specified trust provider. |
| 0x800B0003 | 指定的信任提供程序不认识或不支持使用者的指定格式。 |
The form specified for the subject is not one supported or known by the specified trust provider. |
| 0x800B0004 | 对于指定的操作，该使用者不受信任。 |
The subject is not trusted for the specified action. |
| 0x800B0005 | 由于 ASN.1 编码过程问题出错。 |
Error due to problem in ASN.1 encoding process. |
| 0x800B0006 | 由于 ASN.1 解码过程问题出错。 |
Error due to problem in ASN.1 decoding process. |
| 0x800B0007 | 读/写具有适当属性的扩展，反之亦然。 |
Reading / writing Extensions where Attributes are appropriate, and vice versa. |
| 0x800B0008 | 未指定的密码失败。 |
Unspecified cryptographic failure. |
| 0x800B0009 | 无法确定数据的大小。 |
The size of the data could not be determined. |
| 0x800B000A | 数据大小没有定义，无法确定。 |
The size of the indefinite-sized data could not be determined. |
| 0x800B000B | 该对象没有读写自动调整大小的数据。 |
This object does not read and write self-sizing data. |
| 0x800B0100 | 主题中没有签名。 |
No signature was present in the subject. |
| 0x800B0101 | 根据当前系统时钟或签名文件中的时间戳验证时要求的证书不在有效期内。 |
A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. |
| 0x800B0102 | 证书链的有效时期嵌套不正确。 |
The validity periods of the certification chain do not nest correctly. |
| 0x800B0103 | 正在将只能用作最终实体的证书用作 CA，反之亦然。 |
A certificate that can only be used as an end-entity is being used as a CA or vice versa. |
| 0x800B0104 | 违反了证书链的路径长度限定。 |
A path length constraint in the certification chain has been violated. |
| 0x800B0105 | 证书含有标记为 'critical' 的未知扩展名。 |
A certificate contains an unknown extension that is marked 'critical'. |
| 0x800B0106 | 证书没有被用于证书颁发机构指定的目的。 |
A certificate being used for a purpose other than the ones specified by its CA. |
| 0x800B0107 | 事实上，所给证书的父证书没有颁发此子证书。 |
A parent of a given certificate in fact did not issue that child certificate. |
| 0x800B0108 | 找不到证书，或某个重要字符域(例如使用者或颁发者姓名)是空的。 |
A certificate is missing or has an empty value for an important field, such as a subject or issuer name. |
| 0x800B0109 | 已处理证书链，但是在不受信任提供程序信任的根证书中终止。 |
A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. |
| 0x800B010A | 无法建立到信任根颁发机构的证书链。 |
A certificate chain could not be built to a trusted root authority. |
| 0x800B010B | 一般信任关系失败。 |
Generic trust failure. |
| 0x800B010C | 证书已被颁发者直接吊销。 |
A certificate was explicitly revoked by its issuer. |
| 0x800B010D | 由于当前的策略设置，该测试根不受信任，证书路径因此而终止。 |
The certification path terminates with the test root which is not trusted with the current policy settings. |
| 0x800B010E | 吊销过程无法继续 - 无法检测证书。 |
The revocation process could not continue - the certificate(s) could not be checked. |
| 0x800B010F | 证书的 CN 名与传递的值不匹配。 |
The certificate's CN name does not match the passed value. |
| 0x800B0111 | 这个证书被明确标注成不能被用户信任。 |
The certificate was explicitly marked as untrusted by the user. |
| 0x800B0112 | 证书链处理得正确，但是其中一个 CA 证书不受策略提供程序的信任。 |
A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider. |
| 0x800B0113 | 证书的策略无效。 |
The certificate has invalid policy. |
| 0x800B0114 | 证书的名称无效。此名称未包含在允许列表中或被显式排除了。 |
The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded. |
| 0x800C0002 | URL 无效。 |
The URL is invalid. |
| 0x800C0003 | 未建立任何 Internet 会话。 |
No Internet session has been established. |
| 0x800C0004 | 无法连接到目标服务器。 |
Unable to connect to the target server. |
| 0x800C0005 | 系统无法找到指定的资源。 |
The system cannot locate the resource specified. |
| 0x800C0006 | 系统无法找到指定的对象。 |
The system cannot locate the object specified. |
| 0x800C0007 | 请求的资源没有可用数据。 |
No data is available for the requested resource. |
| 0x800C0008 | 指定资源下载失败。 |
The download of the specified resource has failed. |
| 0x800C0009 | 访问该资源需要进行身份验证。 |
Authentication is required to access this resource. |
| 0x800C000A | 服务器无法识别所提供的 MIME 类型。 |
The server could not recognize the provided mime type. |
| 0x800C000B | 操作超时。 |
The operation was timed out. |
| 0x800C000C | 服务器不理解该请求，或者该请求无效。 |
The server did not understand the request, or the request was invalid. |
| 0x800C000D | 指定的协议未知。 |
The specified protocol is unknown. |
| 0x800C000E | 出现安全性问题。 |
A security problem occurred. |
| 0x800C000F | 系统无法加载永久性数据。 |
The system could not load the persisted data. |
| 0x800C0010 | 无法实例化此对象。 |
Unable to instantiate the object. |
| 0x800C0014 | 出现重定向问题。 |
A redirection problem occurred. |
| 0x800C0015 | 请求的资源是一个目录，而不是一个文件。 |
The requested resource is a directory, not a file. |
| 0x800C0019 | 访问此资源所需的安全证书无效。 |
Security certificate required to access this resource is invalid. |
| 0x800F0000 | 段落开始之前，INF 中有一个非空白行。 |
A non-empty line was encountered in the INF before the start of a section. |
| 0x800F0001 | INF 中的段落名标记不完整，或是没有单独在一行上。 |
A section name marker in the INF is not complete, or does not exist on a line by itself. |
| 0x800F0002 | 某 INF 段落的名称超过最长段落名。 |
An INF section was encountered whose name exceeds the maximum section name length. |
| 0x800F0003 | INF 语法不正确。 |
The syntax of the INF is invalid. |
| 0x800F0100 | INF 形式与要求的形式不同。 |
The style of the INF is different than what was requested. |
| 0x800F0101 | 在 INF 中找不到所需的段落。 |
The required section was not found in the INF. |
| 0x800F0102 | 在 INF 中找不到所需的行。 |
The required line was not found in the INF. |
| 0x800F0103 | 受这个文件队列安装影响的文件还没有为卸载做备份。 |
The files affected by the installation of this file queue have not been backed up for uninstall. |
| 0x800F0200 | INF、设备信息集或元素都没有相关的安装类。 |
The INF or the device information set or element does not have an associated install class. |
| 0x800F0201 | INF、设备信息集或元素都不符合指定的安装类。 |
The INF or the device information set or element does not match the specified install class. |
| 0x800F0202 | 找到的现存设备是正在手动安装的设备的副本。 |
An existing device was found that is a duplicate of the device being manually installed. |
| 0x800F0203 | 没有为设备信息集或元素选择驱动程序。 |
There is no driver selected for the device information set or element. |
| 0x800F0204 | 要求的设备注册表项不存在。 |
The requested device registry key does not exist. |
| 0x800F0205 | 设备实例名无效。 |
The device instance name is invalid. |
| 0x800F0206 | 安装类不存在或无效。 |
The install class is not present or is invalid. |
| 0x800F0207 | 无法创建设备实例，因为它已经存在。 |
The device instance cannot be created because it already exists. |
| 0x800F0208 | 操作无法在尚未注册的设备信息元素上运行。 |
The operation cannot be performed on a device information element that has not been registered. |
| 0x800F0209 | 设备属性码无效。 |
The device property code is invalid. |
| 0x800F020A | 用来创建驱动程序列表的 INF 不存在。 |
The INF from which a driver list is to be built does not exist. |
| 0x800F020B | 设备实例不在硬件树中。 |
The device instance does not exist in the hardware tree. |
| 0x800F020C | 无法加载代表这个安装类的图标。 |
The icon representing this install class cannot be loaded. |
| 0x800F020D | 类安装程序注册表项无效。 |
The class installer registry entry is invalid. |
| 0x800F020E | 类安装程序已经指出应该为这个安装请求运行默认操作。 |
The class installer has indicated that the default action should be performed for this installation request. |
| 0x800F020F | 操作不要求复制任何文件。 |
The operation does not require any files to be copied. |
| 0x800F0210 | 指定的硬件配置文件不存在。 |
The specified hardware profile does not exist. |
| 0x800F0211 | 目前并未替这个设备信息集选择设备信息元素。 |
There is no device information element currently selected for this device information set. |
| 0x800F0212 | 由于设备信息集已被锁定，操作无法运行。 |
The operation cannot be performed because the device information set is locked. |
| 0x800F0213 | 由于设备信息元素已被锁定，操作无法运行。 |
The operation cannot be performed because the device information element is locked. |
| 0x800F0214 | 指定的路径不包含适用的设备 INF。 |
The specified path does not contain any applicable device INFs. |
| 0x800F0215 | 尚未为设备信息集或元素设置类安装程序参数。 |
No class installer parameters have been set for the device information set or element. |
| 0x800F0216 | 由于文件队列已被锁定，操作无法运行。 |
The operation cannot be performed because the file queue is locked. |
| 0x800F0217 | 这个 INF 中的服务安装段落无效。 |
A service installation section in this INF is invalid. |
| 0x800F0218 | 这个设备信息元素没有类驱动程序列表。 |
There is no class driver list for the device information element. |
| 0x800F0219 | 由于没有为设备实例指定函数驱动程序，安装没有成功。 |
The installation failed because a function driver was not specified for this device instance. |
| 0x800F021A | 目前没有为这个接口类指定的默认设备接口。 |
There is presently no default device interface designated for this interface class. |
| 0x800F021B | 设备接口在使用中，无法执行操作。 |
The operation cannot be performed because the device interface is currently active. |
| 0x800F021C | 设备接口已经从系统上删除，无法执行操作。 |
The operation cannot be performed because the device interface has been removed from the system. |
| 0x800F021D | 这个 INF 中有一个接口安装段落无效。 |
An interface installation section in this INF is invalid. |
| 0x800F021E | 这个接口类不在系统中。 |
This interface class does not exist in the system. |
| 0x800F021F | 给这个接口设备提供的参照字符串无效。 |
The reference string supplied for this interface device is invalid. |
| 0x800F0220 | 指定的计算机名不符合 UNC 命名协议。 |
The specified machine name does not conform to UNC naming conventions. |
| 0x800F0221 | 出现了一般性远程通信错误。 |
A general remote communication error occurred. |
| 0x800F0222 | 此时无法使用为远程通信所选的计算机。 |
The machine selected for remote communication is not available at this time. |
| 0x800F0223 | 即插即用服务在远程计算机上不可用。 |
The Plug and Play service is not available on the remote machine. |
| 0x800F0224 | 属性页提供程序的注册表项无效。 |
The property page provider registry entry is invalid. |
| 0x800F0225 | 要求的设备接口不在系统中。 |
The requested device interface is not present in the system. |
| 0x800F0226 | 设备的辅助安装程序在安装完成后还有额外工作要完成。 |
The device's co-installer has additional work to perform after installation is complete. |
| 0x800F0227 | 设备的辅助安装程序无效。 |
The device's co-installer is invalid. |
| 0x800F0228 | 这个设备没有兼容驱动程序。 |
There are no compatible drivers for this device. |
| 0x800F0229 | 没有代表这个设备或设备类型的图标。 |
There is no icon that represents this device or device type. |
| 0x800F022A | 这个 INF 中指定的一个逻辑配置无效。 |
A logical configuration specified in this INF is invalid. |
| 0x800F022B | 类安装程序拒绝安装或升级此设备的请求。 |
The class installer has denied the request to install or upgrade this device. |
| 0x800F022C | 为此设备安装的一个筛选器驱动程序无效。 |
One of the filter drivers installed for this device is invalid. |
| 0x800F022D | 为该设备选择的驱动程序不支持此版本的 Windows。 |
The driver selected for this device does not support this version of Windows. |
| 0x800F022E | 为这个设备选择的驱动程序不支持 Windows。 |
The driver selected for this device does not support Windows. |
| 0x800F022F | 第三方 INF 不包含数字签名信息。 |
The third-party INF does not contain digital signature information. |
| 0x800F0230 | 试图用设备安装文件队列来验证跟其他平台有关的数字签名，但没有成功。 |
An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms. |
| 0x800F0231 | 无法停用此设备。 |
The device cannot be disabled. |
| 0x800F0232 | 无法动态删除这个设备。 |
The device could not be dynamically removed. |
| 0x800F0233 | 无法复制到指定的目标。 |
Cannot copy to specified target. |
| 0x800F0234 | 驱动程序不适用于该平台。 |
Driver is not intended for this platform. |
| 0x800F0235 | 在 WOW64 中不允许该操作。 |
Operation not allowed in WOW64. |
| 0x800F0236 | 涉及未签字文件复制的操作还原到上一步的操作，因此能设置系统还原点。 |
The operation involving unsigned file copying was rolled back, so that a system restore point could be set. |
| 0x800F0237 | 将 INF 复制到 Windows INF 目录的方式不正确。 |
An INF was copied into the Windows INF directory in an improper manner. |
| 0x800F0238 | 安全配置编辑程序(SCE) API 在此嵌入式的产品中被禁用。 |
The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product. |
| 0x800F0239 | 遇到未知的异常。 |
An unknown exception was encountered. |
| 0x800F023A | 访问即插即用注册表数据库时遇到问题。 |
A problem was encountered when accessing the Plug and Play registry database. |
| 0x800F023B | 请求的操作不被远程计算机支持。 |
The requested operation is not supported for a remote machine. |
| 0x800F023C | 指定的文件不是安装的 OEM INF。 |
The specified file is not an installed OEM INF. |
| 0x800F023D | 一个或多个设备目前使用指定的 INF 安装。 |
One or more devices are presently installed using the specified INF. |
| 0x800F023E | 请求的设备安装操作已过时。 |
The requested device install operation is obsolete. |
| 0x800F023F | 不能验证文件，因为它没有经过 Authenticode(TM)签名的相关目录。 |
A file could not be verified because it does not have an associated catalog signed via Authenticode(tm). |
| 0x800F0240 | 不支持指定 .INF 的 Authenticode(TM)签名验证。 |
Authenticode(tm) signature verification is not supported for the specified INF. |
| 0x800F0241 | 此 INF 用来自信任的发布者的 Authenticode(TM)目录签名。 |
The INF was signed with an Authenticode(tm) catalog from a trusted publisher. |
| 0x800F0242 | 尚未建立对 Authenticode(TM)签名的目录的发布者信任。 |
The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted. |
| 0x800F0243 | 没有建立对 Authenticode(TM)签名的目录的发布者信任。 |
The publisher of an Authenticode(tm) signed catalog was not established as trusted. |
| 0x800F0244 | 此软件在其他版本 Windows 上测试符合 Windows 徽标要求，可能与此版本 Windows 不兼容。 |
The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version. |
| 0x800F0245 | 此文件可能仅由经过 Authenticode(TM)签名的目录验证。 |
The file may only be validated by a catalog signed via Authenticode(tm). |
| 0x800F0246 | 此设备的一个安装程序此时无法执行安装。 |
One of the installers for this device cannot perform the installation at this time. |
| 0x800F0247 | 试图将驱动程序添加到存储区时遇到问题。 |
A problem was encountered while attempting to add the driver to the store. |
| 0x800F0248 | 系统策略禁止安装此设备。请与系统管理员联系。 |
The installation of this device is forbidden by system policy. Contact your system administrator. |
| 0x800F0249 | 系统策略禁止安装此驱动程序。请与系统管理员联系。 |
The installation of this driver is forbidden by system policy. Contact your system administrator. |
| 0x800F024A | 为此操作指定的 INF 类型错误。 |
The specified INF is the wrong type for this operation. |
| 0x800F024B | 文件的哈希值不在指定的目录文件中。此文件可能已损坏或被篡改。 |
The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. |
| 0x800F024C | 试图从存储区中删除驱动程序时遇到问题。 |
A problem was encountered while attempting to delete the driver from the store. |
| 0x800F0300 | 遇到无法恢复的堆栈溢出。 |
An unrecoverable stack overflow was encountered. |
| 0x800F1000 | 没有检测到已安装的组件。 |
No installed components were detected. |
| 0x80100002 | 操作被 SCardCancel 请求所取消。 |
The action was cancelled by an SCardCancel request. |
| 0x80100004 | 无法正确解释一个或多个提供的参数。 |
One or more of the supplied parameters could not be properly interpreted. |
| 0x80100005 | 找不到注册表启动信息，或信息无效。 |
Registry startup information is missing or invalid. |
| 0x80100006 | 可用内存不足，无法完成该命令。 |
Not enough memory available to complete this command. |
| 0x80100007 | 内部一致性计时器已经过期。 |
An internal consistency timer has expired. |
| 0x80100008 | 对于返回数据，接收返回数据的数据缓冲区太小。 |
The data buffer to receive returned data is too small for the returned data. |
| 0x80100009 | 无法识别指定的读卡器名。 |
The specified reader name is not recognized. |
| 0x8010000A | 用户指定的超时值已经过期。 |
The user-specified timeout value has expired. |
| 0x8010000B | 由于其他连接尚未完成，不能访问智能卡。 |
The smart card cannot be accessed because of other connections outstanding. |
| 0x8010000C | 该操作需要一个智能卡，但设备中目前没有智能卡。 |
The operation requires a smart card, but no smart card is currently in the device. |
| 0x8010000D | 无法识别指定的智能卡名。 |
The specified smart card name is not recognized. |
| 0x8010000E | 系统无法按要求方式丢弃媒体。 |
The system could not dispose of the media in the requested manner. |
| 0x8010000F | 请求的协议与目前跟智能卡一起使用的协议不兼容。 |
The requested protocols are incompatible with the protocol currently in use with the smart card. |
| 0x80100010 | 读卡器或智能卡尚未准备好接受命令。 |
The reader or smart card is not ready to accept commands. |
| 0x80100011 | 一个或数个提供的参数值未能被正确解释。 |
One or more of the supplied parameters values could not be properly interpreted. |
| 0x80100012 | 操作被系统取消，可能要注销或关机。 |
The action was cancelled by the system, presumably to log off or shut down. |
| 0x80100013 | 检测到一个内部通讯错误。 |
An internal communications error has been detected. |
| 0x80100014 | 检测到一个内部错误，但来源不明。 |
An internal error has been detected, but the source is unknown. |
| 0x80100015 | 从注册表获取的 ATR 不是有效的 ATR 字符串。 |
An ATR obtained from the registry is not a valid ATR string. |
| 0x80100016 | 试图结束一个不存在的事务。 |
An attempt was made to end a non-existent transaction. |
| 0x80100017 | 指定的读卡器目前不可使用。 |
The specified reader is not currently available for use. |
| 0x80100018 | 为了使服务器应用程序退出，已中止操作。 |
The operation has been aborted to allow the server application to exit. |
| 0x80100019 | PCI 接收缓冲区太小。 |
The PCI Receive buffer was too small. |
| 0x8010001A | 读卡器驱动程序不符合支持的最低要求。 |
The reader driver does not meet minimal requirements for support. |
| 0x8010001B | 读卡器驱动程序没有产生一个唯一的读卡器名。 |
The reader driver did not produce a unique reader name. |
| 0x8010001C | 智能卡不符合支持的最低要求。 |
The smart card does not meet minimal requirements for support. |
| 0x8010001D | 智能卡资源管理器未运行。 |
The Smart Card Resource Manager is not running. |
| 0x8010001E | 智能卡资源管理器已关闭。 |
The Smart Card Resource Manager has shut down. |
| 0x8010001F | 卡出现了异常错误。 |
An unexpected card error has occurred. |
| 0x80100020 | 找不到智能卡的主要提供程序。 |
No Primary Provider can be found for the smart card. |
| 0x80100021 | 不支持请求的对象创建顺序。 |
The requested order of object creation is not supported. |
| 0x80100022 | 这个智能卡不支持请求的性能。 |
This smart card does not support the requested feature. |
| 0x80100023 | 识别的目录在智能卡中不存在。 |
The identified directory does not exist in the smart card. |
| 0x80100024 | 标出的文件在智能卡中不存在。 |
The identified file does not exist in the smart card. |
| 0x80100025 | 提供的路径不代表智能卡目录。 |
The supplied path does not represent a smart card directory. |
| 0x80100026 | 提供的路径不代表智能卡文件。 |
The supplied path does not represent a smart card file. |
| 0x80100027 | 拒绝访问此文件。 |
Access is denied to this file. |
| 0x80100028 | 智能卡中没有足够内存，无法存储该信息。 |
The smart card does not have enough memory to store the information. |
| 0x80100029 | 在试图设置智能卡文件对象指针时出现错误。 |
There was an error trying to set the smart card file object pointer. |
| 0x8010002A | 提供的 PIN 不对。 |
The supplied PIN is incorrect. |
| 0x8010002B | 从分层组件返回了无法识别的错误代码。 |
An unrecognized error code was returned from a layered component. |
| 0x8010002C | 请求的证书不存在。 |
The requested certificate does not exist. |
| 0x8010002D | 不能获得请求的证书。 |
The requested certificate could not be obtained. |
| 0x8010002E | 找不到智能卡读卡器。 |
Cannot find a smart card reader. |
| 0x8010002F | 检测到智能卡有通讯错误。重试操作。 |
A communications error with the smart card has been detected. Retry the operation. |
| 0x80100030 | 智能卡中不存在请求的密钥容器。 |
The requested key container does not exist on the smart card. |
| 0x80100031 | 智能卡资源管理器太忙，无法完成此操作。 |
The Smart Card Resource Manager is too busy to complete this operation. |
| 0x80100032 | 智能卡 PIN 缓存已过期。 |
The smart card PIN cache has expired. |
| 0x80100033 | 无法缓存智能卡 PIN。 |
The smart card PIN cannot be cached. |
| 0x80100034 | 智能卡为只读，无法写入。 |
The smart card is read only and cannot be written to. |
| 0x80100065 | 由于 ATR 配置冲突，读卡器无法与智能卡通信。 |
The reader cannot communicate with the smart card, due to ATR configuration conflicts. |
| 0x80100066 | 智能卡没有响应重置。 |
The smart card is not responding to a reset. |
| 0x80100067 | 智能卡已无电源，所以不可能进一步通信。 |
Power has been removed from the smart card, so that further communication is not possible. |
| 0x80100068 | 智能卡已重置，因此任何共享的状态信息都无效。 |
The smart card has been reset, so any shared state information is invalid. |
| 0x80100069 | 智能卡已被移除，因此不可能进一步通信。 |
The smart card has been removed, so that further communication is not possible. |
| 0x8010006A | 由于违反了安全措施，访问遭到拒绝。 |
Access was denied because of a security violation. |
| 0x8010006B | 由于出现了错误的 PIN，无法访问卡。 |
The card cannot be accessed because the wrong PIN was presented. |
| 0x8010006C | 由于已经达到了 PIN 输入次数最大值，无法访问卡。 |
The card cannot be accessed because the maximum number of PIN entry attempts has been reached. |
| 0x8010006D | 已达到智能卡文件的结尾。 |
The end of the smart card file has been reached. |
| 0x8010006F | 没有向智能卡提供 PIN。 |
No PIN was presented to the smart card. |
| 0x80100070 | 无法在缓存中找到请求的项目。 |
The requested item could not be found in the cache. |
| 0x80100071 | 请求的缓存项目太旧，已从缓存中删除。 |
The requested cache item is too old and was deleted from the cache. |
| 0x80100072 | 新的缓存项目超过了为缓存定义的每个项目的大小上限。 |
The new cache item exceeds the maximum per-item size defined for the cache. |
| 0x80110401 | 访问一个或更多对象时，出现了错误 - ErrorInfo 集合有详细信息 |
Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail |
| 0x80110402 | 至少有一个对象属性找不到或无效 |
One or more of the object's properties are missing or invalid |
| 0x80110403 | 在目录中找不到对象 |
The object was not found in the catalog |
| 0x80110404 | 已注册对象 |
The object is already registered |
| 0x80110407 | 写入应用程序文件时，出现了错误 |
Error occurred writing to the application file |
| 0x80110408 | 读取应用程序文件时，出现了错误 |
Error occurred reading the application file |
| 0x80110409 | 应用程序文件中的版本编号无效 |
Invalid version number in application file |
| 0x8011040A | 文件路径无效 |
The file path is invalid |
| 0x8011040B | 已安装应用程序 |
The application is already installed |
| 0x8011040C | 角色已存在 |
The role already exists |
| 0x8011040D | 复制文件时，出现了一个错误 |
An error occurred copying the file |
| 0x8011040F | 至少有一个用户无效 |
One or more users are not valid |
| 0x80110410 | 应用程序文件中至少有一个用户无效 |
One or more users in the application file are not valid |
| 0x80110411 | 组件的 CLSID 找不到或已损坏 |
The component's CLSID is missing or corrupt |
| 0x80110412 | 组件的 progID 找不到或已损坏 |
The component's progID is missing or corrupt |
| 0x80110413 | 无法为更新请求设置所需的身份验证级别 |
Unable to set required authentication level for update request |
| 0x80110414 | 在应用程序中设定的标识或密码无效 |
The identity or password set on the application is not valid |
| 0x80110418 | 应用程序文件的 CLSID 和 IID 与相应的 DLL 不匹配 |
Application file CLSIDs or IIDs do not match corresponding DLLs |
| 0x80110419 | 接口信息找不到或已更改 |
Interface information is either missing or changed |
| 0x8011041A | DllRegisterServer 在安装组件时失败 |
DllRegisterServer failed on component install |
| 0x8011041B | 没有可以使用的服务器文件共享 |
No server file share available |
| 0x8011041D | 不能加载 DLL |
DLL could not be loaded |
| 0x8011041E | 注册的 TypeLib ID 无效 |
The registered TypeLib ID is not valid |
| 0x8011041F | 找不到应用程序安装目录 |
Application install directory not found |
| 0x80110423 | 在组件注册中出现了错误 |
Errors occurred while in the component registrar |
| 0x80110424 | 文件不存在 |
The file does not exist |
| 0x80110425 | 未能加载 DLL |
The DLL could not be loaded |
| 0x80110426 | GetClassObject 在 DLL 中失败 |
GetClassObject failed in the DLL |
| 0x80110427 | DLL 不支持列在 TypeLib 中的组件 |
The DLL does not support the components listed in the TypeLib |
| 0x80110428 | 无法加载 TypeLib |
The TypeLib could not be loaded |
| 0x80110429 | 文件中不包含组件或组件信息 |
The file does not contain components or component information |
| 0x8011042A | 已停用对这个对象及其子对象所作的更改 |
Changes to this object and its sub-objects have been disabled |
| 0x8011042B | 已为这个对象停用删除功能 |
The delete function has been disabled for this object |
| 0x8011042C | 服务器目录版本不受支持 |
The server catalog version is not supported |
| 0x8011042D | 由于源或目标应用程序是系统应用程序或目前不能作任何更改，不允许组件移动 |
The component move was disallowed, because the source or destination application is either a system application or currently locked against changes |
| 0x8011042E | 由于目标应用程序不再存在，组件移动失败 |
The component move failed because the destination application no longer exists |
| 0x80110430 | 系统无法注册 TypeLib |
The system was unable to register the TypeLib |
| 0x80110433 | 在系统应用程序上无法执行这个操作 |
This operation cannot be performed on the system application |
| 0x80110434 | 在这个文件中引用的组件注册者不可用 |
The component registrar referenced in this file is not available |
| 0x80110435 | 同一个 DLL 中的组件已安装 |
A component in the same DLL is already installed |
| 0x80110436 | 没有安装服务 |
The service is not installed |
| 0x80110437 | 至少有一个属性设置无效或互相冲突 |
One or more property settings are either invalid or in conflict with each other |
| 0x80110438 | 要添加或重命名的对象已经存在 |
The object you are attempting to add or rename already exists |
| 0x80110439 | 组件已存在 |
The component already exists |
| 0x8011043B | 注册文件已损坏 |
The registration file is corrupt |
| 0x8011043C | 属性值太大 |
The property value is too large |
| 0x8011043E | 在注册表中找不到对象 |
Object was not found in registry |
| 0x8011043F | 这个对象不能合并 |
This object is not poolable |
| 0x80110446 | 这台计算机上已安装有与新应用程序 ID 相同的 GUID 的 CLSID |
A CLSID with the same GUID as the new application ID is already installed on this machine |
| 0x80110447 | 分配给组件、接口或方法的角色不在应用程序中 |
A role assigned to a component, interface, or method did not exist in the application |
| 0x80110448 | 应用程序中必须有组件才能启动应用程序 |
You must have components in an application in order to start the application |
| 0x80110449 | 在这个平台上没有启用该操作 |
This operation is not enabled on this platform |
| 0x8011044A | 应用程序代理不可导出 |
Application Proxy is not exportable |
| 0x8011044B | 由于是库应用程序或应用程序代理，因此未能启动。 |
Failed to start application because it is either a library application or an application proxy |
| 0x8011044C | 系统应用程序不可导出 |
System application is not exportable |
| 0x8011044D | 无法订阅这个组件(组件可能已被导入) |
Cannot subscribe to this component (the component may have been imported) |
| 0x8011044E | 事件类不能同时也是订户组件 |
An event class cannot also be a subscriber component |
| 0x8011044F | 库应用程序和应用程序代理不兼容 |
Library applications and application proxies are incompatible |
| 0x80110450 | 此功能仅对基本分区有效 |
This function is valid for the base partition only |
| 0x80110451 | 你不能启动一个已禁用的应用程序 |
You cannot start an application that has been disabled |
| 0x80110457 | 指定的分区名已被用在这台计算机上 |
The specified partition name is already in use on this computer |
| 0x80110458 | 指定的分区名无效。请检查名称是否包含至少一个看得见的字符 |
The specified partition name is invalid. Check that the name contains at least one visible character |
| 0x80110459 | 因为是多个用户的默认分区，无法删除 |
The partition cannot be deleted because it is the default partition for one or more users |
| 0x8011045A | 因为分区中至少一个组件具有相同文件名，无法将分区导出 |
The partition cannot be exported, because one or more components in the partition have the same file name |
| 0x8011045B | 包含一个或多个导入组件的应用程序不能安装到非基本分区里 |
Applications that contain one or more imported components cannot be installed into a non-base partition |
| 0x8011045C | 应用程序名不是唯一的，因此不能解析为一个应用程序 id |
The application name is not unique and cannot be resolved to an application id |
| 0x8011045D | 分区名不是唯一的，因此不能解析为一个分区 id |
The partition name is not unique and cannot be resolved to a partition id |
| 0x80110472 | 尚未初始化 COM+ 注册表数据库 |
The COM+ registry database has not been initialized |
| 0x80110473 | COM+ 注册表数据库没有打开 |
The COM+ registry database is not open |
| 0x80110474 | COM+ 注册表数据库检测到一个系统错误 |
The COM+ registry database detected a system error |
| 0x80110475 | COM+ 注册表数据库已在运行 |
The COM+ registry database is already running |
| 0x80110480 | 不能迁移这个版本的 COM+ 注册表数据库 |
This version of the COM+ registry database cannot be migrated |
| 0x80110481 | 在 COM+ 注册表数据库中找不到要迁移的架构版本 |
The schema version to be migrated could not be found in the COM+ registry database |
| 0x80110482 | 二进制文件之间类型不匹配 |
There was a type mismatch between binaries |
| 0x80110483 | 提供的二进制文件类型不明或无效 |
A binary of unknown or invalid type was provided |
| 0x80110484 | 二进制文件和应用程序之间类型不匹配 |
There was a type mismatch between a binary and an application |
| 0x80110485 | 不能暂停或继续此应用程序 |
The application cannot be paused or resumed |
| 0x80110486 | 执行期间，COM+ 目录服务器出现一个例外 |
The COM+ Catalog Server threw an exception during execution |
| 0x80110600 | 只有标记为 \"queued\" 的 COM+ 应用程序才能用 \"queue\" 标记调用 |
Only COM+ Applications marked \"queued\" can be invoked using the \"queue\" moniker |
| 0x80110601 | 至少有一个接口必须标为 \"queued\"，才能用 \"queue\" 标记创建队列组件实例 |
At least one interface must be marked \"queued\" in order to create a queued component instance with the \"queue\" moniker |
| 0x80110602 | 请求的操作所需的 MSMQ 没有安装。 |
MSMQ is required for the requested operation and is not installed |
| 0x80110603 | 无法整理一个不支持 IPersistStream 的接口 |
Unable to marshal an interface that does not support IPersistStream |
| 0x80110604 | 该消息格式不对或者在中转时遭到破坏 |
The message is improperly formatted or was damaged in transit |
| 0x80110605 | 一个只接受经过验证的消息的应用程序收到一个未经验证的消息 |
An unauthenticated message was received by an application that accepts only authenticated messages |
| 0x80110606 | 一位不是“QC 信任用户”角色的用户重新排队或移动了此消息 |
The message was requeued or moved by a user not in the \"QC Trusted User\" role |
| 0x80110701 | 不能创建分布式事务协调器类型的双重资源 |
Cannot create a duplicate resource of type Distributed Transaction Coordinator |
| 0x80110808 | 正在被插入或更新的一个对象不属于有效的父集合 |
One of the objects being inserted or updated does not belong to a valid parent collection |
| 0x80110809 | 找不到一个指定的对象 |
One of the specified objects cannot be found |
| 0x8011080A | 指定的应用程序当前没有运行 |
The specified application is not currently running |
| 0x8011080B | 指定的分区无效。 |
The partition(s) specified are not valid. |
| 0x8011080D | 作为 NT 服务运行的 COM+ 应用程序不能被集区或回收 |
COM+ applications that run as NT service may not be pooled or recycled |
| 0x8011080E | 一位或多位用户已被分配到本地分区集。 |
One or more users are already assigned to a local partition set. |
| 0x8011080F | 不能回收库应用程序。 |
Library applications may not be recycled. |
| 0x80110811 | 不能回收以 NT 服务运行的应用程序。 |
Applications running as NT services may not be recycled. |
| 0x80110812 | 此进程已被回收。 |
The process has already been recycled. |
| 0x80110813 | 不能回收暂停的进程。 |
A paused process may not be recycled. |
| 0x80110814 | 库应用程序不能是 NT 服务。 |
Library applications may not be NT services. |
| 0x80110815 | 为复制操作所提供的 ProgID 无效。该 ProgID 已被另一注册了的 CLSID 所用。 |
The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID. |
| 0x80110816 | 被指定为默认的分区不是该分区集的成员。 |
The partition specified as default is not a member of the partition set. |
| 0x80110817 | 不能暂停回收进程。 |
A recycled process may not be paused. |
| 0x80110818 | 拒绝访问指定的分区。 |
Access to the specified partition is denied. |
| 0x80110819 | 只有应用程序文件(*.MSI 文件)可被安装到分区里。 |
Only Application Files (*.MSI files) can be installed into partitions. |
| 0x8011081A | 不可将含有一个或多个旧式组件的应用程序输出到 1.0 格式。 |
Applications containing one or more legacy components may not be exported to 1.0 format. |
| 0x8011081B | 旧式组件不可存在于非基本分区里。 |
Legacy components may not exist in non-base partitions. |
| 0x8011081C | 不能从系统应用程序、应用程序代理或不可更改的应用程序里移动 (或复制) 组件 |
A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application |
| 0x8011081D | 不能将组件移到(或复制到)系统应用程序、应用程序代理或不可更改的应用程序 |
A component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application |
| 0x8011081E | 不能将专用组件移到(或复制到)库应用程序或基本分区 |
A private component cannot be moved (or copied) to a library application or to the base partition |
| 0x8011081F | 基本应用程序分区在所有分区集里，而且不能删除。 |
The Base Application Partition exists in all partition sets and cannot be removed. |
| 0x80110820 | 哎呀，不能给事件类组件别名。 |
Alas, Event Class components cannot be aliased. |
| 0x80110821 | 因为组件是专用的，拒绝访问。 |
Access is denied because the component is private. |
| 0x80110822 | 指定的 SAFER 级别无效。 |
The specified SAFER level is invalid. |
| 0x80110823 | 指定的用户无法写入系统注册表 |
The specified user cannot write to the system registry |
| 0x80110824 | COM+ 分区当前禁用。 |
COM+ partitions are currently disabled. |
| 0x80190001 | 异常的 HTTP 状态代码。 |
Unexpected HTTP status code. |
| 0x80190003 | 异常的重定向状态代码(3xx)。 |
Unexpected redirection status code (3xx). |
| 0x80190004 | 异常的客户端错误状态代码(4xx)。 |
Unexpected client error status code (4xx). |
| 0x80190005 | 异常的服务器错误状态代码(5xx)。 |
Unexpected server error status code (5xx). |
| 0x8019012C | 多个选择(300)。 |
Multiple choices (300). |
| 0x8019012D | 永久移动(301)。 |
Moved permanently (301). |
| 0x8019012E | 找到(302)。 |
Found (302). |
| 0x8019012F | 查看其他(303)。 |
See Other (303). |
| 0x80190130 | 未修改(304)。 |
Not modified (304). |
| 0x80190131 | 使用代理(305)。 |
Use proxy (305). |
| 0x80190133 | 暂时重定向(307)。 |
Temporary redirect (307). |
| 0x80190190 | 错误的请求(400)。 |
Bad request (400). |
| 0x80190191 | 未授权(401)。 |
Unauthorized (401). |
| 0x80190192 | 需要付费(402)。 |
Payment required (402). |
| 0x80190193 | 已禁止(403)。 |
Forbidden (403). |
| 0x80190194 | 未找到(404)。 |
Not found (404). |
| 0x80190195 | 禁止使用方法(405)。 |
Method not allowed (405). |
| 0x80190196 | 不可接受(406)。 |
Not acceptable (406). |
| 0x80190197 | 需要代理身份验证(407)。 |
Proxy authentication required (407). |
| 0x80190198 | 请求超时(408)。 |
Request timeout (408). |
| 0x80190199 | 冲突(409)。 |
Conflict (409). |
| 0x8019019A | 不存在(410)。 |
Gone (410). |
| 0x8019019B | 需要提供长度(411)。 |
Length required (411). |
| 0x8019019C | 预处理失败(412)。 |
Precondition failed (412). |
| 0x8019019D | 请求实体过大(413)。 |
Request entity too large (413). |
| 0x8019019E | 请求 URI 过长(414)。 |
Request-URI too long (414). |
| 0x8019019F | 不支持的媒体类型(415)。 |
Unsupported media type (415). |
| 0x801901A0 | 无法满足请求的范围(416)。 |
Requested range not satisfiable (416). |
| 0x801901A1 | 预期失败(417)。 |
Expectation failed (417). |
| 0x801901F4 | 内部服务器错误(500)。 |
Internal server error (500). |
| 0x801901F5 | 尚未执行(501)。 |
Not implemented (501). |
| 0x801901F6 | 错误的网关(502)。 |
Bad gateway (502). |
| 0x801901F7 | 无法使用服务(503)。 |
Service unavailable (503). |
| 0x801901F8 | 网关超时(504)。 |
Gateway timeout (504). |
| 0x801901F9 | 版本不受支持(505)。 |
Version not supported (505). |
| 0x801B8000 | 崩溃报告失败。 |
Crash reporting failed. |
| 0x801B8001 | 由于用户取消而中止报告。 |
Report aborted due to user cancelation. |
| 0x801B8002 | 由于网络故障而中止报告。 |
Report aborted due to network failure. |
| 0x801B8003 | 未初始化报告。 |
Report not initialized. |
| 0x801B8004 | 已在为指定的进程运行报告。 |
Reporting is already in progress for the specified process. |
| 0x801B8005 | 由于限制，未生成转储。 |
Dump not generated due to a throttle. |
| 0x801B8006 | 由于未获得用户的充分同意，操作失败。 |
Operation failed due to insufficient user consent. |
| 0x801B8007 | 报告因性能标准而中止。 |
Report aborted due to performance criteria. |
| 0x801F0001 | 筛选器未定义此操作的处理程序。 |
A handler was not defined by the filter for this operation. |
| 0x801F0002 | 已定义此对象的上下文。 |
A context is already defined for this object. |
| 0x801F0003 | 异步请求对此操作无效。 |
Asynchronous requests are not valid for this operation. |
| 0x801F0004 | 不允许此操作的快速 IO 路径。 |
Disallow the Fast IO path for this operation. |
| 0x801F0005 | 执行的名称请求无效。此时无法检索请求的名称。 |
An invalid name request was made. The name requested cannot be retrieved at this time. |
| 0x801F0006 | 此时将此操作发送到工作线程进行进一步处理是不安全的，因为这样会导致系统死锁。 |
Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. |
| 0x801F0007 | 尝试注册筛选器时，筛选器管理器未初始化。请确保将筛选器管理器加载为驱动程序。 |
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. |
| 0x801F0008 | 筛选器尚未准备好附加到卷，因为筛选器还未完成初始化(尚未调用 FltStartFiltering)。 |
The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). |
| 0x801F0009 | 此时筛选器必须清理所有操作特定的上下文，因为从系统中删除其上下文之后，低级驱动程序才能完成此操作。 |
The 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. |
| 0x801F000A | 筛选器管理器发生无法恢复的内部错误，因此该操作失败。这通常是因为筛选器从预操作回调中返回了无效的值。 |
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. |
| 0x801F000B | 正在删除为此操作指定的对象，因此此时无法完成请求的操作。 |
The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. |
| 0x801F000C | 必须对此类型的上下文使用非分页缓冲池。 |
Non-paged pool must be used for this type of context. |
| 0x801F000D | 为操作提供了重复的处理程序定义。 |
A duplicate handler definition has been provided for an operation. |
| 0x801F000E | 回调数据队列已禁用。 |
The callback data queue has been disabled. |
| 0x801F000F | 此时不要将筛选器附加到卷。 |
Do not attach the filter to the volume at this time. |
| 0x801F0010 | 此时不要从卷分离筛选器。 |
Do not detach the filter from the volume at this time. |
| 0x801F0011 | 在指定卷的此高度上已存在实例。 |
An instance already exists at this altitude on the volume specified. |
| 0x801F0012 | 在指定卷上已存在此名称的实例。 |
An instance already exists with this name on the volume specified. |
| 0x801F0013 | 系统无法找到指定的筛选器。 |
The system could not find the filter specified. |
| 0x801F0014 | 系统无法找到指定的卷。 |
The system could not find the volume specified. |
| 0x801F0015 | 系统无法找到指定的实例。 |
The system could not find the instance specified. |
| 0x801F0016 | 找不到为给定请求注册的上下文分配定义。 |
No registered context allocation definition was found for the given request. |
| 0x801F0017 | 注册上下文期间指定了无效的参数。 |
An invalid parameter was specified during context registration. |
| 0x801F0018 | 在筛选器管理器的名称缓存中找不到请求的名称，无法从文件系统中检索。 |
The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
| 0x801F0019 | 给定的卷中不存在请求的设备对象。 |
The requested device object does not exist for the given volume. |
| 0x801F001A | 已装载指定的卷。 |
The specified volume is already mounted. |
| 0x801F001B | 指定的事务上下文已在事务中登记 |
The specified Transaction Context is already enlisted in a transaction |
| 0x801F001C | 特定上下文已附加到另一对象 |
The specifiec context is already attached to another object |
| 0x801F0020 | 不存在等候筛选器回复此消息的程序。 |
No waiter is present for the filter's reply to this message. |
| 0x801F0023 | 文件系统数据库资源正在使用中。目前无法完成注册。 |
The filesystem database resource is in use. Registration cannot complete at this time. |
| 0x80260001 | {显示驱动程序停止响应}%hs 显示驱动程序已经正常停止工作。请保存你的工作并重新启动系统以还原完整的显示功能。下一次你重新启动计算机时，将显示对话框以让你有机会向 Microsoft 报告此故障。 |
{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. |
| 0x80263001 | {已禁用桌面合成}操作无法完成，因为已禁用桌面合成。 |
{Desktop composition is disabled}The operation could not be completed because desktop composition is disabled. |
| 0x80263002 | {执行远程操作时不支持某些桌面合成 API}在远程会话中运行时，不支持此操作。 |
{Some desktop composition APIs are not supported while remoting}The operation is not supported while running in a remote session. |
| 0x80263003 | {没有可用的 DWM 重定向表面}DWM 无法提供重定向表面来完成 DirectX 显示。 |
{No DWM redirection surface is available}The DWM was unable to provide a redireciton surface to complete the DirectX present. |
| 0x80263004 | {DWM 没有为指定的窗口排队显示}指定的窗口当前未使用排队显示。 |
{DWM is not queuing presents for the specified window}The window specified is not currently using queued presents. |
| 0x80263005 | {找不到由 LUID 指定的适配器}DWM 找不到由 LUID 指定的适配器。 |
{The adapter specified by the LUID is not found}DWM can not find the adapter specified by the LUID. |
| 0x80263007 | {无法创建重定向表面。表面的大小大于此计算机所支持的大小}无法创建重定向表面。表面的大小大于此计算机所支持的大小。 |
{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. |
| 0x80270001 | NAP SoH 数据包无效。 |
The NAP SoH packet is invalid. |
| 0x80270002 | NAP 数据包中的 SoH 丢失。 |
An SoH was missing from the NAP packet. |
| 0x80270003 | 实体 ID 与已注册的 ID 冲突。 |
The entity ID conflicts with an already registered id. |
| 0x80270004 | 不存在缓存的 SoH。 |
No cached SoH is present. |
| 0x80270005 | 实体仍然绑定到 NAP 系统。 |
The entity is still bound to the NAP system. |
| 0x80270006 | NAP 系统未注册该实体。 |
The entity is not registered with the NAP system. |
| 0x80270007 | NAP 系统未初始化该实体。 |
The entity is not initialized with the NAP system. |
| 0x80270008 | SoH-Request 和 SoH-Response 中的相关 ID 不匹配。 |
The correlation id in the SoH-Request and SoH-Response do not match up. |
| 0x80270009 | 当前未挂起的请求指示操作已完成。 |
Completion was indicated on a request that is not currently pending. |
| 0x8027000A | 未找到 NAP 组件的 ID。 |
The NAP component's id was not found. |
| 0x8027000B | 最大连接大小对于 SoH 数据包而言过小。 |
The maximum size of the connection is too small for an SoH packet. |
| 0x8027000C | NapAgent 服务未运行。 |
The NapAgent service is not running. |
| 0x8027000E | NapAgent 服务已禁用该实体。 |
The entity is disabled with the NapAgent service. |
| 0x8027000F | 未配置组策略。 |
Group Policy is not configured. |
| 0x80270010 | 同时执行的调用过多。 |
Too many simultaneous calls. |
| 0x80270011 | SHV 配置已存在。 |
SHV configuration already existed. |
| 0x80270012 | 未找到 SHV 配置。 |
SHV configuration is not found. |
| 0x80270013 | 请求的 SHV 超时。 |
SHV timed out on the request. |
| 0x80270220 | 已达到访问列表的最大项目数。必须先删除一个项目，然后才能添加其他项目。 |
The maximum number of items for the access list has been reached. An item must be removed before another item is added. |
| 0x80270222 | 无法访问家庭组。家庭组可能未设置或遇到错误。 |
Cannot access Homegroup. Homegroup may not be set up or may have encountered an error. |
| 0x80270250 | 无法启动此应用，因为屏幕分辨率低于 1024x768。请选择较高的屏幕分辨率，然后重试。 |
This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again. |
| 0x80270251 | 无法从提升的上下文中激活此应用。 |
This app can't be activated from an elevated context. |
| 0x80270252 | 在禁用 UAC 时，无法激活此应用。 |
This app can't be activated when UAC is disabled. |
| 0x80270253 | 内置管理员无法激活此应用。 |
This app can't be activated by the Built-in Administrator. |
| 0x80270254 | 此应用不支持指定的合约或未安装该应用。 |
This app does not support the contract specified or is not installed. |
| 0x80270255 | 此应用注册了多个扩展以支持指定的合约。通过 AppUserModelId 执行的激活为不确定的操作。 |
This app has mulitple extensions registered to support the specified contract. Activation by AppUserModelId is ambiguous. |
| 0x80270256 | 此应用的程序包系列安装了多个程序包。不支持此操作。 |
This app's package family has more than one package installed. This is not supported. |
| 0x80270257 | 需要使用应用管理器激活应用程序，但该管理器未运行。 |
The app manager is required to activate applications, but is not running. |
| 0x8027025A | 应用未在所需的时间内启动。 |
The app didn't start in the required time. |
| 0x8027025B | 应用未启动。 |
The app didn't start. |
| 0x8027025C | 此应用无法启动，因为它的许可证出现问题。请稍后重试。 |
This app failed to launch because of an issue with its license. Please try again in a moment. |
| 0x8027025D | 此应用无法启动，因为其试用许可证已过期。 |
This app failed to launch because its trial license has expired. |
| 0x80270260 | 请选择已使用 NTFS 文件系统格式化的驱动器上的文件夹。 |
Please choose a folder on a drive that's formatted with the NTFS file system. |
| 0x80270261 | 已使用此位置。请选择一个不同的位置。 |
This location is already being used. Please choose a different location. |
| 0x80270262 | 无法为此位置编制索引。请选择一个不同的位置。 |
This location cannot be indexed. Please choose a different location. |
| 0x80270263 | 抱歉，无法完成该操作，因为文件尚未完成上载。请稍后重试。 |
Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later. |
| 0x80270264 | 抱歉，无法完成该操作。 |
Sorry, the action couldn't be completed. |
| 0x80270265 | 此内容只能移至文件夹中。若要将内容移至此驱动器上，请选择或创建文件夹。 |
This content can only be moved to a folder. To move the content to this drive, please choose or create a folder. |
| 0x80280000 | 这是一种将 TPM 硬件错误转换为 Windows 错误的错误掩码。 |
This is an error mask to convert TPM hardware errors to win errors. |
| 0x80280001 | 身份验证失败。 |
Authentication failed. |
| 0x80280002 | 对 PCR、DIR 或其他注册项的索引不正确。 |
The index to a PCR, DIR or other register is incorrect. |
| 0x80280003 | 一个或多个参数不正确。 |
One or more parameter is bad. |
| 0x80280004 | 操作成功完成，但是此操作的审核失败。 |
An operation completed successfully but the auditing of that operation failed. |
| 0x80280005 | 已设置清除禁用的标志，现在所有清除操作都要求物理访问。 |
The clear disable flag is set and all clear operations now require physical access. |
| 0x80280006 | 激活受信任的平台模块(TPM)。 |
Activate the Trusted Platform Module (TPM). |
| 0x80280007 | 启用受信任的平台模块(TPM)。 |
Enable the Trusted Platform Module (TPM). |
| 0x80280008 | 目标命令已经禁用。 |
The target command has been disabled. |
| 0x80280009 | 操作失败。 |
The operation failed. |
| 0x8028000A | 序数未知或不一致。 |
The ordinal was unknown or inconsistent. |
| 0x8028000B | 安装所有者的功能被禁用。 |
The ability to install an owner is disabled. |
| 0x8028000C | 无法解释密钥句柄。 |
The key handle cannot be interpreted. |
| 0x8028000D | 密钥句柄指向无效的密钥。 |
The key handle points to an invalid key. |
| 0x8028000E | 不可接受的加密方案。 |
Unacceptable encryption scheme. |
| 0x8028000F | 迁移授权失败。 |
Migration authorization failed. |
| 0x80280010 | 无法解释 PCR 信息。 |
PCR information could not be interpreted. |
| 0x80280011 | 没有空间加载密钥。 |
No room to load key. |
| 0x80280012 | 没有存储根密钥(SRK)集。 |
There is no Storage Root Key (SRK) set. |
| 0x80280013 | 加密的 blob 无效或不是由此 TPM 创建的。 |
An encrypted blob is invalid or was not created by this TPM. |
| 0x80280014 | 受信任的平台模块(TPM)已存在一个所有者。 |
The Trusted Platform Module (TPM) already has an owner. |
| 0x80280015 | TPM 内部资源不足，无法执行请求的操作。 |
The TPM has insufficient internal resources to perform the requested action. |
| 0x80280016 | 随机字符串过短。 |
A random string was too short. |
| 0x80280017 | TPM 没有执行该操作的空间。 |
The TPM does not have the space to perform the operation. |
| 0x80280018 | 命名的 PCR 值与当前的 PCR 值不匹配。 |
The named PCR value does not match the current PCR value. |
| 0x80280019 | 此命令的 paramSize 参数包含不正确的值。 |
The paramSize argument to the command has the incorrect value . |
| 0x8028001A | 不存在现有的 SHA-1 线程。 |
There is no existing SHA-1 thread. |
| 0x8028001B | 计算无法进行，因为现有的 SHA-1 线程已遇到错误。 |
The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. |
| 0x8028001C | TPM 硬件设备在其内部自测期间报告了一个错误。尝试重新启动计算机以解决该问题。如果问题仍然存在，请检查是否存在针对你的 TPM 硬件的最新 BIOS 或固件更新。请参考计算机制造商的文档获取说明。 |
The 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. |
| 0x8028001D | 为 2 密钥函数中的第二个密钥授权失败。 |
The authorization for the second key in a 2 key function failed authorization. |
| 0x8028001E | 为命令发送的标记值无效。 |
The tag value sent to for a command is invalid. |
| 0x8028001F | 向 TPM 传输信息时发生 IO 错误。 |
An IO error occurred transmitting information to the TPM. |
| 0x80280020 | 加密过程存在问题。 |
The encryption process had a problem. |
| 0x80280021 | 加密过程没有完成。 |
The decryption process did not complete. |
| 0x80280022 | 使用了无效句柄。 |
An invalid handle was used. |
| 0x80280023 | TPM 未安装认可密钥(EK)。 |
The TPM does not have an Endorsement Key (EK) installed. |
| 0x80280024 | 不允许使用密钥。 |
The usage of a key is not allowed. |
| 0x80280025 | 不允许已提交的实体类型。 |
The submitted entity type is not allowed. |
| 0x80280026 | 相对于 TPM_Init 和后续的 TPM_Startup 而言，命令的接收顺序错误。 |
The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup. |
| 0x80280027 | 签名的数据不能包含其他 DER 信息。 |
Signed data cannot include additional DER information. |
| 0x80280028 | TPM_KEY_PARM 中的密钥属性不受此 TPM 支持。 |
The key properties in TPM_KEY_PARMs are not supported by this TPM. |
| 0x80280029 | 此密钥的迁移属性不正确。 |
The migration properties of this key are incorrect. |
| 0x8028002A | 此密钥的签名或加密方案不正确或在这种情况下不允许。 |
The signature or encryption scheme for this key is incorrect or not permitted in this situation. |
| 0x8028002B | 数据(或 blob)参数的大小不正确或与引用的密钥不一致。 |
The size of the data (or blob) parameter is bad or inconsistent with the referenced key. |
| 0x8028002C | 模式参数不正确，如 TPM_GetCapability 的 capArea 或 subCapArea，PM_PhysicalPresence 的 phsicalPresence 参数，或者 TPM_CreateMigrationBlob 的 migrationType 参数。 |
A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob. |
| 0x8028002D | physicalPresence 位或 physicalPresenceLock 位的值错误。 |
Either the physicalPresence or physicalPresenceLock bits have the wrong value. |
| 0x8028002E | TPM 无法执行此版本的功能。 |
The TPM cannot perform this version of the capability. |
| 0x8028002F | TPM 不允许换行的传输会话。 |
The TPM does not allow for wrapped transport sessions. |
| 0x80280030 | TPM 审核构造失败，基础命令也返回故障代码。 |
TPM audit construction failed and the underlying command was returning a failure code also. |
| 0x80280031 | TPM 审核构造失败，但基础命令返回成功。 |
TPM audit construction failed and the underlying command was returning success. |
| 0x80280032 | 试图重置不具有可重置属性的 PCR 注册项。 |
Attempt to reset a PCR register that does not have the resettable attribute. |
| 0x80280033 | 试图重置的 PCR 注册项要求有区域且区域修饰符不是命令传输的一部分。 |
Attempt to reset a PCR register that requires locality and locality modifier not part of command transport. |
| 0x80280034 | 使标识 blob 未正确键入。 |
Make identity blob not properly typed. |
| 0x80280035 | 保存上下文时，已标识的资源类型与实际资源不匹配。 |
When saving context identified resource type does not match actual resource. |
| 0x80280036 | TPM 试图执行仅在 FIPS 模式中可用的命令。 |
The TPM is attempting to execute a command only available when in FIPS mode. |
| 0x80280037 | 此命令试图使用无效的系列 ID。 |
The command is attempting to use an invalid family ID. |
| 0x80280038 | 操作 NV 存储器的权限不可用。 |
The permission to manipulate the NV storage is not available. |
| 0x80280039 | 此操作需要签名的命令。 |
The operation requires a signed command. |
| 0x8028003A | 加载 NV 密钥的操作错误。 |
Wrong operation to load an NV key. |
| 0x8028003B | NV_LoadKey blob 需要所有者和 blob 授权。 |
NV_LoadKey blob requires both owner and blob authorization. |
| 0x8028003C | NV 区域已锁定，无法写入。 |
The NV area is locked and not writtable. |
| 0x8028003D | 此区域不适合尝试的操作。 |
The locality is incorrect for the attempted operation. |
| 0x8028003E | NV 区域是只读的，无法写入。 |
The NV area is read only and can't be written to. |
| 0x8028003F | 没有对 NV 区域进行写保护。 |
There is no protection on the write to the NV area. |
| 0x80280040 | 系列计数值不匹配。 |
The family count value does not match. |
| 0x80280041 | 已写入 NV 区域。 |
The NV area has already been written to. |
| 0x80280042 | NV 区域属性冲突。 |
The NV area attributes conflict. |
| 0x80280043 | 结构标记和版本无效或不一致。 |
The structure tag and version are invalid or inconsistent. |
| 0x80280044 | 此密钥受 TPM 所有者控制，只能由 TPM 所有者收回。 |
The key is under control of the TPM Owner and can only be evicted by the TPM Owner. |
| 0x80280045 | 计数器句柄不正确。 |
The counter handle is incorrect. |
| 0x80280046 | 此写入不是该区域的完全写入。 |
The write is not a complete write of the area. |
| 0x80280047 | 已保存上下文计数之间的跨度过大。 |
The gap between saved context counts is too large. |
| 0x80280048 | 已超出没有所有者的 NV 写入的最大数目。 |
The maximum number of NV writes without an owner has been exceeded. |
| 0x80280049 | 未设置操作者 AuthData 值。 |
No operator AuthData value is set. |
| 0x8028004A | 未加载上下文指向的资源。 |
The resource pointed to by context is not loaded. |
| 0x8028004B | 委派的管理员已锁定。 |
The delegate administration is locked. |
| 0x8028004C | 试图管理委派系列之外的系列。 |
Attempt to manage a family other then the delegated family. |
| 0x8028004D | 未启用委派表管理。 |
Delegation table management not enabled. |
| 0x8028004E | 存在一个在独占传输会话之外执行的命令。 |
There was a command executed outside of an exclusive transport session. |
| 0x8028004F | 试图使上下文保存不受所有者收回控制的密钥。 |
Attempt to context save a owner evict controlled key. |
| 0x80280050 | DAA 命令没有可用的资源来执行此命令。 |
The DAA command has no resources availble to execute the command. |
| 0x80280051 | 对 DAA 参数 inputData0 的一致性检查失败。 |
The consistency check on DAA parameter inputData0 has failed. |
| 0x80280052 | 对 DAA 参数 inputData1 的一致性检查失败。 |
The consistency check on DAA parameter inputData1 has failed. |
| 0x80280053 | 对 DAA_issuerSettings 的一致性检查失败。 |
The consistency check on DAA_issuerSettings has failed. |
| 0x80280054 | 对 DAA_tpmSpecific 的一致性检查失败。 |
The consistency check on DAA_tpmSpecific has failed. |
| 0x80280055 | 已提交的 DAA 命令指示的原子过程不是预期的过程。 |
The atomic process indicated by the submitted DAA command is not the expected process. |
| 0x80280056 | 颁发者的有效性检查已检测到不一致。 |
The issuer's validity check has detected an inconsistency. |
| 0x80280057 | 对 w 的一致性检查已失败。 |
The consistency check on w has failed. |
| 0x80280058 | 句柄错误。 |
The handle is incorrect. |
| 0x80280059 | 委派错误。 |
Delegation is not correct. |
| 0x8028005A | 上下文 blob 无效。 |
The context blob is invalid. |
| 0x8028005B | TPM 包含的上下文过多。 |
Too many contexts held by the TPM. |
| 0x8028005C | 迁移授权签名验证失败。 |
Migration authority signature validation failure. |
| 0x8028005D | 迁移目标尚未进行身份验证。 |
Migration destination not authenticated. |
| 0x8028005E | 迁移源错误。 |
Migration source incorrect. |
| 0x8028005F | 迁移授权不正确。 |
Incorrect migration authority. |
| 0x80280061 | 试图吊销 EK，但 EK 是不可吊销的。 |
Attempt to revoke the EK and the EK is not revocable. |
| 0x80280062 | CMK 票证签名不正确。 |
Bad signature of CMK ticket. |
| 0x80280063 | 上下文列表中没有用于其他上下文的空间。 |
There is no room in the context list for additional contexts. |
| 0x80280400 | 命令被阻止。 |
The command was blocked. |
| 0x80280401 | 找不到指定句柄。 |
The specified handle was not found. |
| 0x80280402 | TPM 返回重复的句柄，需要重新提交此命令。 |
The TPM returned a duplicate handle and the command needs to be resubmitted. |
| 0x80280403 | 传输中的命令被阻止。 |
The command within the transport was blocked. |
| 0x80280404 | 传输中的命令不受支持。 |
The command within the transport is not supported. |
| 0x80280800 | TPM 忙碌，无法立即响应此命令，但是稍后会重新提交此命令。 |
The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time. |
| 0x80280801 | SelfTestFull 尚未运行。 |
SelfTestFull has not been run. |
| 0x80280802 | TPM 当前正在执行全面自测。 |
The TPM is currently executing a full selftest. |
| 0x80280803 | TPM 正在定义防止字典攻击，且处于超时期限。 |
The TPM is defending against dictionary attacks and is in a time-out period. |
| 0x80284001 | 受信任的平台模块支持程序中出现内部错误。 |
An internal error has occurred within the Trusted Platform Module support program. |
| 0x80284002 | 一个或多个输入参数不正确。 |
One or more input parameters is bad. |
| 0x80284003 | 指定的输出指针不正确。 |
A specified output pointer is bad. |
| 0x80284004 | 指定的上下文句柄引用的上下文无效。 |
The specified context handle does not refer to a valid context. |
| 0x80284005 | 指定的输出缓冲区过小。 |
A specified output buffer is too small. |
| 0x80284006 | 与 TPM 通讯时发生错误。 |
An error occurred while communicating with the TPM. |
| 0x80284007 | 一个或多个上下文参数无效。 |
One or more context parameters is invalid. |
| 0x80284008 | TBS 服务未运行，且无法启动。 |
The TBS service is not running and could not be started. |
| 0x80284009 | 无法创建新的上下文，因为打开的上下文过多。 |
A new context could not be created because there are too many open contexts. |
| 0x8028400A | 无法创建新的虚拟资源，因为打开的虚拟资源太多。 |
A new virtual resource could not be created because there are too many open virtual resources. |
| 0x8028400B | TBS 服务已启动，但尚未运行。 |
The TBS service has been started but is not yet running. |
| 0x8028400C | 不支持物理存在接口。 |
The physical presence interface is not supported. |
| 0x8028400D | 命令已取消。 |
The command was canceled. |
| 0x8028400E | 输入或输出缓冲区过大。 |
The input or output buffer is too large. |
| 0x8028400F | 这台计算机上找不到兼容的受信任的平台模块(TPM)安全设备。 |
A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer. |
| 0x80284010 | TBS 服务已经被禁用。 |
The TBS service has been disabled. |
| 0x80284011 | 没有可用的 TCG 事件日志。 |
No TCG event log is available. |
| 0x80284012 | 调用方没有相应的权限来执行请求的操作。 |
The caller does not have the appropriate rights to perform the requested operation. |
| 0x80284013 | 指定的标志不允许进行 TPM 预配操作。要成功完成预配，可能需要完成若干操作之一。使 TPM 就绪的 TPM 管理控制台 (tpm.msc) 操作可能有所帮助。有关详细信息，请参阅有关 Win32_Tpm WMI 方法“预配”的文档。(可能需要的操作包括将 TPM 所有者授权值导入系统中，调用用于预配 TPM 以及为“ForceClear_Allowed”或“PhysicalPresencePrompts_Allowed”指定 TRUE (如附加信息中的返回值所指示的)的 Win32_Tpm WMI 方法，或在系统 BIOS 中启用 TPM。) |
The 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.) |
| 0x80284014 | 此固件的物理存在接口不支持请求的方法。 |
The Physical Presence Interface of this firmware does not support the requested method. |
| 0x80284015 | 找不到请求的 TPM OwnerAuth 值。 |
The requested TPM OwnerAuth value was not found. |
| 0x80284016 | TPM 预配未完成。有关完成预配的详细信息，请调用用于预配 TPM (“预配”) 的 Win32_Tpm WMI 方法并查看返回的信息。 |
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. |
| 0x80290100 | 命令缓冲区的状态不正确。 |
The command buffer is not in the correct state. |
| 0x80290101 | 命令缓冲区包含的数据不足，无法满足请求。 |
The command buffer does not contain enough data to satisfy the request. |
| 0x80290102 | 命令缓冲区无法包含任何更多的数据。 |
The command buffer cannot contain any more data. |
| 0x80290103 | 一个或多个输出参数为 NULL 或无效。 |
One or more output parameters was NULL or invalid. |
| 0x80290104 | 一个或多个输入参数无效。 |
One or more input parameters is invalid. |
| 0x80290105 | 可用的内存不足，无法满足请求。 |
Not enough memory was available to satisfy the request. |
| 0x80290106 | 指定的缓冲区太小。 |
The specified buffer was too small. |
| 0x80290107 | 检测到一个内部错误。 |
An internal error was detected. |
| 0x80290109 | 指定的授权信息无效。 |
The specified authorization information was invalid. |
| 0x8029010A | 指定的上下文句柄无效。 |
The specified context handle was not valid. |
| 0x8029010B | 与 TBS 通讯时发生错误。 |
An error occurred while communicating with the TBS. |
| 0x8029010C | TPM 返回一个意外的结果。 |
The TPM returned an unexpected result. |
| 0x8029010D | 编码方案的消息过大。 |
The message was too large for the encoding scheme. |
| 0x8029010E | 无法识别 blob 中的编码。 |
The encoding in the blob was not recognized. |
| 0x8029010F | 密钥大小无效。 |
The key size is not valid. |
| 0x80290110 | 加密操作失败。 |
The encryption operation failed. |
| 0x80290111 | 密钥参数结构无效。 |
The key parameters structure was not valid |
| 0x80290112 | 请求提供的数据似乎不是有效的迁移授权 blob。 |
The requested supplied data does not appear to be a valid migration authorization blob. |
| 0x80290113 | 指定的 PCR 索引无效。 |
The specified PCR index was invalid |
| 0x80290114 | 给定的数据看起来不是有效的委派 blob。 |
The data given does not appear to be a valid delegate blob. |
| 0x80290115 | 一个或多个指定的上下文参数无效。 |
One or more of the specified context parameters was not valid. |
| 0x80290116 | 给定的数据看起来不是有效的密钥 blob。 |
The data given does not appear to be a valid key blob |
| 0x80290117 | 指定的 PCR 数据无效。 |
The specified PCR data was invalid. |
| 0x80290118 | 所有者授权数据的格式无效。 |
The format of the owner auth data was invalid. |
| 0x80290119 | 随机生成的号码未通过 FIPS RNG 检查。 |
The random number generated did not pass FIPS RNG check. |
| 0x8029011A | TCG 事件日志不包含任何数据。 |
The TCG Event Log does not contain any data. |
| 0x8029011B | TCG 事件日志中的某个条目无效。 |
An entry in the TCG Event Log was invalid. |
| 0x8029011C | 找不到 TCG 分页器。 |
A TCG Separator was not found. |
| 0x8029011D | TCG 日志条目中的一个摘要值与哈希数据不匹配。 |
A digest value in a TCG Log entry did not match hashed data. |
| 0x8029011E | 当前的 TPM 策略阻止了请求的操作。请联系你的系统管理员以获得帮助。 |
The requested operation was blocked by current TPM policy. Please contact your system administrator for assistance. |
| 0x80290201 | 无法清理上下文。 |
The context could not be cleaned up. |
| 0x80290203 | 指定的上下文参数无效。 |
An invalid context parameter was specified. |
| 0x80290205 | 指定的密钥中找不到任何项。 |
No entry with the specified key was found. |
| 0x80290206 | 指定的虚拟句柄与正在使用的虚拟句柄匹配。 |
The specified virtual handle matches a virtual handle already in use. |
| 0x80290207 | 指向返回句柄位置的指针为 NULL 或无效。 |
The pointer to the returned handle location was NULL or invalid |
| 0x80290208 | 一个或多个参数无效。 |
One or more parameters is invalid |
| 0x80290209 | 无法对 RPC 子系统进行初始化。 |
The RPC subsystem could not be initialized. |
| 0x8029020A | TBS 计划程序未运行。 |
The TBS scheduler is not running. |
| 0x8029020C | 内存不足，无法完成请求。 |
There was not enough memory to fulfill the request |
| 0x8029020D | 指定的列表为空，或迭代已到达列表的末尾。 |
The specified list is empty, or the iteration has reached the end of the list. |
| 0x8029020E | 在列表中找不到指定的项。 |
The specified item was not found in the list. |
| 0x8029020F | TPM 空间不足，无法加载请求的资源。 |
The TPM does not have enough space to load the requested resource. |
| 0x80290210 | 正在使用的 TPM 上下文过多。 |
There are too many TPM contexts in use. |
| 0x80290211 | TPM 命令失败。 |
The TPM command failed. |
| 0x80290212 | TBS 不识别指定的序号。 |
The TBS does not recognize the specified ordinal. |
| 0x80290213 | 请求的资源不再可用。 |
The requested resource is no longer available. |
| 0x80290214 | 资源类型不匹配。 |
The resource type did not match. |
| 0x80290215 | 无法卸载任何资源。 |
No resources can be unloaded. |
| 0x80290216 | 无法向哈希表中添加任何新项。 |
No new entries can be added to the hash table. |
| 0x80290217 | 无法创建新的 TBS 上下文，因为打开的上下文太多。 |
A new TBS context could not be created because there are too many open contexts. |
| 0x8029021A | TBS 与系统中找到的 TPM 版本不兼容。 |
TBS is not compatible with the version of TPM found on the system. |
| 0x80290300 | 试图获取 BIOS 对 Physical Presence 命令的响应时，检测到一个常规错误。 |
A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command. |
| 0x80290301 | 用户无法确认 TPM 操作请求。 |
The user failed to confirm the TPM operation request. |
| 0x80290302 | BIOS 故障阻止了所请求 TPM 操作(例如，无效的 TPM 操作请求、BIOS 与TPM 的通信错误)的成功执行。 |
The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM). |
| 0x80290303 | BIOS 不支持物理存在接口。 |
The BIOS does not support the physical presence interface. |
| 0x80290304 | 当前 BIOS 设置阻止了物理存在命令。系统所有者需要重新配置 BIOS 设置来启用该命令。 |
The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command. |
| 0x80290400 | 这是一种将平台加密提供程序错误转换为 Windows 错误的错误掩码。 |
This is an error mask to convert Platform Crypto Provider errors to win errors. |
| 0x80290401 | 平台加密设备当前未就绪。它需要进行完全预配才能运行。 |
The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational. |
| 0x80290402 | 提供给平台加密提供程序的句柄无效。 |
The handle provided to the Platform Crypto Provider is invalid. |
| 0x80290403 | 提供给平台加密提供程序的参数无效。 |
A parameter provided to the Platform Crypto Provider is invalid. |
| 0x80290404 | 为平台加密提供程序提供的标志不受支持。 |
A provided flag to the Platform Crypto Provider is not supported. |
| 0x80290405 | 此平台加密提供程序不支持请求的操作。 |
The requested operation is not supported by this Platform Crypto Provider. |
| 0x80290406 | 缓冲区过小，无法包含所有数据。没有信息写入到缓冲区。 |
The buffer is too small to contain all data. No information has been written to the buffer. |
| 0x80290407 | 在平台加密提供程序中发生了意外的内部错误。 |
An unexpected internal error has occurred in the Platform Crypto Provider. |
| 0x80290408 | 授权使用提供程序对象失败。 |
The authorization to use a provider object has failed. |
| 0x80290409 | 平台加密设备已经忽略了对提供程序对象的授权，以减少字典式攻击。 |
The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack. |
| 0x8029040A | 找不到引用的策略。 |
The referenced policy was not found. |
| 0x8029040B | 找不到引用的配置文件。 |
The referenced profile was not found. |
| 0x8029040C | 验证不成功。 |
The validation was not succesful. |
| 0x8029040E | 试图将某个键导入或加载到不正确的存储父项下。 |
An attempt was made to import or load a key under an incorrect storage parent. |
| 0x8029040F | 该 TPM 密钥未加载。 |
The TPM key is not loaded. |
| 0x80290410 | 该 TPM 密钥证书尚未生成。 |
The TPM key certification has not been generated. |
| 0x80290411 | 该 TPM 密钥尚未完成。 |
The TPM key is not yet finalized. |
| 0x80290412 | 未设置 TPM 证明质询。 |
The TPM attestation challenge is not set. |
| 0x80290413 | TPM PCR 服务信息不可用。 |
The TPM PCR info is not available. |
| 0x80290414 | 该 TPM 密钥已完成。 |
The TPM key is already finalized. |
| 0x80290415 | 不支持该 TPM 密钥使用策略。 |
The TPM key usage policy is not supported. |
| 0x80290416 | 该 TPM 密钥使用策略无效。 |
The TPM key usage policy is invalid. |
| 0x80290417 | 要导入到 TPM 的软件密钥有问题。 |
There was a problem with the software key being imported into the TPM. |
| 0x80290418 | 该 TPM 密钥未进行身份验证。 |
The TPM key is not authenticated. |
| 0x80290419 | 该 TPM 密钥不是 AIK。 |
The TPM key is not an AIK. |
| 0x8029041A | 该 TPM 密钥不是签名密钥。 |
The TPM key is not a signing key. |
| 0x8029041B | 该 TPM 已锁定。 |
The TPM is locked out. |
| 0x8029041C | 不支持请求的声明类型。 |
The claim type requested is not supported. |
| 0x8029041D | 不支持 TPM 版本。 |
TPM version is not supported. |
| 0x8029041E | 缓冲区长度不匹配。 |
The buffer lengths do not match. |
| 0x80290500 | 由于客户端上启用了零排放模式，已阻止与 TPM 相关的网络操作。 |
TPM related network operations are blocked as Zero Exhaust mode is enabled on client. |
| 0x802A0001 | 无法创建此对象。 |
The object could not be created. |
| 0x802A0002 | 已对此对象或拥有它的对象调用了关闭。 |
Shutdown was already called on this object or the object that owns it. |
| 0x802A0003 | 无法在此类型回调过程中调用该方法。 |
This method cannot be called during this type of callback. |
| 0x802A0004 | 此对象已密封，因此不再允许该更改。 |
This object has been sealed, so this change is no longer allowed. |
| 0x802A0005 | 从未设置请求的值。 |
The requested value was never set. |
| 0x802A0006 | 无法确定请求的值。 |
The requested value cannot be determined. |
| 0x802A0007 | 回调返回了无效的输出参数。 |
A callback returned an invalid output parameter. |
| 0x802A0008 | 回调返回了不同于 S_OK 或 S_FALSE 的成功代码。 |
A callback returned a success code other than S_OK or S_FALSE. |
| 0x802A0009 | 应该属于此对象的参数却属于其他对象。 |
A parameter that should be owned by this object is owned by a different object. |
| 0x802A000A | 多个项目符合搜索标准。 |
More than one item matched the search criteria. |
| 0x802A000B | 发生浮点运算溢出。 |
A floating-point overflow occurred. |
| 0x802A000C | 只能从创建对象的线程调用该方法。 |
This method can only be called from the thread that created the object. |
| 0x802A0101 | 当前在计划中安排了情节提要。 |
The storyboard is currently in the schedule. |
| 0x802A0102 | 情节提要尚未播放。 |
The storyboard is not playing. |
| 0x802A0103 | 起始关键帧可能出现在结束关键帧之后。 |
The start keyframe might occur after the end keyframe. |
| 0x802A0104 | 达到起始关键帧后，可能会无法确定结束关键帧的时间。 |
It might not be possible to determine the end keyframe time when the start keyframe is reached. |
| 0x802A0105 | 情节提要重复的两个部分可能会重叠。 |
Two repeated portions of a storyboard might overlap. |
| 0x802A0106 | 此转换已经添加到情节提要。 |
The transition has already been added to a storyboard. |
| 0x802A0107 | 此转换尚未添加到情节提要。 |
The transition has not been added to a storyboard. |
| 0x802A0108 | 此转换可能遮盖情节提要中其他转换的开头。 |
The transition might eclipse the beginning of another transition in the storyboard. |
| 0x802A0109 | 给定时间早于传递到上次更新的时间。 |
The given time is earlier than the time passed to the last update. |
| 0x802A010A | 该客户端已连接到计时器。 |
This client is already connected to a timer. |
| 0x802A010B | 传递的维度无效或者与对象的维度不相符。 |
The passed dimension is invalid or does not match the object's dimension. |
| 0x802A010C | 添加的原语在插入程序持续时间时开始或在插入程序持续时间之后开始。 |
The added primitive begins at or beyond the duration of the interpolator. |
| 0x802A0201 | 由于正在关闭窗口，无法完成操作。 |
The operation cannot be completed because the window is being closed. |
| 0x80300002 | 找不到数据收集器集。 |
Data Collector Set was not found. |
| 0x80300045 | 无法启动数据收集器集，因为文件夹过多。 |
Unable to start Data Collector Set because there are too many folders. |
| 0x80300070 | 可用磁盘空间不足，无法启动数据收集器集。 |
Not enough free disk space to start Data Collector Set. |
| 0x803000AA | 数据收集器集或其相关项之一已在使用中。 |
The Data Collector Set or one of its dependencies is already in use. |
| 0x803000B7 | 数据收集器集已存在。 |
Data Collector Set already exists. |
| 0x80300101 | 属性值冲突。 |
Property value conflict. |
| 0x80300102 | 此数据收集器集的当前配置要求正好包含一个数据收集程序。 |
The current configuration for this Data Collector Set requires that it contain exactly one Data Collector. |
| 0x80300103 | 需要有用户帐户，以便提交当前的数据收集器集属性。 |
A user account is required in order to commit the current Data Collector Set properties. |
| 0x80300104 | 数据收集器集未运行。 |
Data Collector Set is not running. |
| 0x80300105 | 检测到包含/排除 API 的列表中有冲突。不要在包含列表和排除列表中指定相同的 API。 |
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. |
| 0x80300106 | 已指定的可执行路径引用了网络共享或 UNC 路径。 |
The executable path you have specified refers to a network share or UNC path. |
| 0x80300107 | 已指定的可执行路径配置为用于 API 跟踪。 |
The executable path you have specified is already configured for API tracing. |
| 0x80300108 | 已指定的可执行路径不存在。请验证指定的路径是否正确。 |
The executable path you have specified does not exist. Verify that the specified path is correct. |
| 0x80300109 | 数据收集器已存在。 |
Data Collector already exists. |
| 0x8030010A | 等待数据收集器集开始通知已超时。 |
The wait for the Data Collector Set start notification has timed out. |
| 0x8030010B | 等待数据收集器启动已超时。 |
The wait for the Data Collector to start has timed out. |
| 0x8030010C | 等待报告生成工具完成已超时。 |
The wait for the report generation tool to finish has timed out. |
| 0x8030010D | 不允许有重复的项。 |
Duplicate items are not allowed. |
| 0x8030010E | 指定要跟踪的可执行文件时，必须指定到达可执行文件的完整路径，而非仅指定文件名。 |
When specifying the executable that you want to trace, you must specify a full path to the executable and not just a filename. |
| 0x8030010F | 提供的会话名无效。 |
The session name provided is invalid. |
| 0x80300110 | 必须启用事件日志通道 Microsoft-Windows-Diagnosis-PLA/Operational 才能执行此操作。 |
The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation. |
| 0x80300111 | 必须启用事件日志通道 Microsoft-Windows-TaskScheduler 才能执行此操作。 |
The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation. |
| 0x80300112 | 执行规则管理器失败。 |
The execution of the Rules Manager failed. |
| 0x80300113 | 尝试压缩或提取数据时出错。 |
An error occurred while attempting to compress or extract the data. |
| 0x80310000 | BitLocker 驱动器加密已锁定该驱动器。必须从控制面板解除此驱动器锁定。 |
This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel. |
| 0x80310001 | 该驱动器未加密。 |
This drive is not encrypted. |
| 0x80310002 | BIOS 与受信任的平台模块(TPM)通信不正常。有关 BIOS 的升级说明，请与计算机制造商联系。 |
The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310003 | BIOS 与主启动记录(MBR)通信不正常。有关 BIOS 的升级说明，请与计算机的制造商联系。 |
The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310004 | 缺少所需的 TPM 度量。如果计算机中有可引导的 CD 或 DVD，则将其取出，重新启动计算机，然后再启用 BitLocker。如果该问题仍存在，请确保主启动记录最新。 |
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. |
| 0x80310005 | 该驱动器的启动扇区与 BitLocker 驱动器加密不兼容。请在 Windows 恢复环境中使用 Bootrec.exe 工具以更新或修复引导管理器(BOOTMGR)。 |
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). |
| 0x80310006 | 该操作系统的引导管理器与 BitLocker 驱动器加密不兼容。请在 Windows 恢复环境中使用 Bootrec.exe 工具以更新或修复引导管理器(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). |
| 0x80310007 | 执行该操作至少需要一个安全密钥保护器。 |
At least one secure key protector is required for this operation to be performed. |
| 0x80310008 | 该驱动器上没有启用 BitLocker 驱动器加密。请启用 BitLocker。 |
BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker. |
| 0x80310009 | 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. |
| 0x8031000A | Active Directory 域服务林不包含所需的属性和类，以主持 BitLocker 驱动器加密或受信任的平台模块信息。请与域管理员联系，以验证是否安装了任何所需的 BitLocker Active Directory 架构扩展。 |
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. |
| 0x8031000B | 从 Active Directory 中获取的数据不是预期的类型。BitLocker 恢复信息可能丢失或已损坏。 |
The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000C | 从 Active Directory 中获取的数据不是预期的大小。BitLocker 恢复信息可能丢失或已损坏。 |
The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000D | 从 Active Directory 中读取的属性不包含任何值。BitLocker 恢复信息可能丢失或已损坏。 |
The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000E | 未设置属性。请验证你是否使用能够向 Active Directory 对象写入信息的域帐户登录。 |
The 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. |
| 0x8031000F | 在 Active Directory 域服务中找不到指定的属性。请与域管理员联系，以验证是否安装了任何所需的 BitLocker Active Directory 架构扩展。 |
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. |
| 0x80310010 | 已加密驱动器的 BitLocker 元数据无效。你可以尝试修复该驱动器以还原访问。 |
The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access. |
| 0x80310011 | 由于该驱动器上的可用空间不足，因此无法对其进行加密。请删除该驱动器上任何不必要的数据以创建其他可用空间，然后重试。 |
The 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. |
| 0x80310012 | 由于该驱动器包含系统启动信息，因此无法对其进行加密。请创建一个单独的分区，用作包含启动信息的系统驱动器；再创建一个分区，用作操作系统驱动器，然后对该操作系统驱动器进行加密。 |
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. |
| 0x80310013 | 由于不支持该文件系统，因此无法对该驱动器进行加密。 |
The drive cannot be encrypted because the file system is not supported. |
| 0x80310014 | 文件系统大小大于分区表中的分区大小。该驱动器可能已损坏或者可能被篡改。若要对其使用 BitLocker，必须重新格式化该分区。 |
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. |
| 0x80310015 | 无法对该驱动器进行加密。 |
This drive cannot be encrypted. |
| 0x80310017 | 在当前计算机上指定的数据驱动器未设置为自动解锁，因此无法自动解锁。 |
The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically. |
| 0x80310018 | 必须先初始化受信任的平台模块(TPM)，才能使用 BitLocker 驱动器加密。 |
You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption. |
| 0x80310019 | 无法在操作系统驱动器上执行尝试的操作。 |
The operation attempted cannot be performed on an operating system drive. |
| 0x8031001A | 为函数提供的缓冲区不足，无法包含返回的数据。请增加缓冲区大小，然后再次运行该函数。 |
The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again. |
| 0x8031001B | 转换驱动器时读取操作失败。该驱动器未转换。请重新启用 BitLocker。 |
A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker. |
| 0x8031001D | 需要一个或多个 BitLocker 密钥保护器。无法删除该驱动器上的最后一个密钥。 |
One or more BitLocker key protectors are required. You cannot delete the last key on this drive. |
| 0x8031001E | BitLocker 驱动器加密不支持群集配置。 |
Cluster configurations are not supported by BitLocker Drive Encryption. |
| 0x8031001F | 在当前计算机上指定的驱动器已配置为自动解锁。 |
The drive specified is already configured to be automatically unlocked on the current computer. |
| 0x80310020 | 该操作系统驱动器不受 BitLocker 驱动器加密保护。 |
The operating system drive is not protected by BitLocker Drive Encryption. |
| 0x80310021 | 在该驱动器上 BitLocker 驱动器加密已暂停。为该驱动器配置的所有 BitLocker 密钥保护程序都被有效禁用，并且将使用未加密(明文)密钥对该驱动器进行自动解锁。 |
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. |
| 0x80310022 | 尝试锁定的驱动器没有任何可用于加密的密钥保护程序，因为 BitLocker 保护当前已暂停。请重新启用 BitLocker 对该驱动器进行解锁。 |
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. |
| 0x80310023 | BitLocker 无法使用受信任的平台模块(TPM)保护数据驱动器。只能对操作系统驱动器使用 TPM 保护。 |
BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive. |
| 0x80310024 | 无法更新已加密驱动器的 BitLocker 元数据，因为它已由另一个进程锁定以进行更新。请重试该进程。 |
The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again. |
| 0x80310025 | 受信任的平台模块(TPM)的存储根密钥(SRK)授权数据不是零，因此与 BitLocker 不兼容。请初始化 TPM，然后尝试将其与 BitLocker 一起使用。 |
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. |
| 0x80310026 | 在这种大小的扇区上无法使用驱动器加密算法。 |
The drive encryption algorithm cannot be used on this sector size. |
| 0x80310027 | 无法通过提供的密钥解锁驱动器。请确认你提供了正确的密钥，然后重试。 |
The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again. |
| 0x80310028 | 指定的驱动器不是操作系统驱动器。 |
The drive specified is not the operating system drive. |
| 0x80310029 | 直到对与该计算机关联的固定数据驱动器和可移动数据驱动器禁用自动解锁之后，才能在操作系统驱动器上禁用 BitLocker 驱动器加密。 |
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. |
| 0x8031002A | 系统分区引导扇区不执行受信任的平台模块(TPM)度量。请在 Windows 恢复环境中使用 Bootrec.exe 工具以更新或修复引导扇区。 |
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. |
| 0x8031002B | 若要进行加密，BitLocker 驱动器加密操作系统驱动器文件系统必须采用 NTFS 格式。将驱动器转换为 NTFS，然后启用 BitLocker。 |
BitLocker 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. |
| 0x8031002C | 组策略设置要求在对驱动器加密之前必须指定恢复密码。 |
Group Policy settings require that a recovery password be specified before encrypting the drive. |
| 0x8031002D | 无法在之前加密的驱动器上设置驱动器加密算法和密钥。若要使用 BitLocker 驱动器加密对该驱动器进行加密，请删除以前的加密，然后启用 BitLocker。 |
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. |
| 0x8031002E | BitLocker 驱动器加密无法加密指定的驱动器，因为加密密钥不可用。请添加一个密钥保护器以对该驱动器进行加密。 |
BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive. |
| 0x80310030 | BitLocker 驱动器加密检测到计算机中存在可引导媒体(CD 或 DVD)。请取出该媒体并重新启动计算机，然后配置 BitLocker。 |
BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker. |
| 0x80310031 | 无法添加该密钥保护器。该驱动器只允许这种类型的一个密钥保护器。 |
This key protector cannot be added. Only one key protector of this type is allowed for this drive. |
| 0x80310032 | 由于指定了相对路径，因此找不到恢复密码文件。必须将恢复密码保存到完全限定的路径。可以在路径中使用该计算机上配置的环境变量。 |
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. |
| 0x80310033 | 在该驱动器上找不到指定的密钥保护器。请尝试其他密钥保护器。 |
The specified key protector was not found on the drive. Try another key protector. |
| 0x80310034 | 提供的恢复密钥已损坏，因此无法用于访问驱动器。必须使用其他恢复方法(如恢复密码、数据恢复代理或恢复密钥的备份)恢复对驱动器的访问。 |
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. |
| 0x80310035 | 提供的恢复密码的格式无效。BitLocker 恢复密码为 48 位。请验证恢复密码的格式是否正确，然后重试。 |
The 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. |
| 0x80310036 | 随机数生成器检查测试失败。 |
The random number generator check test failed. |
| 0x80310037 | 要求 FIPS 兼容的组策略设置阻止生成本地恢复密码或阻止被 BitLocker 驱动器加密使用。当在 FIPS 兼容模式运行时，BitLocker 恢复选项可以是存储在 U 盘上的恢复密钥，也可以是通过数据恢复代理进行恢复。 |
The 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. |
| 0x80310038 | 要求 FIPS 兼容的组策略设置阻止将恢复密码保存到 Active Directory。当在 FIPS 兼容模式运行时，BitLocker 恢复选项可以是存储在 U 盘上的恢复密钥，也可以是通过数据恢复代理进行恢复。请检查你的组策略设置配置。 |
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. |
| 0x80310039 | 必须完全解密驱动器才能完成此操作。 |
The drive must be fully decrypted to complete this operation. |
| 0x8031003A | 无法对该操作使用指定的密钥保护器。 |
The key protector specified cannot be used for this operation. |
| 0x8031003B | 驱动器上没有执行硬件测试的密钥保护器。 |
No key protectors exist on the drive to perform the hardware test. |
| 0x8031003C | 在 USB 设备上找不到 BitLocker 启动密钥或恢复密码。请验证你是否拥有正确的 USB 设备，以及该 USB 设备是否已插入计算机的活动 USB 端口，重新启动计算机，然后重试。如果该问题仍然存在，请与计算机制造商联系以获取 BIOS 升级说明。 |
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. |
| 0x8031003D | 提供的 BitLocker 启动密钥或恢复密码问题已损坏或无效。请验证你是否拥有正确的启动密钥或恢复密码文件，然后重试。 |
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. |
| 0x8031003E | 无法从启动密钥或恢复密码中获取 BitLocker 加密密钥。请验证你是否拥有正确的启动密钥或恢复密钥，然后重试。 |
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. |
| 0x8031003F | 受信任的平台模块(TPM)被禁用。必须启用、初始化 TPM 并且拥有有效的所有权，然后才能将其与 BitLocker 驱动器加密一起使用。 |
The 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. |
| 0x80310040 | 无法管理指定驱动器的 BitLocker 配置，因为当前该计算机正在以安全模式运行。当处于安全模式时，只能使用 BitLocker 驱动器加密进行恢复。 |
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. |
| 0x80310041 | 受信任的平台模块(TPM)无法解锁该驱动器。选择 BitLocker 设置后系统启动信息已更改或 PIN 不匹配。如果尝试几次后问题仍然存在，则可能是硬件或固件问题。 |
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. |
| 0x80310042 | 无法从受信任的平台模块(TPM)获取 BitLocker 加密密钥。 |
The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM). |
| 0x80310043 | 无法从受信任的平台模块(TPM)和 PIN 获取 BitLocker 加密密钥。 |
The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN. |
| 0x80310044 | 自启用 BitLocker 驱动器加密后，一个引导应用程序已经更改。 |
A boot application has changed since BitLocker Drive Encryption was enabled. |
| 0x80310045 | 自启用 BitLocker 驱动器加密后，引导配置数据(BCD)设置已经更改。 |
The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled. |
| 0x80310046 | 要求 FIPS 兼容的组策略设置禁止使用未加密的密钥，这会阻止 BitLocker 在该驱动器上暂停。有关详细信息，请与域管理员联系。 |
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. |
| 0x80310047 | 无法使用 BitLocker 驱动器加密对该驱动器进行加密，因为文件系统未扩展到该驱动器的末尾。请对该驱动器进行重新分区，然后重试。 |
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. |
| 0x80310048 | 无法在操作系统驱动器上启用 BitLocker 驱动器加密。请与计算机制造商联系以获取 BIOS 升级说明。 |
BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310049 | 此版本的 Windows 不包含 BitLocker 驱动器加密。若要使用 BitLocker 驱动器加密，请升级操作系统。 |
This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system. |
| 0x8031004A | 由于 BitLocker 系统文件丢失或已损坏，因此无法使用 BitLocker 驱动器加密。请使用 Windows 启动修复将这些文件还原到你的计算机。 |
BitLocker 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. |
| 0x8031004B | 该驱动器正在使用，因此无法锁定。 |
The drive cannot be locked when the drive is in use. |
| 0x8031004C | 与当前线程相关联的访问令牌不是模拟标记。 |
The access token associated with the current thread is not an impersonated token. |
| 0x8031004D | 无法获取 BitLocker 加密密钥。请验证是否启用了受信任的平台模块(TPM)以及是否获取了所有权。如果该计算机没有 TPM，请验证该 U 盘是否已插入以及是否可用。 |
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. |
| 0x8031004E | 必须重新启动计算机才能继续 BitLocker 驱动器加密。 |
You must restart your computer before continuing with BitLocker Drive Encryption. |
| 0x8031004F | 启用引导调试时无法进行驱动器加密。请使用 bcdedit 命令行工具关闭引导调试。 |
Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging. |
| 0x80310050 | 由于 BitLocker 驱动器加密处于原始访问模式，因此没有采取任何操作。 |
No action was taken as BitLocker Drive Encryption is in raw access mode. |
| 0x80310051 | 该驱动器的 BitLocker 驱动器加密无法进入原始访问模式，因为该驱动器当前正在使用。 |
BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use. |
| 0x80310052 | 启动配置数据(BCD)中为 BitLocker 驱动器加密完整性保护应用程序指定的路径不正确。请验证并更正你的 BCD 设置，然后重试。 |
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. |
| 0x80310053 | 当计算机运行在预安装环境或恢复环境时，只能使用 BitLocker 驱动器加密进行有限的预配或恢复。 |
BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments. |
| 0x80310054 | 自动解锁主密钥不在操作系统驱动器中。 |
The auto-unlock master key was not available from the operating system drive. |
| 0x80310055 | 系统固件未能在计算机重新启动时清除系统内存。 |
The system firmware failed to enable clearing of system memory when the computer was restarted. |
| 0x80310056 | 无法加密隐藏的驱动器。 |
The hidden drive cannot be encrypted. |
| 0x80310057 | 因为该驱动器处于临时状态，因此忽略 BitLocker 加密密钥。 |
BitLocker encryption keys were ignored because the drive was in a transient state. |
| 0x80310058 | 不允许在该驱动器上使用基于公钥的保护器。 |
Public key based protectors are not allowed on this drive. |
| 0x80310059 | BitLocker 驱动器加密正在该驱动器上执行某个操作。继续之前，请完成所有操作。 |
BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing. |
| 0x8031005A | 此版本的 Windows 不支持 BitLocker 驱动器加密这项功能。若要使用该功能，请升级操作系统。 |
This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system. |
| 0x8031005B | BitLocker 启动选项的组策略设置冲突，因此无法应用。有关详细信息，请与系统管理员联系。 |
The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information. |
| 0x8031005C | 组策略设置不允许创建恢复密码。 |
Group Policy settings do not permit the creation of a recovery password. |
| 0x8031005D | 组策略设置要求创建恢复密码。 |
Group Policy settings require the creation of a recovery password. |
| 0x8031005E | 组策略设置不允许创建恢复密钥。 |
Group Policy settings do not permit the creation of a recovery key. |
| 0x8031005F | 组策略设置要求创建恢复密钥。 |
Group Policy settings require the creation of a recovery key. |
| 0x80310060 | 组策略设置不允许在启动时使用 PIN。请选择其他 BitLocker 启动选项。 |
Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option. |
| 0x80310061 | 组策略设置要求在启动时使用 PIN。请选择此 BitLocker 启动选项。 |
Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option. |
| 0x80310062 | 组策略设置不允许使用启动密钥。请选择其他 BitLocker 启动选项。 |
Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option. |
| 0x80310063 | 组策略设置要求使用启动密钥。请选择此 BitLocker 启动选项。 |
Group Policy settings require the use of a startup key. Please choose this BitLocker startup option. |
| 0x80310064 | 组策略设置不允许使用启动密钥和 PIN。请选择其他 BitLocker 启动选项。 |
Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option. |
| 0x80310065 | 组策略设置要求使用启动密钥和 PIN。请选择此 BitLocker 启动选项。 |
Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option. |
| 0x80310066 | 组策略禁止在启动时使用仅 TPM。请选择其他 BitLocker 启动选项。 |
Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option. |
| 0x80310067 | 组策略设置要求在启动时使用仅 TPM。请选择此 BitLocker 启动选项。 |
Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option. |
| 0x80310068 | 提供的 PIN 不符合最小或最大长度要求。 |
The PIN provided does not meet minimum or maximum length requirements. |
| 0x80310069 | 当前在驱动器上的 BitLocker 驱动器加密版本不支持密钥保护器。请升级此驱动器以添加密钥保护器。 |
The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector. |
| 0x8031006A | 组策略设置不允许创建密码。 |
Group Policy settings do not permit the creation of a password. |
| 0x8031006B | 组策略设置要求创建密码。 |
Group Policy settings require the creation of a password. |
| 0x8031006C | 要求 FIPS 兼容的组策略设置阻止生成或使用密码。有关详细信息，请与系统管理员联系。 |
The Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information. |
| 0x8031006D | 无法向操作系统驱动器添加密码。 |
A password cannot be added to the operating system drive. |
| 0x8031006E | 驱动器上的 BitLocker 对象标识符(OID)无效或已损坏。请使用 manage-BDE 重置该驱动器上的 OID。 |
The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive. |
| 0x8031006F | 驱动器太小，无法使用 BitLocker 驱动器加密进行保护。 |
The drive is too small to be protected using BitLocker Drive Encryption. |
| 0x80310070 | 选定的发现驱动器类型与驱动器上的文件系统不兼容。必须在 FAT 格式的驱动器上创建 BitLocker To Go 发现驱动器。 |
The 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. |
| 0x80310071 | 计算机的组策略设置不允许使用所选的发现驱动器类型。请验证组策略设置是否允许创建用于 BitLocker To Go 的发现驱动器。 |
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. |
| 0x80310072 | 组策略设置不允许将用户证书(如智能卡)与 BitLocker 驱动器加密一起使用。 |
Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption. |
| 0x80310073 | 组策略设置要求你具有与 BitLocker 驱动器加密一起使用的有效用户证书，如智能卡。 |
Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption. |
| 0x80310074 | 组策略设置要求你将基于智能卡的密钥保护器与 BitLocker 驱动器加密一起使用。 |
Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption. |
| 0x80310075 | 组策略设置不允许自动解锁受 BitLocker 保护的固定数据驱动器。 |
Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked. |
| 0x80310076 | 组策略设置不允许自动解锁受 BitLocker 保护的可移动数据驱动器。 |
Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked. |
| 0x80310077 | 组策略设置不允许在可移动数据驱动器上配置 BitLocker 驱动器加密。 |
Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives. |
| 0x80310078 | 组策略设置不允许在可移动数据驱动器上启用 BitLocker 驱动器加密。如果需要启用 BitLocker，请与系统管理员联系。 |
Group 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. |
| 0x80310079 | 组策略设置不允许在可移动数据驱动器上关闭 BitLocker 驱动器加密。如果需要关闭 BitLocker，请与系统管理员联系。 |
Group 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. |
| 0x80310080 | 密码不符合最小密码长度要求。默认情况下，密码长度必须至少为 8 个字符。有关你组织的密码长度要求，请与系统管理员联系。 |
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. |
| 0x80310081 | 密码不符合系统管理员设置的复杂性要求。请尝试添加大小写字符、数字和符号。 |
Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols. |
| 0x80310082 | 无法加密此驱动器，因为它是为 Windows 系统恢复选项保留的。 |
This drive cannot be encrypted because it is reserved for Windows System Recovery Options. |
| 0x80310083 | 由于组策略设置发生冲突，因此无法对此驱动器应用 BitLocker 驱动器加密。当禁用用户恢复选项时，无法将 BitLocker 配置为自动解锁固定数据驱动器。如果你希望在进行密钥验证之后自动解锁受 BitLocker 保护的固定数据驱动器，请在启用 BitLocker 之前让系统管理员解决设置冲突。 |
BitLocker 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. |
| 0x80310084 | 由于组策略设置发生冲突，因此无法对此驱动器应用 BitLocker 驱动器加密。当禁用用户恢复选项时，无法将 BitLocker 配置为自动解锁可移动数据驱动器。如果你希望在进行密钥验证之后自动解锁受 BitLocker 保护的可移动数据驱动器，请在启用 BitLocker 之前让系统管理员解决设置冲突。 |
BitLocker 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. |
| 0x80310085 | 指定证书的增强型密钥使用(EKU)属性不允许将其用于 BitLocker 驱动器加密。BitLocker 不要求证书具备 EKU 属性，但是如果已配置了该属性，则必须将其设置为与为 BitLocker 配置的 OID 匹配的对象标识符(OID)。 |
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. |
| 0x80310086 | 由于组策略设置，无法对当前配置的此驱动器应用 BitLocker 驱动器加密。为驱动器加密提供的证书是自签名证书。当前组策略设置不允许使用自签名证书。在尝试启用 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. |
| 0x80310087 | 由于组策略设置发生冲突，因此无法对此驱动器应用 BitLocker 加密。当对不受 BitLocker 保护的驱动器的写访问被拒绝时，无法要求使用 USB 启动密钥。请在尝试启用 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. |
| 0x80310088 | 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. |
| 0x80310089 | 请求的虚拟化大小过大。 |
The requested virtualization size is too big. |
| 0x80310090 | 由于操作系统驱动器上恢复选项的组策略设置发生冲突，因此无法对此驱动器应用 BitLocker 驱动器加密。当不允许生成恢复密码时，无法要求将恢复信息存储到 Active Directory 域服务。请在尝试启用 BitLocker 之前让系统管理员解决这些策略冲突。 |
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. |
| 0x80310091 | 由于固定数据驱动器上恢复选项的组策略设置发生冲突，因此无法对此驱动器应用 BitLocker 驱动器加密。当不允许生成恢复密码时，无法要求将恢复信息存储到 Active Directory 域服务。请在尝试启用 BitLocker 之前让系统管理员解决这些策略冲突。 |
BitLocker 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. |
| 0x80310092 | 由于可移动数据驱动器上恢复选项的组策略设置发生冲突，因此无法对此驱动器应用 BitLocker 驱动器加密。当不允许生成恢复密码时，无法要求将恢复信息存储到 Active Directory 域服务。请在尝试启用 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. |
| 0x80310093 | 指定证书的密钥使用(KU)属性不允许其用于 BitLocker 驱动器加密。BitLocker 不要求证书具有 KU 属性，但如果某个证书配置了此属性，则必须将此证书设置为“密钥加密”或“密钥协议”。 |
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. |
| 0x80310094 | 无法授权与指定证书关联的私钥。未提供私钥授权或者提供的授权无效。 |
The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid. |
| 0x80310095 | 必须使用“证书”管理单元删除数据恢复代理证书。 |
Removal of the data recovery agent certificate must be done using the Certificates snap-in. |
| 0x80310096 | 使用 Windows Vista 和 Windows Server 2008 附带的不支持组织标识符的 BitLocker 驱动器加密版本对该驱动器进行加密。若要为该驱动器指定组织标识符，请使用 \"manage-bde -upgrade\" 命令将驱动器加密升级到最新版本。 |
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. |
| 0x80310097 | 该驱动器无法锁定，因为它在此计算机上是自动解锁的。删除自动解锁保护程序可锁定此驱动器。 |
The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive. |
| 0x80310098 | 你的智能卡不支持 ECC 智能卡的默认 BitLocker 密钥派生功能 SP800-56A。要求与 FIPS 兼容的组策略设置阻止 BitLocker 使用任何其他密钥派生功能进行加密。在 FIPS 受限制的环境中，必须使用与 FIPS 兼容的智能卡。 |
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. |
| 0x80310099 | 无法从受信任的平台模块(TPM)和增强的 PIN 获取 BitLocker 加密密钥。请尝试使用只包含数字的 PIN。 |
The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals. |
| 0x8031009A | 请求的 TPM PIN 包含无效字符。 |
The requested TPM PIN contains invalid characters. |
| 0x8031009B | 存储在此驱动器上的管理信息包含未知类型。如果你使用的是旧版本的 Windows，请尝试从最新版本访问此驱动器。 |
The 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. |
| 0x8031009C | 该功能仅在 EFI 系统上受支持。 |
The feature is only supported on EFI systems. |
| 0x8031009D | 系统上找到多个网络密钥保护程序证书。 |
More than one Network Key Protector certificate has been found on the system. |
| 0x8031009E | 必须使用证书管理单元来删除网络密钥保护程序证书。 |
Removal of the Network Key Protector certificate must be done using the Certificates snap-in. |
| 0x8031009F | 网络密钥保护程序证书存储中找到了无效的证书。 |
An invalid certificate has been found in the Network Key Protector certificate store. |
| 0x803100A0 | 此驱动器未受 PIN 保护。 |
This drive isn't protected with a PIN. |
| 0x803100A1 | 请输入正确的当前 PIN。 |
Please enter the correct current PIN. |
| 0x803100A2 | 必须使用管理员帐户登录才能更改 PIN。单击该链接以管理员身份重置 PIN。 |
You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator. |
| 0x803100A3 | 由于请求失败的次数过多，BitLocker 已禁止 PIN 更改。单击该链接以管理员身份重置 PIN。 |
BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator. |
| 0x803100A4 | 系统管理员要求密码仅包含可打印的 ASCII 字符。这包括无重音字母 (A-Z、a-z)、数字 (0-9)、空格、算术符号、常用标点符号、分隔符，以及以下符号: # $ & @ ^ _ ~ 。 |
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: # $ & @ ^ _ ~ . |
| 0x803100A5 | 在精简预配的存储上，BitLocker 驱动器加密仅支持“仅加密已用空间”。 |
BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage. |
| 0x803100A6 | BitLocker 驱动器加密不支持在精简预配的存储上擦除可用空间。 |
BitLocker Drive Encryption does not support wiping free space on thin provisioned storage. |
| 0x803100A7 | 此驱动器不支持要求的身份验证密钥长度。 |
The required authentication key length is not supported by the drive. |
| 0x803100A8 | 此驱动器未受密码保护。 |
This drive isn't protected with a password. |
| 0x803100A9 | 请输入正确的当前密码。 |
Please enter the correct current password. |
| 0x803100AA | 密码不能超过 256 个字符。 |
The password cannot exceed 256 characters. |
| 0x803100AB | 无法添加密码密钥保护程序，原因是驱动器中存在 TPM 保护程序。 |
A password key protector cannot be added because a TPM protector exists on the drive. |
| 0x803100AC | 无法添加 TPM 密钥保护程序，原因是驱动器中存在密码保护程序。 |
A TPM key protector cannot be added because a password protector exists on the drive. |
| 0x803100AD | 只能从指定的 CSV 卷的协调器节点执行此命令。 |
This command can only be performed from the coordinator node for the specified CSV volume. |
| 0x803100AE | 当卷是群集的一部分时，无法在卷上执行此命令。 |
This command cannot be performed on a volume when it is part of a cluster. |
| 0x803100AF | 由于组策略配置的原因，BitLocker 未还原为使用 BitLocker 软件加密。 |
BitLocker did not revert to using BitLocker software encryption due to group policy configuration. |
| 0x803100B0 | BitLocker 无法管理此驱动器，原因是此驱动器的硬件加密功能已被使用。 |
The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use. |
| 0x803100B1 | 组策略设置不允许使用基于硬件的加密。 |
Group Policy settings do not allow the use of hardware-based encryption. |
| 0x803100B2 | 指定的驱动器不支持基于硬件的加密。 |
The drive specified does not support hardware-based encryption. |
| 0x803100B3 | 在磁盘加密或解密过程中，无法升级 BitLocker。 |
BitLocker cannot be upgraded during disk encryption or decryption. |
| 0x803100B4 | 使用硬件加密的卷不能用作发现卷。 |
Discovery Volumes are not supported for volumes using hardware encryption. |
| 0x803100B5 | 没有检测到预启动键盘。用户可能无法提供必要的输入来解锁卷。 |
No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume. |
| 0x803100B6 | 没有检测到预启动键盘或 Windows 恢复环境。用户可能无法提供必要的输入来解锁卷。 |
No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume. |
| 0x803100B7 | 组策略设置要求创建起动 PIN，但是预启动键盘无法在此设备上使用。用户可能无法提供必要的输入来解锁卷。 |
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. |
| 0x803100B8 | 组策略设置要求创建恢复密码，但是预启动键盘或 Windows 恢复环境无法在此设备上使用。用户可能无法提供必要的输入来解锁卷。 |
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. |
| 0x803100B9 | 当前未进行擦除可用空间的操作。 |
Wipe of free space is not currently taking place. |
| 0x803100BA | BitLocker 无法使用用于平台完整性的“安全引导”，原因是“安全引导”已禁用。 |
BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled. |
| 0x803100BB | BitLocker 无法使用用于平台完整性的“安全引导”，原因是“安全引导”配置不满足 BitLocker 的要求。 |
BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker. |
| 0x803100BC | 你的计算机不支持基于硬件的 BitLocker 加密。请与计算机制造商联系，以获取固件更新。 |
Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates. |
| 0x803100BD | 无法在该卷上启用 BitLocker，原因是它包含卷影副本。删除所有卷影副本，然后再对卷进行加密。 |
BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume. |
| 0x803100BE | 无法对此驱动器应用 BitLocker 驱动器加密，原因是“增强型引导配置数据”的组策略设置包含无效数据。请让你的系统管理员解决此无效配置，然后再尝试启用 BitLocker。 |
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. |
| 0x803100BF | 这台电脑的固件无法支持硬件加密。 |
This PC's firmware is not capable of supporting hardware encryption. |
| 0x803100C0 | BitLocker 已在过多次的失败请求后禁用密码更改。单击该链接以管理员身份重置密码。 |
BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator. |
| 0x803100C1 | 必须使用管理员帐户登录才能更改密码。单击该链接以管理员身份重置密码。 |
You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator. |
| 0x803100C2 | BitLocker 无法保存恢复密码，因为指定的 Microsoft 帐户已被暂停使用。 |
BitLocker cannot save the recovery password because the specified Microsoft account is Suspended. |
| 0x803100C3 | BitLocker 无法保存恢复密码，因为指定的 Microsoft 帐户已被阻止。 |
BitLocker cannot save the recovery password because the specified Microsoft account is Blocked. |
| 0x803100C4 | 这台电脑未预配为支持设备加密。请在所有卷上启用 BitLocker 以符合设备加密策略。 |
This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy. |
| 0x803100C5 | 这台电脑无法支持设备加密，因为存在未加密的固定数据卷。 |
This PC cannot support device encryption because unencrypted fixed data volumes are present. |
| 0x803100C6 | 这台电脑不符合支持设备加密的硬件要求。 |
This PC does not meet the hardware requirements to support device encryption. |
| 0x803100C7 | 这台电脑无法支持设备加密，因为未正确配置 WinRE。 |
This PC cannot support device encryption because WinRE is not properly configured. |
| 0x803100C8 | 卷上启用了保护功能，但是该功能已被暂停。这可能是由于系统正在应用更新所致。请在重新启动后再试一次。 |
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. |
| 0x803100C9 | 这台电脑未预配为支持设备加密。 |
This PC is not provisioned to support device encryption. |
| 0x803100CA | 由于过多次输入了错误的密码，因此已触发设备锁定。 |
Device Lock has been triggered due to too many incorrect password attempts. |
| 0x803100CB | 卷上尚未启用保护功能。启用保护功能需要使用连接的帐户。如果你已有连接帐户并看到此错误，请参考事件日志获取详细信息。 |
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. |
| 0x803100CC | PIN 只能包含 0 至 9 的数字。 |
Your PIN can only contain numbers from 0 to 9. |
| 0x803100CD | BitLocker 无法使用硬件重播保护，因为你的电脑上未提供计数器。 |
BitLocker cannot use hardware replay protection because no counter is available on your PC. |
| 0x803100CE | 由于计数器不匹配，设备锁定状态验证失败。 |
Device Lockout state validation failed due to counter mismatch. |
| 0x803100CF | 输入缓冲区太大。 |
The input buffer is too large. |
| 0x803100D0 | 调用目标不支持请求的功能。 |
The target of an invocation does not support requested capability. |
| 0x803100D1 | 这台电脑的配置当前阻止设备加密。 |
Device encryption is currently blocked by this PC's configuration. |
| 0x803100D2 | 此驱动器已选择关闭设备加密。 |
This drive has been opted out of device encryption. |
| 0x803100D3 | 此驱动器无法进行设备加密。 |
Device encryption isn't available for this drive. |
| 0x803100D4 | 此版本的 Windows 中不支持 BitLocker 写入时加密模式。你可以启用 BitLocker 而不使用写入时加密模式。 |
The 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. |
| 0x803100D5 | 对于此驱动器类型，组策略禁止将恢复密码备份到 Active Directory。有关详细信息，请与系统管理员联系。 |
Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator. |
| 0x803100D6 | 在加密此驱动器时，无法关闭设备加密。请稍后再试。 |
Device encryption can't be turned off while this drive is being encrypted. Please try again later. |
| 0x803100D7 | 不支持此操作，因为该驱动器并不通过设备加密来自动管理。 |
This action isn't supported because this drive isn't automatically managed with device encryption. |
| 0x803100D8 | 在下次重新启动以前，将无法在此驱动器上暂停 BitLocker。 |
BitLocker can't be suspended on this drive until the next restart. |
| 0x803100D9 | BitLocker 驱动器加密策略不允许对受保护的 OS 卷进行 KSR 操作。 |
BitLocker Drive Encryption policy does not allow KSR operation with protected OS volume. |
| 0x80320001 | 标注不存在。 |
The callout does not exist. |
| 0x80320002 | 筛选条件不存在。 |
The filter condition does not exist. |
| 0x80320003 | 筛选器不存在。 |
The filter does not exist. |
| 0x80320004 | 层不存在。 |
The layer does not exist. |
| 0x80320005 | 提供程序不存在。 |
The provider does not exist. |
| 0x80320006 | 提供程序上下文不存在。 |
The provider context does not exist. |
| 0x80320007 | 子层不存在。 |
The sublayer does not exist. |
| 0x80320008 | 对象不存在。 |
The object does not exist. |
| 0x80320009 | 具有该 GUID 或 LUID 的对象已经存在。 |
An object with that GUID or LUID already exists. |
| 0x8032000A | 其他对象引用了该对象，因此无法将其删除。 |
The object is referenced by other objects so cannot be deleted. |
| 0x8032000B | 不允许从动态会话内进行调用。 |
The call is not allowed from within a dynamic session. |
| 0x8032000C | 调用是从错误的会话进行的，因此无法完成。 |
The call was made from the wrong session so cannot be completed. |
| 0x8032000D | 必须从显式事务内进行该调用。 |
The call must be made from within an explicit transaction. |
| 0x8032000E | 不允许从显式事务内进行该调用。 |
The call is not allowed from within an explicit transaction. |
| 0x8032000F | 显式事务已经强制取消。 |
The explicit transaction has been forcibly cancelled. |
| 0x80320010 | 会话已取消。 |
The session has been cancelled. |
| 0x80320011 | 不允许从只读事务内进行调用。 |
The call is not allowed from within a read-only transaction. |
| 0x80320012 | 等待获取事务锁定时调用超时。 |
The call timed out while waiting to acquire the transaction lock. |
| 0x80320013 | 网络诊断事件的集合已禁用。 |
Collection of network diagnostic events is disabled. |
| 0x80320014 | 指定的层不支持该操作。 |
The operation is not supported by the specified layer. |
| 0x80320015 | 仅有内核模式的调用方允许使用该调用。 |
The call is allowed for kernel-mode callers only. |
| 0x80320016 | 该调用尝试将两个生存时间不兼容的对象相互关联。 |
The call tried to associate two objects with incompatible lifetimes. |
| 0x80320017 | 此对象为内置对象，因此无法删除。 |
The object is built in so cannot be deleted. |
| 0x80320018 | 已达到标注的最大数目。 |
The maximum number of callouts has been reached. |
| 0x80320019 | 无法发送该通知，因为消息队列已达到其最大容量。 |
A notification could not be delivered because a message queue is at its maximum capacity. |
| 0x8032001A | 流量参数与安全关联上下文参数不匹配。 |
The traffic parameters do not match those for the security association context. |
| 0x8032001B | 当前安全关联状态不允许使用该调用。 |
The call is not allowed for the current security association state. |
| 0x8032001C | 所需的指针为 Null。 |
A required pointer is null. |
| 0x8032001D | 枚举器无效。 |
An enumerator is not valid. |
| 0x8032001E | 标志字段包含无效值。 |
The flags field contains an invalid value. |
| 0x8032001F | 网络掩码无效。 |
A network mask is not valid. |
| 0x80320020 | FWP_RANGE 无效。 |
An FWP_RANGE is not valid. |
| 0x80320021 | 时间间隔无效。 |
The time interval is not valid. |
| 0x80320022 | 必须至少包含一个元素的数组的长度为零。 |
An array that must contain at least one element is zero length. |
| 0x80320023 | displayData.name 字段不能为 Null。 |
The displayData.name field cannot be null. |
| 0x80320024 | 该操作类型不是筛选器允许的操作类型。 |
The action type is not one of the allowed action types for a filter. |
| 0x80320025 | 筛选器权重无效。 |
The filter weight is not valid. |
| 0x80320026 | 筛选条件包含与操作数不兼容的匹配类型。 |
A filter condition contains a match type that is not compatible with the operands. |
| 0x80320027 | FWP_VALUE 或 FWPM_CONDITION_VALUE 类型错误。 |
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. |
| 0x80320028 | 整数值超出允许的范围。 |
An integer value is outside the allowed range. |
| 0x80320029 | 保留的字段为非零值。 |
A reserved field is non-zero. |
| 0x8032002A | 筛选器在单个字段上不能包含多个条件运算。 |
A filter cannot contain multiple conditions operating on a single field. |
| 0x8032002B | 策略不能多次包含同一键控模块。 |
A policy cannot contain the same keying module more than once. |
| 0x8032002C | 操作类型与层不兼容。 |
The action type is not compatible with the layer. |
| 0x8032002D | 操作类型与子层不兼容。 |
The action type is not compatible with the sublayer. |
| 0x8032002E | 原始上下文或提供程序上下文与层不兼容。 |
The raw context or the provider context is not compatible with the layer. |
| 0x8032002F | 原始上下文或提供程序上下文与标注不兼容。 |
The raw context or the provider context is not compatible with the callout. |
| 0x80320030 | 身份验证方法与策略类型不兼容。 |
The authentication method is not compatible with the policy type. |
| 0x80320031 | Diffie-Hellman 组与策略类型不兼容。 |
The Diffie-Hellman group is not compatible with the policy type. |
| 0x80320032 | IKE 策略不能包含扩展模式策略。 |
An IKE policy cannot contain an Extended Mode policy. |
| 0x80320033 | 枚举模板或订阅将不匹配任何对象。 |
The enumeration template or subscription will never match any objects. |
| 0x80320034 | 提供程序上下文类型错误。 |
The provider context is of the wrong type. |
| 0x80320036 | 已达到子层的最大数目。 |
The maximum number of sublayers has been reached. |
| 0x80320037 | 标注的通知功能返回了一个错误。 |
The notification function for a callout returned an error. |
| 0x80320038 | IPSec 身份验证转换无效。 |
The IPsec authentication transform is not valid. |
| 0x80320039 | IPSec 密码转换无效。 |
The IPsec cipher transform is not valid. |
| 0x8032003A | IPSec 密码转换与策略不兼容。 |
The IPsec cipher transform is not compatible with the policy. |
| 0x8032003B | IPSec 转换类型的组合无效。 |
The combination of IPsec transform types is not valid. |
| 0x8032003C | 策略不能多次包含同一个身份验证方法。 |
A policy cannot contain the same auth method more than once. |
| 0x8032003D | 隧道终结点配置无效。 |
A tunnel endpoint configuration is invalid. |
| 0x8032003E | WFP MAC 层未就绪。 |
The WFP MAC Layers are not ready. |
| 0x8032003F | 已经注册具有密钥识别功能的密钥管理器 |
A key manager capable of key dictation is already registered |
| 0x80320040 | 密钥管理器指示密钥无效 |
A key manager dictated invalid keys |
| 0x80320041 | BFE IPsec 连接跟踪已禁用。 |
The BFE IPsec Connection Tracking is disabled. |
| 0x80320042 | DNS 名称无效。 |
The DNS name is invalid. |
| 0x80320043 | 由于其他配置设置，引擎选项仍处于启用状态。 |
The engine option is still enabled due to other configuration settings. |
| 0x80320044 | IKEEXT 服务未运行。只有在计算机已应用 IPSec 策略时，此服务才会运行。 |
The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine. |
| 0x80320104 | 数据包应丢弃，不应发送任何 ICMP。 |
The packet should be dropped, no ICMP should be sent. |
| 0x80340002 | 到网络接口的绑定已关闭。 |
The binding to the network interface is being closed. |
| 0x80340004 | 指定的版本无效。 |
An invalid version was specified. |
| 0x80340005 | 使用了无效的特征表。 |
An invalid characteristics table was used. |
| 0x80340006 | 找不到网络接口，或网络接口未就绪。 |
Failed to find the network interface or network interface is not ready. |
| 0x80340007 | 未能打开网络接口。 |
Failed to open the network interface. |
| 0x80340008 | 网络接口出现了不可恢复的内部故障。 |
Network interface has encountered an internal unrecoverable failure. |
| 0x80340009 | 网络接口上的多播列表已满。 |
The multicast list on the network interface is full. |
| 0x8034000A | 已尝试将重复的多播地址添加到该列表。 |
An attempt was made to add a duplicate multicast address to the list. |
| 0x8034000B | 已尝试删除从未添加的多播地址。 |
At attempt was made to remove a multicast address that was never added. |
| 0x8034000C | 网络接口已中止请求。 |
Netowork interface aborted the request. |
| 0x8034000D | 由于网络接口正在重置，无法处理该请求。 |
Network interface can not process the request because it is being reset. |
| 0x8034000F | 已尝试在网络接口上发送无效的数据包。 |
An attempt was made to send an invalid packet on a network interface. |
| 0x80340010 | 指定的请求为目标设备的无效操作。 |
The specified request is not a valid operation for the target device. |
| 0x80340011 | 网络接口未就绪，无法完成此操作。 |
Network interface is not ready to complete this operation. |
| 0x80340014 | 为此操作提交的缓冲区长度无效。 |
The length of the buffer submitted for this operation is not valid. |
| 0x80340015 | 用于此操作的数据无效。 |
The data used for this operation is not valid. |
| 0x80340016 | 为此操作提交的缓冲区长度太小。 |
The length of buffer submitted for this operation is too small. |
| 0x80340017 | 网络接口不支持此 OID (对象标识符) |
Network interface does not support this OID (Object Identifier) |
| 0x80340018 | 已删除网络接口。 |
The network interface has been removed. |
| 0x80340019 | 网络接口不支持此媒体类型。 |
Network interface does not support this media type. |
| 0x8034001A | 已尝试删除其他组件正在使用的令牌环组地址。 |
An attempt was made to remove a token ring group address that is in use by other components. |
| 0x8034001B | 已试图映射无法找到的文件。 |
An attempt was made to map a file that can not be found. |
| 0x8034001C | NDIS 尝试映射文件时出错。 |
An error occurred while NDIS tried to map the file. |
| 0x8034001D | 已试图映射已映射的文件。 |
An attempt was made to map a file that is alreay mapped. |
| 0x8034001E | 尝试分配硬件资源失败，原因是另一组件在使用该资源。 |
An attempt to allocate a hardware resource failed because the resource is used by another component. |
| 0x8034001F | I/O 操作失败，原因是网络媒体断开连接或无线访问点超出范围。 |
The I/O operation failed because network media is disconnected or wireless access point is out of range. |
| 0x80340022 | 请求中所使用的网络地址无效。 |
The network address used in the request is invalid. |
| 0x8034002A | 网络接口上的卸载操作已暂停。 |
The offload operation on the network interface has been paused. |
| 0x8034002B | 找不到网络接口。 |
Network interface was not found. |
| 0x8034002C | 不支持该结构中指定的修订号。 |
The revision number specified in the structure is not supported. |
| 0x8034002D | 此网络接口上不存在指定的端口。 |
The specified port does not exist on this network interface. |
| 0x8034002E | 此网络接口上指定端口的当前状态不支持所请求的操作。 |
The current state of the specified port on this network interface does not support the requested operation. |
| 0x8034002F | 微型端口适配器处于低电量状态。 |
The miniport adapter is in low power state. |
| 0x80340030 | 此操作要求重新初始化微型端口适配器。 |
This operation requires the miniport adapter to be reinitialized. |
| 0x803400BB | 网络接口不支持此请求。 |
Netword interface does not support this request. |
| 0x80342000 | 无线局域网接口处于自动配置模式下，它不支持请求的参数更改操作。 |
The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation. |
| 0x80342001 | 无线局域网接口忙，无法执行请求的操作。 |
The wireless local area network interface is busy and can not perform the requested operation. |
| 0x80342002 | 无线局域网接口电源关闭，它不支持请求的操作。 |
The wireless local area network interface is powered down and doesn't support the requested operation. |
| 0x80342003 | LAN 唤醒模式的列表已满。 |
The list of wake on LAN patterns is full. |
| 0x80342004 | 低电量协议卸载列表已满。 |
The list of low power protocol offloads is full. |
| 0x80342005 | 无线局域网接口现在无法在指定的通道上启动 AP。 |
The wireless local area network interface cannot start an AP on the specified channel right now. |
| 0x80342006 | 无线局域网接口现在无法在指定的波段上启动 AP。 |
The wireless local area network interface cannot start an AP on the specified band right now. |
| 0x80342007 | 由于监管原因，无线局域网接口无法在此通道上启动 AP。 |
The wireless local area network interface cannot start an AP on this channel due to regulatory reasons. |
| 0x80342008 | 由于监管原因，无线局域网接口无法在此波段上启动 AP。 |
The wireless local area network interface cannot start an AP on this band due to regulatory reasons. |
| 0x80370001 | 虚拟机正在其内存已分配给多个 NUMA 节点的情况下运行。除非虚拟机的性能异常缓慢，否则，这并不表示存在问题。如果遇到性能问题，可能需要修改 NUMA 配置。 |
A 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. |
| 0x80380001 | 由于存在坏扇区，因此再生操作无法从活动丛复制所有数据。 |
The regeneration operation was not able to copy all data from the active plexes due to bad sectors. |
| 0x80380002 | 未将一个或多个磁盘完全迁移到目标磁盘组。解决硬件问题之后，可能需要重新导入这些磁盘，也可能不需要重新导入。 |
One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems. |
| 0x80390001 | 未从 BCD 存储正确导入某些 BCD 项目。 |
Some BCD entries were not imported correctly from the BCD store. |
| 0x80390003 | 某些 BCD 项未与固件正确同步。 |
Some BCD entries were not synchronized correctly with the firmware. |
| 0x803A0001 | 虚拟存储子系统已生成一个错误。 |
The virtualization storage subsystem has generated an error. |
| 0x803C0100 | 已取消操作。 |
The operation was cancelled. |
| 0x803C0101 | 运行 PowerShell 脚本时出错。 |
An error occurred when running a PowerShell script. |
| 0x803C0102 | 与 PowerShell 运行时交互时出错。 |
An error occurred when interacting with PowerShell runtime. |
| 0x803C0103 | 脚本诊断托管主机中出错。 |
An error occurred in the Scripted Diagnostic Managed Host. |
| 0x803C0104 | 此疑难解答程序包不包含完成验证所需的验证工具。 |
The troubleshooting pack does not contain a required verifier to complete the verification. |
| 0x803C0106 | 组策略禁用了脚本的诊断。 |
Scripted diagnostics is disabled by group policy. |
| 0x803C0107 | 疑难解答程序包的信任验证已失败。 |
Trust validation of the troubleshooting pack failed. |
| 0x803C0109 | 不支持此版本的疑难解答程序包。 |
This version of the troubleshooting pack is not supported. |
| 0x803C010A | 找不到所需的资源。 |
A required resource cannot be loaded. |
| 0x803C010B | 疑难解答程序包报告了有关根本原因的信息，但没有添加根本原因。 |
The troubleshooting pack reported information for a root cause without adding the root cause. |
| 0x803D0000 | 输入数据未采用预期格式，或不具备预期值。 |
The input data was not in the expected format or did not have the expected value. |
| 0x803D0001 | 无法完成该操作，因为该对象因前一个错误而处于错误状态。 |
The operation could not be completed because the object is in a faulted state due to a previous error. |
| 0x803D0002 | 无法完成该操作，因为此操作将导致数值溢出。 |
The operation could not be completed because it would lead to numeric overflow. |
| 0x803D0003 | 由于对象的当前状态，禁止执行此操作。 |
The operation is not allowed due to the current state of the object. |
| 0x803D0004 | 操作已中止。 |
The operation was aborted. |
| 0x803D0005 | 远程终结点拒绝访问。 |
Access was denied by the remote endpoint. |
| 0x803D0006 | 该操作在分配的时间内未完成。 |
The operation did not complete within the time allotted. |
| 0x803D0007 | 已放弃该操作。 |
The operation was abandoned. |
| 0x803D0008 | 已超出配额。 |
A quota was exceeded. |
| 0x803D0009 | 信息在指定的语言中不可用。 |
The information was not available in the specified language. |
| 0x803D000A | 对所接收的数据执行的安全验证失败。 |
Security verification was not successful for the received data. |
| 0x803D000B | 该地址已被使用。 |
The address is already being used. |
| 0x803D000C | 该地址对此上下文无效。 |
The address is not valid for this context. |
| 0x803D000D | 远程终结点不存在或找不到。 |
The remote endpoint does not exist or could not be located. |
| 0x803D000E | 位于此位置的远程终结点当前不在服务中。 |
The remote endpoint is not currently in service at this location. |
| 0x803D000F | 远程终结点无法处理请求。 |
The remote endpoint could not process the request. |
| 0x803D0010 | 无法访问远程终结点。 |
The remote endpoint was not reachable. |
| 0x803D0011 | 远程终结点不支持此操作。 |
The operation was not supported by the remote endpoint. |
| 0x803D0012 | 由于重载，远端终结点无法处理此请求。 |
The remote endpoint is unable to process the request due to being overloaded. |
| 0x803D0013 | 从远端终结点收到包含错误的消息。 |
A message containing a fault was received from the remote endpoint. |
| 0x803D0014 | 与远程终结点之间的连接被终止。 |
The connection with the remote endpoint was terminated. |
| 0x803D0015 | HTTP 代理服务器无法处理请求。 |
The HTTP proxy server could not process the request. |
| 0x803D0016 | 访问被 HTTP 代理服务器拒绝。 |
Access was denied by the HTTP proxy server. |
| 0x803D0017 | 请求的功能在此平台上不可用。 |
The requested feature is not available on this platform. |
| 0x803D0018 | HTTP 代理服务器需要“基本”HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'basic'. |
| 0x803D0019 | HTTP 代理服务器需要“摘要式”HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'digest'. |
| 0x803D001A | HTTP 代理服务器需要 \"NTLM\" HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'NTLM'. |
| 0x803D001B | HTTP 代理服务器需要“协商”HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'negotiate'. |
| 0x803D001C | 远程终结点需要“基本”HTTP 身份验证方案。 |
The remote endpoint requires HTTP authentication scheme 'basic'. |
| 0x803D001D | 远程终结点需要“摘要式”HTTP 身份验证方案。 |
The remote endpoint requires HTTP authentication scheme 'digest'. |
| 0x803D001E | 远程终结点需要 \"NTLM\" HTTP 身份验证方案。 |
The remote endpoint requires HTTP authentication scheme 'NTLM'. |
| 0x803D001F | 远程终结点需要“协商”HTTP 身份验证方案。 |
The remote endpoint requires HTTP authentication scheme 'negotiate'. |
| 0x803D0020 | 终结点地址 URL 无效。 |
The endpoint address URL is invalid. |
| 0x803D0021 | Windows Web 服务框架中出现无法识别的错误。 |
Unrecognized error occurred in the Windows Web Services framework. |
| 0x803D0022 | 安全令牌被服务器拒绝，因为它已过期。 |
A security token was rejected by the server because it has expired. |
| 0x803D0023 | Windows Web 服务框架中的安全操作失败。 |
A security operation failed in the Windows Web Services framework. |
| 0x803E0100 | 已关闭通知通道。 |
The notification channel has already been closed. |
| 0x803E0101 | 通知通道请求未成功完成。 |
The notification channel request did not complete successfully. |
| 0x803E0102 | 提供的应用程序标识符无效。 |
The application identifier provided is invalid. |
| 0x803E0103 | 提供的应用程序标识符的通知通道请求正在进行中。 |
A notification channel request for the provided application identifier is in progress. |
| 0x803E0104 | 通道标识符已连接到另一个应用程序终结点。 |
The channel identifier is already tied to another application endpoint. |
| 0x803E0105 | 通知平台不可用。 |
The notification platform is unavailable. |
| 0x803E0106 | 通知已经发布。 |
The notification has already been posted. |
| 0x803E0107 | 通知已经隐藏。 |
The notification has already been hidden. |
| 0x803E0108 | 通知无法隐藏，除非它已经显示。 |
The notification cannot be hidden until it has been shown. |
| 0x803E0109 | 云通知已关闭。 |
Cloud notifications have been turned off. |
| 0x803E0110 | 应用程序不具有云通知功能。 |
The application does not have the cloud notification capability. |
| 0x803E0111 | 设置会阻止通知传递。 |
Settings prevent the notification from being delivered. |
| 0x803E0112 | 应用程序功能会阻止通知传递。 |
Application capabilities prevent the notification from being delivered. |
| 0x803E0113 | 此应用程序不具有 Internet 访问功能。 |
The application does not have the internet access capability. |
| 0x803E0114 | 设置会阻止通知类型传递。 |
Settings prevent the notification type from being delivered. |
| 0x803E0115 | 通知内容的大小过大。 |
The size of the notification content is too large. |
| 0x803E0116 | 通知标签的大小过大。 |
The size of the notification tag is too large. |
| 0x803E0117 | 通知平台没有相应的资源权限。 |
The notification platform doesn't have appropriate privilege on resources. |
| 0x803E0118 | 通知平台发现应用程序已注册。 |
The notification platform found application is already registered. |
| 0x803E0119 | 应用程序后台任务不具有推送通知功能。 |
The application background task does not have the push notification capability. |
| 0x803E011A | 通知平台无法检索连接到云通知服务所需的身份验证凭据。 |
The notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service. |
| 0x803E011B | 通知平台无法连接到云通知服务。 |
The notification platform is unable to connect to the cloud notification service. |
| 0x803E011C | 通知平台无法初始化锁屏更新的回调。 |
The notification platform is unable to initialize a callback for lock screen updates. |
| 0x803E0120 | 用于计划通知的开发人员 ID 的大小过大。 |
The size of the developer id for scheduled notification is too large. |
| 0x803E012A | 通知标记不是字母数字标记。 |
The notification tag is not alphanumeric. |
| 0x803E012B | 通知平台已收到无效 HTTP 状态代码，而不是用于轮询的 2xx。 |
The notification platform has received invalid HTTP status code other than 2xx for polling. |
| 0x803E0200 | 通知平台已用完表示层会话。 |
The notification platform has run out of presentation layer sessions. |
| 0x803E0201 | 通知平台拒绝图像下载请求，原因是系统处于节电模式。 |
The notification platform rejects image download request due to system in power save mode. |
| 0x803E0202 | 通知平台在其缓存中没有请求的图像。 |
The notification platform doesn't have the requested image in its cache. |
| 0x803E0203 | 通知平台无法完成所有请求的图像。 |
The notification platform cannot complete all of requested image. |
| 0x803E0204 | 从通知平台下载的云图像无效。 |
A cloud image downloaded from the notification platform is invalid. |
| 0x803E0205 | 作为筛选器提供的通知 ID 与通知平台维护的通知 ID 相符。 |
Notification Id provided as filter is matched with what the notification platform maintains. |
| 0x803E0206 | 通知回调接口已注册。 |
Notification callback interface is already registered. |
| 0x803E0207 | Toast 通知已丢弃，未向用户显示。 |
Toast Notification was dropped without being displayed to the user. |
| 0x803E0208 | 通知平台没有正确权限，无法完成请求。 |
The notification platform does not have the proper privileges to complete the request. |
| 0x803E0209 | 通知组的大小太大。 |
The size of the notification group is too large. |
| 0x803E020A | 该通知组不是字母数字的通知租。 |
The notification group is not alphanumeric. |
| 0x803E020B | 由于策略设置，已对应用程序禁用云通知。 |
Cloud notifications have been disabled for the application due to a policy setting. |
| 0x80400000 | 输入数据只能按照时间先后顺序进行处理。 |
Input data cannot be processed in the non-chronological order. |
| 0x80400001 | 请求的操作无法在回调或事件处理程序中执行。 |
Requested operation cannot be performed inside the callback or event handler. |
| 0x80400002 | 无法处理输入，因为正在与另一个指针类型进行交互。 |
Input cannot be processed because there is ongoing interaction with another pointer type. |
| 0x80400003 | 输入数据包中的一个或多个字段无效。 |
One or more fields in the input packet are invalid. |
| 0x80400004 | 帧中的数据包不一致。可能是由于指针 ID 不唯一，或者时间戳、帧 ID、指针类型或源设备中存在差异。 |
Packets 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. |
| 0x80400005 | 帧的历史记录不一致。可能是由于指针 ID、指针类型或源设备不匹配，或者帧 ID 不唯一，也可能是时间戳的顺序有错误。 |
The 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. |
| 0x80400006 | 无法检索有关输入设备的信息。 |
Failed to retrieve information about the input device. |
| 0x80400007 | 坐标系统转换功能转换数据失败。 |
Coordinate system transformation failed to transform the data. |
| 0x80400008 | 该属性不受支持，或不能由输入设备正确报告。 |
The property is not supported or not reported correctly by the input device. |
| 0x80548201 | 上下文未激活。 |
Context is not activated. |
| 0x80548202 | 插入的 SIM 错误。 |
Bad SIM is inserted. |
| 0x80548203 | 请求的数据类不可用。 |
Requested data class is not avaialable. |
| 0x80548204 | 访问点名称(APN)或拨号号码不正确。 |
Access point name (APN) or Access string is incorrect. |
| 0x80548205 | 已达到最大激活上下文数目。 |
Max activated contexts have reached. |
| 0x80548206 | 设备处于数据包分离状态。 |
Device is in packet detach state. |
| 0x80548207 | 提供程序不可见。 |
Provider is not visible. |
| 0x80548208 | 无线电收发器已关闭。 |
Radio is powered off. |
| 0x80548209 | MBN 订阅未激活。 |
MBN subscription is not activated. |
| 0x8054820A | 未插入 SIM。 |
SIM is not inserted. |
| 0x8054820B | 语音呼叫正在进行。 |
Voice call in progress. |
| 0x8054820C | 可见提供程序缓存无效。 |
Visible provider cache is invalid. |
| 0x8054820D | 未注册设备。 |
Device is not registered. |
| 0x8054820E | 找不到提供程序。 |
Providers not found. |
| 0x8054820F | 不支持 Pin。 |
Pin is not supported. |
| 0x80548210 | Pin 是必需的。 |
Pin is required. |
| 0x80548211 | PIN 处于禁用状态。 |
PIN is disabled. |
| 0x80548212 | 常规故障。 |
Generic Failure. |
| 0x80548218 | 配置文件无效。 |
Profile is invalid. |
| 0x80548219 | 存在默认配置文件。 |
Default profile exist. |
| 0x80548220 | 不支持 SMS 编码。 |
SMS encoding is not supported. |
| 0x80548221 | 不支持 SMS 筛选器。 |
SMS filter is not supported. |
| 0x80548222 | 使用的 SMS 内存索引无效。 |
Invalid SMS memory index is used. |
| 0x80548223 | 不支持 SMS 语言。 |
SMS language is not supported. |
| 0x80548224 | 出现 SMS 内存故障。 |
SMS memory failure occurred. |
| 0x80548225 | 发生 SMS 网络超时。 |
SMS network timeout happened. |
| 0x80548226 | 使用了未知的 SMSC 地址。 |
Unknown SMSC address is used. |
| 0x80548227 | 不支持 SMS 格式。 |
SMS format is not supported. |
| 0x80548228 | 不允许 SMS 操作。 |
SMS operation is not allowed. |
| 0x80548229 | 设备 SMS 内存已满。 |
Device SMS memory is full. |
| 0x80550001 | Windows 无法评估此 EAS 策略，因为该策略不是由操作系统进行管理。 |
Windows cannot evaluate this EAS policy since this is not managed by the operating system. |
| 0x80550002 | 如果由用户执行某些操作，则系统可以符合此 EAS 策略。 |
The system can be made compliant to this EAS policy if certain actions are performed by the user. |
| 0x80550003 | 系统无法强制实施正在评估的 EAS 策略。 |
The EAS policy being evaluated cannot be enforced by the system. |
| 0x80550004 | 无法评估用户的 EAS 密码策略，因为用户使用的是空密码。 |
EAS password policies for the user cannot be evaluated as the user has a blank password. |
| 0x80550005 | 无法符合 EAS 密码过期策略，因为密码过期时间间隔小于系统的最小密码时间间隔。 |
EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system. |
| 0x80550006 | 不允许用户更改其密码。 |
The user is not allowed to change her password. |
| 0x80550007 | 无法评估 EAS 密码策略，因为一个或多个管理员使用的是空密码。 |
EAS password policies cannot be evaluated as one or more admins have blank passwords. |
| 0x80550008 | 不允许一个或多个管理员更改其密码。 |
One or more admins are not allowed to change their password. |
| 0x80550009 | 存在其他标准用户(不允许其更改密码)。 |
There are other standard users present who are not allowed to change their password. |
| 0x8055000A | 至少有一个管理员的已连接帐户提供程序无法强制实施 EAS 密码策略。 |
The EAS password policy cannot be enforced by the connected account provider of at least one administrator. |
| 0x8055000B | 至少有一个管理员的已连接帐户密码需要更改以符合 EAS 密码策略。 |
There is at least one administrator whose connected account password needs to be changed for EAS password policy compliance. |
| 0x8055000C | 当前用户的已连接帐户提供程序无法强制实施 EAS 密码策略。 |
The EAS password policy cannot be enforced by the connected account provider of the current user. |
| 0x8055000D | 当前用户的已连接帐户密码需要更改以符合 EAS 密码策略。 |
The connected account password of the current user needs to be changed for EAS password policy compliance. |
| 0x80630001 | 未安装 IPv6 协议。 |
The IPv6 protocol is not installed. |
| 0x80630002 | 组件尚未初始化。 |
The compoment has not been initialized. |
| 0x80630003 | 无法启动请求的服务。 |
The required service canot be started. |
| 0x80630004 | P2P 协议未获得在此 OS 上运行的许可。 |
The P2P protocol is not licensed to run on this OS. |
| 0x80630010 | 图表句柄无效。 |
The graph handle is invalid. |
| 0x80630011 | 图形数据库名称已更改。 |
The graph database name has changed. |
| 0x80630012 | 具有相同 ID 的图表已存在。 |
A graph with the same ID already exists. |
| 0x80630013 | 此图表未准备就绪。 |
The graph is not ready. |
| 0x80630014 | 此图表正在关闭。 |
The graph is shutting down. |
| 0x80630015 | 此图表仍在使用中。 |
The graph is still in use. |
| 0x80630016 | 此图此数据库已损坏。 |
The graph database is corrupt. |
| 0x80630017 | 使用了过多的属性。 |
Too many attributes have been used. |
| 0x80630103 | 无法找到连接。 |
The connection can not be found. |
| 0x80630106 | 对等机尝试与其自身连接。 |
The peer attempted to connect to itself. |
| 0x80630107 | 对等机已在侦听连接。 |
The peer is already listening for connections. |
| 0x80630108 | 找不到节点。 |
The node was not found. |
| 0x80630109 | 连接尝试失败。 |
The Connection attempt failed. |
| 0x8063010A | 对等机连接无法进行身份验证。 |
The peer connection could not be authenticated. |
| 0x8063010B | 连接遭到拒绝。 |
The connection was refused. |
| 0x80630201 | 对等机名称分类器过长。 |
The peer name classifier is too long. |
| 0x80630202 | 创建的标识数目已达到最大。 |
The maximum number of identities have been created. |
| 0x80630203 | 无法访问密钥。 |
Unable to access a key. |
| 0x80630204 | 组已经存在。 |
The group already exists. |
| 0x80630301 | 无法找到请求的记录。 |
The requested record could not be found. |
| 0x80630302 | 数据库访问遭拒绝。 |
Access to the database was denied. |
| 0x80630303 | 无法初始化数据库。 |
The Database could not be initialized. |
| 0x80630304 | 记录过长。 |
The record is too big. |
| 0x80630305 | 数据库已经存在。 |
The database already exists. |
| 0x80630306 | 找不到数据库。 |
The database could not be found. |
| 0x80630401 | 无法找到标识。 |
The identity could not be found. |
| 0x80630501 | 无法找到事件句柄。 |
The event handle could not be found. |
| 0x80630601 | 无效的搜索。 |
Invalid search. |
| 0x80630602 | 搜索属性无效。 |
The search atributes are invalid. |
| 0x80630701 | 邀请不可信。 |
The invitiation is not trusted. |
| 0x80630703 | 证书链过长。 |
The certchain is too long. |
| 0x80630705 | 时间段无效。 |
The time period is invalid. |
| 0x80630706 | 检测到循环的证书链。 |
A circular cert chain was detected. |
| 0x80630801 | 证书存储已损坏。 |
The certstore is corrupted. |
| 0x80631001 | 指定的 PNRP 云不存在。 |
The specified PNRP cloud deos not exist. |
| 0x80631005 | 云名称不明确。 |
The cloud name is ambiguous. |
| 0x80632010 | 记录无效。 |
The record is invlaid. |
| 0x80632020 | 未授权。 |
Not authorized. |
| 0x80632021 | 密码不满足策略要求。 |
The password does not meet policy requirements. |
| 0x80632030 | 记录验证已延迟。 |
The record validation has been defered. |
| 0x80632040 | 组属性无效。 |
The group properies are invalid. |
| 0x80632050 | 对等机名称无效。 |
The peername is invalid. |
| 0x80632060 | 分类器无效。 |
The classifier is invalid. |
| 0x80632070 | 友好名称无效。 |
The friendly name is invalid. |
| 0x80632071 | 无效的角色属性。 |
Invalid role property. |
| 0x80632072 | 分类器属性无效。 |
Invalid classifer property. |
| 0x80632080 | 无效的记录过期日期。 |
Invlaid record expiration. |
| 0x80632081 | 无效的凭据信息。 |
Invlaid credential info. |
| 0x80632082 | 无效的凭据。 |
Invalid credential. |
| 0x80632083 | 无效的记录大小。 |
Invalid record size. |
| 0x80632090 | 不支持的版本。 |
Unsupported version. |
| 0x80632091 | 组未就绪。 |
The group is not ready. |
| 0x80632092 | 组仍在使用中。 |
The group is still in use. |
| 0x80632093 | 组无效。 |
The group is invalid. |
| 0x80632095 | 没有成员连接。 |
There are no member connections. |
| 0x80632096 | 无法侦听。 |
Unable to listen. |
| 0x806320A0 | 标识不存在。 |
The identity does not exist. |
| 0x806320A1 | 此服务无法使用。 |
The service is not availible. |
| 0x80634001 | 对等机名称无法转换为 DNS pnrp 名称。 |
The peername could not be converted to a DNS pnrp name. |
| 0x80634002 | 无效的对等主机名。 |
Invalid peer host name. |
| 0x80634003 | 无法找到其他数据。 |
No more data could be found. |
| 0x80634005 | 现有的对等机名称已注册。 |
The existing peer name is already registered. |
| 0x80636001 | 无法找到联系人。 |
THe contact could not be found. |
| 0x80637000 | 用户已取消应用邀请请求。 |
The app invite request was cancelled by the user. |
| 0x80637001 | 没有收到邀请回复。 |
No response of the invite was received. |
| 0x80637003 | 用户未登录至无服务器状态。 |
User is not signed into serverless presence. |
| 0x80637004 | 用户拒绝隐私策略提示。 |
The user declined the privacy policy prompt. |
| 0x80637005 | 出现超时。 |
A timeout occurred. |
| 0x80637007 | 地址无效。 |
The address is invalid. |
| 0x80637008 | 所需的防火墙异常已禁用。 |
A required firewall exception is disabled. |
| 0x80637009 | 服务被防火墙策略阻止。 |
The service is blocked by a firewall policy. |
| 0x8063700A | 防火墙异常已禁用。 |
Firewall exceptions are disabled. |
| 0x8063700B | 用户拒绝启用防火墙异常。 |
The user declined to enable the firewall exceptions. |
| 0x80650001 | 给定的属性句柄在此服务器上无效。 |
The attribute handle given was not valid on this server. |
| 0x80650002 | 无法读取属性。 |
The attribute cannot be read. |
| 0x80650003 | 无法写入属性。 |
The attribute cannot be written. |
| 0x80650004 | 属性 PDU 无效。 |
The attribute PDU was invalid. |
| 0x80650005 | 属性需要进行身份验证，然后才能读取或写入。 |
The attribute requires authentication before it can be read or written. |
| 0x80650006 | 属性服务器不支持从客户端接收的请求。 |
Attribute server does not support the request received from the client. |
| 0x80650007 | 指定的偏移量超出了属性的结尾。 |
Offset specified was past the end of the attribute. |
| 0x80650009 | 排队的准备写入操作过多。 |
Too many prepare writes have been queued. |
| 0x8065000A | 在给定的属性句柄范围内未找到任何属性。 |
No attribute found within the given attribute handle range. |
| 0x8065000B | 使用读取 BLOB 请求无法读取或写入属性。 |
The attribute cannot be read or written using the Read Blob Request. |
| 0x8065000C | 用于加密此链接的加密密钥大小不足。 |
The Encryption Key Size used for encrypting this link is insufficient. |
| 0x8065000D | 此属性值长度对于此操作无效。 |
The attribute value length is invalid for the operation. |
| 0x8065000E | 请求的属性请求遇到不太可能发生的错误，因此无法根据请求完成。 |
The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. |
| 0x8065000F | 属性需要进行加密，然后才能读取或写入。 |
The attribute requires encryption before it can be read or written. |
| 0x80650010 | 属性类型不是较高层规范所定义的支持的分组属性。 |
The attribute type is not a supported grouping attribute as defined by a higher layer specification. |
| 0x80650011 | 资源不足，无法完成请求。 |
Insufficient Resources to complete the request. |
| 0x80651000 | 接收到位于预留范围内的错误。 |
An error that lies in the reserved range has been received. |
| 0x80660001 | PortCl 无法找到声称支持 IMiniportAudioEngineNode 的微型端口驱动程序所暴露的音频引擎节点。 |
PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode. |
| 0x80660002 | HD 音频小组件遇到意外的空连接列表。 |
HD Audio widget encountered an unexpected empty connection list. |
| 0x80660003 | HD 音频小组件不支持连接列表参数。 |
HD Audio widget does not support the connection list parameter. |
| 0x80660004 | 未成功创建任何 HD 音频子设备。 |
No HD Audio subdevices were successfully created. |
| 0x80660005 | 链接的列表中遇到意外的 NULL 指针。 |
An unexpected NULL pointer was encountered in a linked list. |
| 0x80670001 | 乐观锁定失败。数据如果自读取以来已发生更改，则无法进行更新。 |
Optimistic locking failure. Data cannot be updated if it has changed since it was read. |
| 0x80670002 | 预定义语句至少已执行一次，但未运行到完成或重置。这可能会导致非空闲等待。 |
A prepared statement has been stepped at least once but not run to completion or reset. This may result in busy waits. |
| 0x80670003 | StateRepository 配置无效。 |
The StateRepository configuration is not valid. |
| 0x80670004 | 该 StateRepository 架构版本未知。 |
The StateRepository schema version is not known. |
| 0x80670005 | StateRepository 字典无效。 |
A StateRepository dictionary is not valid. |
| 0x80670006 | 请求失败，因为 StateRepository 主动阻止了请求。 |
The request failed because the StateRepository is actively blocking requests. |
| 0x80670007 | 数据库文件被锁定。将重试该请求。 |
The database file is locked. The request will be retried. |
| 0x80670008 | 由于另一个进程正忙于恢复数据库，数据库文件被锁定。将重试该请求。 |
The database file is locked because another process is busy recovering the database. The request will be retried. |
| 0x80670009 | 数据库中的表被锁定。将重试该请求。 |
A table in the database is locked. The request will be retried. |
| 0x8067000A | 数据库的共享缓存已被另一个连接锁定。将重试该请求。 |
The shared cache for the database is locked by another connection. The request will be retried. |
| 0x8067000B | 需要进行事务处理才能执行该请求操作。 |
A transaction is required to perform the request operation. |
| 0x8067000C | 数据库文件已锁定。请求超过了允许的阈值。 |
The database file is locked. The request has exceeded the allowed threshold. |
| 0x8067000D | 由于另一个进程正忙于恢复数据库，数据库文件已锁定。请求超过了允许的阈值。 |
The database file is locked because another process is busy recovering the database. The request has exceeded the allowed threshold. |
| 0x8067000E | 数据库中的表已锁定。请求超过了允许的阈值。 |
A table in the database is locked. The request has exceeded the allowed threshold. |
| 0x8067000F | 另一个连接锁定了数据库的共享缓存。请求超过了允许的阈值。 |
The shared cache for the database is locked by another connection. The request has exceeded the allowed threshold. |
| 0x80670010 | StateRepository 服务停止事件正在进行。 |
The StateRepository service Stop event is in progress. |
| 0x80820001 | 启动文件过小，无法支持持续快照。 |
The bootfile is too small to support persistent snapshots. |
| 0x80820002 | 激活此卷上的永久性快照所用时间超过了允许的时间。 |
Activation of persistent snapshots on this volume took longer than was allowed. |
| 0x80830001 | 指定的卷不支持存储层。 |
The specified volume does not support storage tiers. |
| 0x80830002 | 存储层管理服务检测到指定的卷正在被卸载。 |
The Storage Tiers Management service detected that the specified volume is in the process of being dismounted. |
| 0x80830003 | 在卷上找不到指定的存储层。请确认存储层名称是有效的。 |
The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid. |
| 0x80830004 | 指定的文件标识符不是卷上的有效文件标识符。 |
The file identifier specified is not valid on the volume. |
| 0x80830005 | 必须在拥有元数据卷的群集节点上调用存储层操作。 |
Storage tier operations must be called on the clustering node that owns the metadata volume. |
| 0x80830006 | 存储层管理服务已在优化指定卷上的存储层。 |
The Storage Tiers Management service is already optimizing the storage tiers on the specified volume. |
| 0x80830007 | 无法将请求的对象类型分配给存储层。 |
The requested object type cannot be assigned to a storage tier. |
| 0x80830008 | 所请求的文件未固定到层。 |
The requested file is not pinned to a tier. |
| 0x80830009 | 卷不是分层卷。 |
The volume is not a tiered volume. |
| 0x8083000A | 所请求的属性不存在于指定的文件或目录中。 |
The requested attribute is not present on the specified file or directory. |
| 0x80860001 | 身份验证目标无效或配置不正确。 |
Authentication target is invalid or not configured correctly. |
| 0x80860002 | 由于用户接受了“使用条款”，因此你的应用程序无法获得联机 ID 属性。 |
Your application cannot get the Online Id properties due to the Terms of Use accepted by the user. |
| 0x80860003 | 应用程序请求身份验证令牌被禁用或者配置错误。 |
The application requesting authentication tokens is either disabled or incorrectly configured. |
| 0x80860004 | 登录前必须更新联机 ID 密码。 |
Online Id password must be updated before signin. |
| 0x80860005 | 登录前必须更新联机 ID 帐户属性。 |
Online Id account properties must be updated before signin. |
| 0x80860006 | 为了帮助保护你的联机 ID 帐户，你必须重新登录。 |
To help protect your Online Id account you must signin again. |
| 0x80860007 | 联机 ID 帐户已锁定，因为尝试登录的次数过多。 |
Online Id account was locked because there have been too many attempts to sign in. |
| 0x80860008 | 联机 ID 帐户需要得到父母许可才能继续。 |
Online Id account requires parental consent before proceeding. |
| 0x80860009 | 尚未验证联机 ID 登录名。需要验证电子邮件才能登录。 |
Online Id signin name is not yet verified. Email verification is required before signin. |
| 0x8086000A | 我们注意到你的联机 ID 帐户中存在一些异常活动。你需要执行一些操作以确保你的帐户没有被他人使用。 |
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. |
| 0x8086000B | 我们检测到你的联机 ID 帐户中存在一些可疑活动。为了帮助保护你帐户的安全，我们已暂时阻止了你的帐户。 |
We detected some suspicious activity with your Online Id account. To help protect you, we've temporarily blocked your account. |
| 0x8086000C | 需要用户交互才能进行身份验证。 |
User interaction is required for authentication. |
| 0x8086000D | 用户已达到每个用户的最大设备关联数限制。 |
User has reached the maximum device associations per user limit. |
| 0x8086000E | 由于已连接用户帐户，无法从应用程序中注销。 |
Cannot sign out from the application since the user account is connected. |
| 0x8086000F | 此操作需要验证用户身份。 |
User authentication is required for this operation. |
| 0x80860010 | 我们希望确保这确实是你。身份验证需要用户进行交互操作。 |
We want to make sure this is you. User interaction is required for authentication. |
| 0x80B00001 | 无法从 ARM 体系结构设备创建新的进程。 |
Could not create new process from ARM architecture device. |
| 0x80B00002 | 无法附加到 ARM 体系结构设备的应用程序进程。 |
Could not attach to the application process from ARM architecture device. |
| 0x80B00003 | 无法连接到 ARM 体系结构设备的 dbgsrv 服务器。 |
Could not connect to dbgsrv server from ARM architecture device. |
| 0x80B00004 | 无法从 ARM 体系结构设备启动 dbgsrv 服务器。 |
Could not start dbgsrv server from ARM architecture device. |
| 0x80E70001 | 指定的容错域类型或最小/最大容错域类型的组合无效。 |
The specified fault domain type or combination of minimum / maximum fault domain type is not valid. |
| 0x80E70002 | 发生存储空间内部错误。 |
A Storage Spaces internal error occurred. |
| 0x80E70003 | 指定的复原类型无效。 |
The specified resiliency type is not valid. |
| 0x80E70004 | 存储池不支持物理磁盘的扇区大小。 |
The physical disk's sector size is not supported by the storage pool. |
| 0x80E70006 | 请求的冗余已超出支持的值的范围。 |
The requested redundancy is outside of the supported range of values. |
| 0x80E70007 | 请求的数据副本数已超出值的支持范围。 |
The number of data copies requested is outside of the supported range of values. |
| 0x80E70008 | ParityLayout 的值已超出值的支持范围。 |
The value for ParityLayout is outside of the supported range of values. |
| 0x80E70009 | 交错长度的值不在受支持的值范围内或者不是 2 的幂。 |
The value for interleave length is outside of the supported range of values or is not a power of 2. |
| 0x80E7000A | 指定的列数已超出值的支持范围。 |
The number of columns specified is outside of the supported range of values. |
| 0x80E7000B | 没有足够的物理磁盘空间完成请求的操作。 |
There were not enough physical disks to complete the requested operation. |
| 0x80E7000C | 有扩展的错误信息可用。 |
Extended error information is available. |
| 0x80E7000D | 指定的预配类型无效。 |
The specified provisioning type is not valid. |
| 0x80E7000E | 分配大小不在受支持的值范围内。 |
The allocation size is outside of the supported range of values. |
| 0x80E7000F | 此虚拟磁盘不支持外壳识别。 |
Enclosure awareness is not supported for this virtual disk. |
| 0x80E70010 | 写缓存大小不在受支持的值范围内。 |
The write cache size is outside of the supported range of values. |
| 0x80E70011 | 组数目的值不在受支持的值范围内。 |
The value for number of groups is outside of the supported range of values. |
| 0x80E70012 | 物理磁盘的 OperationalState 对此操作无效。 |
The OperationalState of the physical disk is invalid for this operation. |
| 0x83750001 | 不支持的格式。 |
Unsupported format. |
| 0x83750002 | XML 无效。 |
Invalid XML. |
| 0x83750003 | 缺少必需元素。 |
Missing required element. |
| 0x83750004 | 缺少必需属性。 |
Missing required attribute. |
| 0x83750005 | 异常内容。 |
Unexpected content. |
| 0x83750006 | 资源过大。 |
Resource too large. |
| 0x83750007 | JSON 字符串无效。 |
Invalid JSON string. |
| 0x83750008 | JSON 数字无效。 |
Invalid JSON number. |
| 0x83750009 | 未找到 JSON 值。 |
JSON value not found. |
| 0x83760001 | 由协议执行的操作无效。 |
Invalid operation performed by the protocol. |
| 0x83760002 | 特定协议操作的数据格式无效。 |
Invalid data format for the specific protocol operation. |
| 0x83760003 | 不支持协议扩展。 |
Protocol extensions are not supported. |
| 0x83760004 | 不支持子协议。 |
Subrotocol is not supported. |
| 0x83760005 | 协议版本不正确。 |
Incorrect protocol version. |
| 0x87AF0001 | SQL 错误或缺少数据库 |
SQL error or missing database |
| 0x87AF0002 | SQLite 中的内部逻辑错误 |
Internal logic error in SQLite |
| 0x87AF0003 | 访问权限被拒绝 |
Access permission denied |
| 0x87AF0004 | 回调例程已请求中止 |
Callback routine requested an abort |
| 0x87AF0005 | 数据库文件已锁定 |
The database file is locked |
| 0x87AF0006 | 数据库中的表已锁定 |
A table in the database is locked |
| 0x87AF0007 | malloc() 失败 |
A malloc() failed |
| 0x87AF0008 | 尝试写入只读数据库 |
Attempt to write a readonly database |
| 0x87AF0009 | 操作由 sqlite3_interrupt() 终止 |
Operation terminated by sqlite3_interrupt() |
| 0x87AF000A | 出现某种类型的磁盘 I/O 错误 |
Some kind of disk I/O error occurred |
| 0x87AF000B | 数据库磁盘映像格式错误 |
The database disk image is malformed |
| 0x87AF000C | sqlite3_file_control() 中的未知操作代码 |
Unknown opcode in sqlite3_file_control() |
| 0x87AF000D | 由于数据库已满，插入失败 |
Insertion failed because database is full |
| 0x87AF000E | 无法打开数据库文件 |
Unable to open the database file |
| 0x87AF000F | 数据库锁协议错误 |
Database lock protocol error |
| 0x87AF0010 | 数据库是空的 |
Database is empty |
| 0x87AF0011 | 数据库架构已更改 |
The database schema changed |
| 0x87AF0012 | 字符串或 BLOB 超过大小限制 |
String or BLOB exceeds size limit |
| 0x87AF0013 | 由于约束冲突而中止 |
Abort due to constraint violation |
| 0x87AF0014 | 数据类型不匹配 |
Data type mismatch |
| 0x87AF0015 | 不正确地使用了库 |
Library used incorrectly |
| 0x87AF0016 | 使用主机上不支持的 OS 功能 |
Uses OS features not supported on host |
| 0x87AF0017 | 授权被拒绝 |
Authorization denied |
| 0x87AF0018 | 辅助数据库格式错误 |
Auxiliary database format error |
| 0x87AF0019 | sqlite3_bind 的第二个参数超出范围 |
2nd parameter to sqlite3_bind out of range |
| 0x87AF001A | 打开的文件不是数据库文件 |
File opened that is not a database file |
| 0x87AF001B | sqlite3_log() 发出的通知 |
Notifications from sqlite3_log() |
| 0x87AF001C | sqlite3_log() 发出的警告 |
Warnings from sqlite3_log() |
| 0x87AF0064 | sqlite3_step() 已准备好另一行 |
sqlite3_step() has another row ready |
| 0x87AF0065 | sqlite3_step() 已完成执行 |
sqlite3_step() has finished executing |
| 0x87AF0105 | SQLITE_BUSY_RECOVERY |
SQLITE_BUSY_RECOVERY |
| 0x87AF0106 | SQLITE_LOCKED_SHAREDCACHE |
SQLITE_LOCKED_SHAREDCACHE |
| 0x87AF0108 | SQLITE_READONLY_RECOVERY |
SQLITE_READONLY_RECOVERY |
| 0x87AF010A | SQLITE_IOERR_READ |
SQLITE_IOERR_READ |
| 0x87AF010B | SQLITE_CORRUPT_VTAB |
SQLITE_CORRUPT_VTAB |
| 0x87AF010E | SQLITE_CANTOPEN_NOTEMPDIR |
SQLITE_CANTOPEN_NOTEMPDIR |
| 0x87AF0113 | SQLITE_CONSTRAINT_CHECK |
SQLITE_CONSTRAINT_CHECK |
| 0x87AF011B | SQLITE_NOTICE_RECOVER_WAL |
SQLITE_NOTICE_RECOVER_WAL |
| 0x87AF011C | SQLITE_WARNING_AUTOINDEX |
SQLITE_WARNING_AUTOINDEX |
| 0x87AF0204 | SQLITE_ABORT_ROLLBACK |
SQLITE_ABORT_ROLLBACK |
| 0x87AF0205 | SQLITE_BUSY_SNAPSHOT |
SQLITE_BUSY_SNAPSHOT |
| 0x87AF0208 | SQLITE_READONLY_CANTLOCK |
SQLITE_READONLY_CANTLOCK |
| 0x87AF020A | SQLITE_IOERR_SHORT_READ |
SQLITE_IOERR_SHORT_READ |
| 0x87AF020E | SQLITE_CANTOPEN_ISDIR |
SQLITE_CANTOPEN_ISDIR |
| 0x87AF0213 | SQLITE_CONSTRAINT_COMMITHOOK |
SQLITE_CONSTRAINT_COMMITHOOK |
| 0x87AF021B | SQLITE_NOTICE_RECOVER_ROLLBACK |
SQLITE_NOTICE_RECOVER_ROLLBACK |
| 0x87AF0308 | SQLITE_READONLY_ROLLBACK |
SQLITE_READONLY_ROLLBACK |
| 0x87AF030A | SQLITE_IOERR_WRITE |
SQLITE_IOERR_WRITE |
| 0x87AF030E | SQLITE_CANTOPEN_FULLPATH |
SQLITE_CANTOPEN_FULLPATH |
| 0x87AF0313 | SQLITE_CONSTRAINT_FOREIGNKEY |
SQLITE_CONSTRAINT_FOREIGNKEY |
| 0x87AF0408 | SQLITE_READONLY_DBMOVED |
SQLITE_READONLY_DBMOVED |
| 0x87AF040A | SQLITE_IOERR_FSYNC |
SQLITE_IOERR_FSYNC |
| 0x87AF040E | SQLITE_CANTOPEN_CONVPATH |
SQLITE_CANTOPEN_CONVPATH |
| 0x87AF0413 | SQLITE_CONSTRAINT_FUNCTION |
SQLITE_CONSTRAINT_FUNCTION |
| 0x87AF050A | SQLITE_IOERR_DIR_FSYNC |
SQLITE_IOERR_DIR_FSYNC |
| 0x87AF0513 | SQLITE_CONSTRAINT_NOTNULL |
SQLITE_CONSTRAINT_NOTNULL |
| 0x87AF060A | SQLITE_IOERR_TRUNCATE |
SQLITE_IOERR_TRUNCATE |
| 0x87AF0613 | SQLITE_CONSTRAINT_PRIMARYKEY |
SQLITE_CONSTRAINT_PRIMARYKEY |
| 0x87AF070A | SQLITE_IOERR_FSTAT |
SQLITE_IOERR_FSTAT |
| 0x87AF0713 | SQLITE_CONSTRAINT_TRIGGER |
SQLITE_CONSTRAINT_TRIGGER |
| 0x87AF080A | SQLITE_IOERR_UNLOCK |
SQLITE_IOERR_UNLOCK |
| 0x87AF0813 | SQLITE_CONSTRAINT_UNIQUE |
SQLITE_CONSTRAINT_UNIQUE |
| 0x87AF090A | SQLITE_IOERR_RDLOCK |
SQLITE_IOERR_RDLOCK |
| 0x87AF0913 | SQLITE_CONSTRAINT_VTAB |
SQLITE_CONSTRAINT_VTAB |
| 0x87AF0A0A | SQLITE_IOERR_DELETE |
SQLITE_IOERR_DELETE |
| 0x87AF0A13 | SQLITE_CONSTRAINT_ROWID |
SQLITE_CONSTRAINT_ROWID |
| 0x87AF0B0A | SQLITE_IOERR_BLOCKED |
SQLITE_IOERR_BLOCKED |
| 0x87AF0C0A | SQLITE_IOERR_NOMEM |
SQLITE_IOERR_NOMEM |
| 0x87AF0D0A | SQLITE_IOERR_ACCESS |
SQLITE_IOERR_ACCESS |
| 0x87AF0E0A | SQLITE_IOERR_CHECKRESERVEDLOCK |
SQLITE_IOERR_CHECKRESERVEDLOCK |
| 0x87AF0F0A | SQLITE_IOERR_LOCK |
SQLITE_IOERR_LOCK |
| 0x87AF100A | SQLITE_IOERR_CLOSE |
SQLITE_IOERR_CLOSE |
| 0x87AF110A | SQLITE_IOERR_DIR_CLOSE |
SQLITE_IOERR_DIR_CLOSE |
| 0x87AF120A | SQLITE_IOERR_SHMOPEN |
SQLITE_IOERR_SHMOPEN |
| 0x87AF130A | SQLITE_IOERR_SHMSIZE |
SQLITE_IOERR_SHMSIZE |
| 0x87AF140A | SQLITE_IOERR_SHMLOCK |
SQLITE_IOERR_SHMLOCK |
| 0x87AF150A | SQLITE_IOERR_SHMMAP |
SQLITE_IOERR_SHMMAP |
| 0x87AF160A | SQLITE_IOERR_SEEK |
SQLITE_IOERR_SEEK |
| 0x87AF170A | SQLITE_IOERR_DELETE_NOENT |
SQLITE_IOERR_DELETE_NOENT |
| 0x87AF180A | SQLITE_IOERR_MMAP |
SQLITE_IOERR_MMAP |
| 0x87AF190A | SQLITE_IOERR_GETTEMPPATH |
SQLITE_IOERR_GETTEMPPATH |
| 0x87AF1A02 | SQLITE_IOERR_VNODE |
SQLITE_IOERR_VNODE |
| 0x87AF1A03 | SQLITE_IOERR_AUTH |
SQLITE_IOERR_AUTH |
| 0x87AF1A0A | SQLITE_IOERR_CONVPATH |
SQLITE_IOERR_CONVPATH |
| 0x87C51001 | 切换(替换)跟踪已启动 |
Toggle (alternative) trace started |
| 0x87C51002 | 无法抢占正在运行的跟踪: 当前跟踪具有较高的优先级 |
Cannot pre-empt running trace: The current trace has a higher priority |
| 0x87C51003 | 始终跟踪未在运行 |
The always-on-trace is not running |
| 0x87C51004 | RunScriptAction 包含无效的脚本类型 |
RunScriptAction contains an invalid script type |
| 0x87C51005 | 找不到所请求的方案定义 |
Requested scenario definition cannot be found |
| 0x87C51006 | 找不到所请求的跟踪配置文件 |
Requested trace profile cannot be found |
| 0x87C51007 | 触发器转发器已启用 |
Trigger forwarder is already enabled |
| 0x87C51008 | 触发器转发器已禁用 |
Trigger forwarder is already disabled |
| 0x87C51009 | 无法分析 EventLog XML: 条目的格式不正确 |
Cannot parse EventLog XML: The entry is malformed |
| 0x87C5100A | 节点包含与此客户端不兼容的 schemaversion |
node contains a schemaversion which is not compatible with this client |
| 0x87C5100B | RunScriptAction 被强制终止某个脚本 |
RunScriptAction was forced to terminate a script |
| 0x87C5100C | ToggleTraceWithCustomFilterAction 包含无效的 自定义筛选器 |
ToggleTraceWithCustomFilterAction contains an invalid custom filter |
| 0x87C5100D | 跟踪未在运行 |
The trace is not running |
| 0x87C5100E | 某个方案未能提升: 此方案最近已提升 |
A scenario failed to escalate: This scenario has escalated too recently |
| 0x87C5100F | 某个方案未能提升: 此方案已在运行提升 |
A scenario failed to escalate: This scenario is already running an escalation |
| 0x87C51010 | 无法启动跟踪: PerfTrack 组件已在跟踪 |
Cannot start tracing: PerfTrack component is already tracing |
| 0x87C51011 | 某个方案未能提升: 此方案已达到此提升类型的最大提升次数 |
A scenario failed to escalate: This scenario has reached max escalations for this escalation type |
| 0x87C51012 | 无法更新转发器: 传递给函数的转发器属于不同的类型 |
Cannot update forwarder: The forwarder passed to the function is of a different type |
| 0x87C51013 | RunScriptAction 未能特意强制此提升终止 |
RunScriptAction failed intentionally to force this escalation to terminate |
| 0x87C51014 | 未能初始化 SQM 记录程序 |
Failed to initialize SQM logger |
| 0x87C51015 | 未能初始化 WER 记录程序: 此系统不支持将 WER 用于 UTC |
Failed to initialize WER logger: This system does not support WER for UTC |
| 0x87C51016 | TraceManager 试图在不初始化跟踪器的情况下执行跟踪操作 |
The TraceManager has attempted to take a tracing action without initializing tracers |
| 0x87C51017 | WinRT 初始化失败 |
WinRT initialization failed |
| 0x87C51019 | 该方案包含永远无法满足的无效筛选器 |
Scenario contains an invalid filter that can never be satisfied |
| 0x87C5101A | 已强制 RunExeWithArgsAction 终止了一个正在运行的可执行文件 |
RunExeWithArgsAction was forced to terminate a running executable |
| 0x87C5101B | 由于权限不足，方案升级失败 |
Escalation for scenario failed due to insufficient permissions |
| 0x87C5101C | 由于权限不足，方案设置失败 |
Setup for scenario failed due to insufficient permissions |
| 0x87C5101D | UTC 启动的进程失败，退出代码为非零。 |
A process launched by UTC failed with a non-zero exit code. |
| 0x87C5101E | RunExeWithArgs 操作包含未经授权的命令行。 |
A RunExeWithArgs action contains an unauthorized command line. |
| 0x87C5101F | UTC 无法加载方案编辑器 XML。请使用编辑器将方案文件转换为 DiagTrack XML。 |
UTC cannot load Scenario Editor XML. Convert the scenario file to a DiagTrack XML using the editor. |
| 0x87C51020 | 该方案的提升已超时 |
Escalation for scenario has timed out |
| 0x87C51021 | 该方案的设置已超时 |
Setup for scenario has timed out |
| 0x87C51022 | 给定的触发器与预期的触发器类型不匹配 |
The given trigger does not match the expected trigger type |
| 0x87C51023 | 找不到所请求的触发器 |
Requested trigger cannot be found |
| 0x87C51024 | SIF 在此计算机上不受支持 |
SIF is not supported on the machine |
| 0x87C51025 | 延迟操作已终止 |
The delay action was terminated |
| 0x87C51026 | 未获得设备票证 |
The device ticket was not obtained |
| 0x87C51027 | 比起可用于跟踪的内存，跟踪配置文件需要更多的内存 |
The trace profile needs more memory than is available for tracing |
| 0x87C51028 | API 未成功完成，因此未显示结果 |
The API was not completed successfully so the result is unavailable |
| 0x87C51029 | 请求的 API 在 API 管理器中遇到超时 |
The requested API encountered a timeout in the API manager |
| 0x87C5102A | 同步 API 遇到等待失败 |
The synchronous API encountered a wait failure |
| 0x87C5102B | UTC API 忙于处理其他请求 |
The UTC API is busy with another request |
| 0x87C5102C | 正在运行的跟踪配置文件的运行时不足，无法完成提升请求 |
The running trace profile does not have a sufficient runtime to fulfill the escalation request |
| 0x87C5102D | 跟踪配置文件无法启动，因为它要求独占性，而另一个优先级更高的跟踪已在运行 |
The trace profile could not be started because it requires exclusivity and another higher priority trace is already running |
| 0x87C5102E | 此文件路径不允许进行 GetFile 升级操作 |
The file path is not approved for the GetFile escalation action |
| 0x87C5102F | 无法针对请求的升级创建升级工作目录，因为该目录已存在 |
The escalation working directory for the requested escalation could not be created because it already exists |
| 0x87C51030 | 时间触发器不能用于源自“开始”状态的转换 |
Time triggers cannot be used on a transition originating from the \"_start\" state |
| 0x87C51031 | 时间触发器只能附加到单个转换 |
Time triggers can only be attached to a single transition |
| 0x87C51032 | 时间触发持续时间必须在 1 秒到 15 分钟(含两者)的范围内 |
Time trigger duration must fall within an inclusive range of one second and 15 minutes |
| 0x87C51033 | 每个状态只允许使用一个时间触发器 |
Only one Time Trigger is allowed per state |
| 0x87C51034 | 某个 RunExeWithArgs 操作包含目标设备上不存在的二进制文件。 |
A RunExeWithArgs action contains a binary which is not present on the targeted device. |
| 0x88010001 | 未使用第三方加密提供程序将一个或多个固定卷预配为支持设备加密。使用第三方提供程序启用加密以遵守策略。 |
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. |
| 0x88010002 | 这台计算机未完全加密。存在不支持加密的固定卷。 |
This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption. |
| 0x88010003 | 这台计算机不满足使用已安装的第三方提供程序支持设备加密的硬件要求。 |
This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider. |
| 0x88010004 | 这台计算机无法支持设备加密，因为未配置设备锁定功能所必需的内容。 |
This computer cannot support device encryption because the requisites for the device lock feature are not configured. |
| 0x88010005 | 保护已在此卷上启用，但未处于活动状态。 |
Protection is enabled on this volume but is not in the active state. |
| 0x88010006 | 第三方提供程序已安装，但无法激活加密，因为许可证尚未激活。 |
The 3rd party provider has been installed, but cannot activate encryption beacuse a license has not been activated. |
| 0x88010007 | 操作系统驱动器不受第三方驱动器加密的保护。 |
The operating system drive is not protected by 3rd party drive encryption. |
| 0x88010008 | 调入第三方驱动器加密插件时发生意外故障。 |
Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin. |
| 0x88010009 | 第三方设备加密使用的锁定元数据输入缓冲区大小太大。 |
The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large. |
| 0x8802B001 | 文件大小大于同步引擎支持的大小。 |
The file size is larger than supported by the sync engine. |
| 0x8802B002 | 无法上载该文件，因为它无法容纳在用户的可用服务提供的存储空间中。 |
The file cannot be uploaded because it doesn't fit in the user's available service provided storage space. |
| 0x8802B003 | 文件名包含无效字符。 |
The file name contains invalid characters. |
| 0x8802B004 | 已达到同步引擎中此文件夹的最大文件计数。 |
The maximum file count has been reached for this folder in the sync engine. |
| 0x8802B005 | 文件同步已委派给另一个程序，并遇到了问题。 |
The file sync has been delegated to another program and has run into an issue. |
| 0x8802B006 | 由于该服务发出限制请求，已延迟同步。 |
Sync has been delayed due to a throttling request from the service. |
| 0x8802C002 | 我们似乎无法找到该文件。请稍后重试。 |
We can't seem to find that file. Please try again later. |
| 0x8802C003 | 你用于登录的帐户无权打开此文件。 |
The account you're signed in with doesn't have permission to open this file. |
| 0x8802C004 | 连接到该服务时出现问题。请稍后重试。 |
There was a problem connecting to the service. Please try again later. |
| 0x8802C005 | 抱歉，下载该文件时出现问题。 |
Sorry, there was a problem downloading the file. |
| 0x8802C006 | 当前在下载该文件时遇到问题。请稍后重试。 |
We're having trouble downloading the file right now. Please try again later. |
| 0x8802D001 | 同步引擎无权访问同步根目录下的本地文件夹。 |
The sync engine does not have permissions to access a local folder under the sync root. |
| 0x8802D002 | 文件夹名包含无效字符。 |
The folder name contains invalid characters. |
| 0x8802D003 | 当前市场中不允许运行同步引擎。 |
The sync engine is not allowed to run in your current market. |
| 0x8802D004 | 由于某个文件或文件夹的路径太长，无法上载所有文件和文件夹。 |
All files and folders can't be uploaded because a path of a file or folder is too long. |
| 0x8802D005 | 由于某个文件或文件夹的路径会超出本地路径限制，无法同步所有文件和文件夹。 |
All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit. |
| 0x8802D006 | 若要使用该同步引擎，需要安装更新。 |
Updates are needed in order to use the sync engine. |
| 0x8802D007 | 同步引擎需要通过代理服务器进行身份验证。 |
The sync engine needs to authenticate with a proxy server. |
| 0x8802D008 | 为该帐户设置存储服务时出现问题。 |
There was a problem setting up the storage services for the account. |
| 0x8802D009 | 无法上载文件，因为存在不支持的重分析点。 |
Files can't be uploaded because there's an unsupported reparse point. |
| 0x8802D00A | 该服务已阻止你的帐户访问存储服务。 |
The service has blocked your account from accessing the storage service. |
| 0x8802D00B | 现在无法执行操作，因为正在移动此文件夹。请稍后重试。 |
The action can't be performed right now because this folder is being moved. Please try again later. |
| 0x88790001 | 应用程序已超出每个 Direct3D 设备的唯一状态对象的最大数目。对于最高 11.1 的功能级别，限制为 4096。 |
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. |
| 0x88790002 | 找不到指定的文件。 |
The specified file was not found. |
| 0x887A0001 | 应用程序进行了无效的调用。调用的参数或某对象的状态不正确。启用 D3D 调试层以便通过调试消息查看详细信息。 |
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. |
| 0x887A0002 | 未找到对象。如果调用 IDXGIFactory::EnumAdaptes，则没有具有指定序号的适配器。 |
The object was not found. If calling IDXGIFactory::EnumAdaptes, there is no adapter with the specified ordinal. |
| 0x887A0003 | 调用方未提供足够大的缓冲区。 |
The caller did not supply a sufficiently large buffer. |
| 0x887A0004 | 指定的设备接口或功能级别在此系统上不受支持。 |
The specified device interface or feature level is not supported on this system. |
| 0x887A0005 | GPU 设备实例已经暂停。使用 GetDeviceRemovedReason 以确定相应的措施。 |
The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. |
| 0x887A0006 | GPU 不响应更多的命令，最为可能的原因是调用应用程序传递了无效的命令。 |
The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. |
| 0x887A0007 | GPU 不响应更多的命令，最为可能的原因是其他应用程序递交了无效的命令。调用应用程序应该重新创建设备并继续。 |
The 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. |
| 0x887A000A | 进行调用时 GPU 正忙，无法执行或计划调用。 |
The GPU was busy at the moment when the call was made, and the call was neither executed nor scheduled. |
| 0x887A000B | 某个事件(如电源周期)中断了演示统计信息的收集。之前的任何统计信息都应该视为是无效的。 |
An event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should beconsidered invalid. |
| 0x887A000C | 无法获得全屏幕模式，原因是指定的输出已处于使用状态。 |
Fullscreen mode could not be achieved because the specified output was already in use. |
| 0x887A0020 | 某个内部错误阻止驱动程序执行指定的操作。驱动程序的状态可疑，应用程序应该终止。 |
An internal issue prevented the driver from carrying out the specified operation. The driver's state is probably suspect,and the application should not continue. |
| 0x887A0021 | 全局计数器资源处于使用状态，目前此 Direct3D 设备无法使用指定的计数器。 |
A global counter resource was in use, and the specified counter cannot be used by this Direct3D device at this time. |
| 0x887A0022 | 调用时资源无法使用，但可能稍后可以使用。 |
A resource is not available at the time of the call, but may become available later. |
| 0x887A0023 | 由于会话断开连接或网络断开连接，应用程序的远程设备已删除。应用程序应该调用 IDXGIFactory1::IsCurrent 以确定何时可以再次使用远程设备。 |
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. |
| 0x887A0024 | 远程会话期间设备已删除，原因是远程计算机内存耗尽。 |
The device has been removed during a remote session because the remote computer ran out of memory. |
| 0x887A0025 | 正在进行的模式更改阻止了调用的完成。如果稍后尝试，调用可能会成功。 |
An on-going mode change prevented completion of the call. The call may succeed if attempted later. |
| 0x887A0026 | 键控互斥已弃用。 |
The keyed mutex was abandoned. |
| 0x887A0027 | 超时值已过，资源还不可用。 |
The timeout value has elapsed and the resource is not yet available. |
| 0x887A0028 | 输出复制功能已禁用，原因是 Windows 会话结束或断开。在远程用户断开连接或在本地使用“切换用户”时会出现这种情况。 |
The 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. |
| 0x887A0029 | 交换链内容仅在其中显示的 DXGI 输出(监视器)已断开连接或已更改。 |
The DXGI outuput (monitor) to which the swapchain content was restricted, has been disconnected or changed. |
| 0x887A002A | DXGI 无法为交换链提供内容保护。这通常是由旧驱动程序，或使用与内容保护不兼容的交换链的应用程序所致。 |
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. |
| 0x887A002B | 此应用程序正在试图使用它不具有必要访问权限的资源。出现此现象的最常见的原因是使用只读权限写入共享资源。 |
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. |
| 0x887A002C | 应用程序正尝试使用已与其他某些资源关联的名称创建共享句柄。 |
The application is trying to create a shared handle using a name that is already associated with some other resource. |
| 0x887A002D | 应用程序请求的操作依赖于已缺失或不匹配的 SDK 组件。 |
The application requested an operation that depends on an SDK component that is missing or mismatched. |
| 0x887A002E | 应用程序已创建的 DXGI 对象不再是最新的，需要重新创建这些对象才能执行此操作。 |
The DXGI objects that the application has created are no longer current & need to be recreated for this operation to be performed. |
| 0x887A0030 | 不足的 HW 保护内存退出以便正常工作。 |
Insufficient HW protected memory exits for proper function. |
| 0x887A0031 | 创建此设备将违反进程的动态代码策略。 |
Creating this device would violate the process's dynamic code policy. |
| 0x887A0032 | 由于合成程序未控制输出，操作失败。 |
The operation failed because the compositor is not in control of the output. |
| 0x887A0033 | 缓存已损坏，无法打开或无法重置。 |
The cache is corrupt and either could not be opened or could not be reset. |
| 0x887A0034 | 此条目将导致缓存超过其配额。在加载操作时，这可能指示超过最大内存中大小。 |
This entry would cause the cache to exceed its quota. On a load operation, this may indicate exceeding the maximum in-memory size. |
| 0x887A0035 | 已找到缓存条目，但提供的密钥与条目中存储的密钥不匹配。 |
A cache entry was found, but the key provided does not match the key stored in the entry. |
| 0x887A0036 | 所需元素已存在。 |
The desired element already exists. |
| 0x887B0001 | 请求此操作时 GPU 正忙。 |
The GPU was busy when the operation was requested. |
| 0x887B0002 | 驱动程序已拒绝创建此资源。 |
The driver has rejected the creation of this resource. |
| 0x887B0003 | 当应用程序请求访问 GPU 计数器时，该计数器正由另一个进程或 d3d 设备使用。 |
The GPU counter was in use by another process or d3d device when application requested access to it. |
| 0x887C0003 | 此应用程序已超出每个 Direct3D 设备的唯一视图对象的最大数目。对于最高 11.1 的功能级别，限制为 2^20。 |
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. |
| 0x887C0004 | 应用程序按命令列表对延迟上下文的映射进行的首次调用未使用 D3D11_MAP_WRITE_DISCARD。 |
The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD. |
| 0x887E0001 | 提供的 Blob 与创建了该设备的适配器不匹配。 |
The blob provided does not match the adapter that the device was created on. |
| 0x887E0002 | 提供的 Blob 是为驱动程序的另一个版本创建的，必须重新创建。 |
The blob provided was created for a different version of the driver, and must be re-created. |
| 0x88980001 | MILERR_OBJECTBUSY |
MILERR_OBJECTBUSY |
| 0x88980002 | MILERR_INSUFFICIENTBUFFER |
MILERR_INSUFFICIENTBUFFER |
| 0x88980003 | MILERR_WIN32ERROR |
MILERR_WIN32ERROR |
| 0x88980004 | MILERR_SCANNER_FAILED |
MILERR_SCANNER_FAILED |
| 0x88980005 | MILERR_SCREENACCESSDENIED |
MILERR_SCREENACCESSDENIED |
| 0x88980006 | MILERR_DISPLAYSTATEINVALID |
MILERR_DISPLAYSTATEINVALID |
| 0x88980007 | MILERR_NONINVERTIBLEMATRIX |
MILERR_NONINVERTIBLEMATRIX |
| 0x88980008 | MILERR_ZEROVECTOR |
MILERR_ZEROVECTOR |
| 0x88980009 | MILERR_TERMINATED |
MILERR_TERMINATED |
| 0x8898000A | MILERR_BADNUMBER |
MILERR_BADNUMBER |
| 0x88980080 | 出现了内部错误 (MIL 错误)。对于已检验版本，将提出声明。 |
An internal error (MIL bug) occurred. On checked builds, an assert would be raised. |
| 0x88980084 | 我们需要呈现的显示格式不受硬件设备支持。 |
The display format we need to render is not supported by the hardware device. |
| 0x88980085 | 对此方法的调用无效。 |
A call to this method is invalid. |
| 0x88980086 | 尝试对已锁定的对象进行锁定。 |
Lock attempted on an already locked object. |
| 0x88980087 | 尝试对一个已解锁的对象进行解锁。 |
Unlock attempted on an unlocked object. |
| 0x88980088 | 未提供使用此设备呈现文本的算法 |
No algorithm avaliable to render text with this device |
| 0x88980089 | 字形运行呈现所需的一些字形位图不包含在字形缓存中。 |
Some glyph bitmaps, required for glyph run rendering, are not contained in glyph cache. |
| 0x8898008A | 字形缓存中的一些字形位图异常大。 |
Some glyph bitmaps in glyph cache are unexpectedly big. |
| 0x8898008B | 当前合成程序已忽略的已知 Win32 错误的标记错误。这是为了避免在出现错误而仍然在正确的位置中展开堆栈时返回 S_OK。 |
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. |
| 0x8898008C | 指导性坐标没有正确排序或包含 NaN。 |
Guideline coordinates are not sorted properly or contain NaNs. |
| 0x8898008D | 没有提供用于此操作的 HW 呈现设备。 |
No HW rendering device is available for this operation. |
| 0x8898008E | 存在可以恢复的演示错误。调用方需要重新创建、重新呈现整个帧，并重新尝试显示。有两个适用于此现象的已知案例: 1) D3D 驱动程序内部错误 2) D3D E_FAIL 2a) 未知根本原因 b) 当过快调整 DWM 的大小时，D3D 保持同步 |
There 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 |
| 0x8898008F | 对象已初始化。 |
The object has already been initialized. |
| 0x88980090 | 对象的大小与预期大小不相符。 |
The size of the object does not match the expected size. |
| 0x88980091 | 重定向表面不可用。 |
No Redirection surface available. |
| 0x88980092 | 不支持对此内容进行远程处理。 |
Remoting of this content is not supported. |
| 0x88980093 | 排队显示不受支持。 |
Queued Presents are not supported. |
| 0x88980094 | 排队显示未在使用中。 |
Queued Presents are not being used. |
| 0x88980095 | 重定向表面不可用。调用方应该重试调用。 |
No redirection surface was available. Caller should retry the call. |
| 0x88980096 | 着色器构造失败，原因是其过于复杂。 |
Shader construction failed because it was too complex. |
| 0x88980097 | MROW 尝试获取读取锁定失败。 |
MROW attempt to get a read lock failed. |
| 0x88980098 | MROW 尝试更新数据失败，原因是另一个更新尚未完成。 |
MROW attempt to update the data failed because another update was outstanding. |
| 0x88980099 | 着色器编译失败。 |
Shader compilation failed. |
| 0x8898009A | 请求的 DX 重定向表面大小超出了最大的纹理大小。 |
Requested DX redirection surface size exceeded maximum texture size. |
| 0x8898009B | QueryPerformanceCounter 返回了过去的时间。 |
QueryPerformanceCounter returned a time in the past. |
| 0x8898009D | 主显示器设备返回了无效的刷新频率。 |
Primary Display device returned an invalid refresh rate. |
| 0x8898009E | DWM 无法找到 LUID 指定的适配器。 |
DWM can not find the adapter specified by the LUID. |
| 0x8898009F | 不支持请求的位图颜色空间。 |
The requested bitmap color space is not supported. |
| 0x889800A0 | 不支持请求的位图预筛选状态。 |
The requested bitmap pre-filtering state is not supported. |
| 0x889800A1 | 访问指定的显示 ID 的请求位图被拒绝。 |
Access is denied to the requested bitmap for the specified display id. |
| 0x88980400 | UCEERR_INVALIDPACKETHEADER |
UCEERR_INVALIDPACKETHEADER |
| 0x88980401 | UCEERR_UNKNOWNPACKET |
UCEERR_UNKNOWNPACKET |
| 0x88980402 | UCEERR_ILLEGALPACKET |
UCEERR_ILLEGALPACKET |
| 0x88980403 | UCEERR_MALFORMEDPACKET |
UCEERR_MALFORMEDPACKET |
| 0x88980404 | UCEERR_ILLEGALHANDLE |
UCEERR_ILLEGALHANDLE |
| 0x88980405 | UCEERR_HANDLELOOKUPFAILED |
UCEERR_HANDLELOOKUPFAILED |
| 0x88980406 | UCEERR_RENDERTHREADFAILURE |
UCEERR_RENDERTHREADFAILURE |
| 0x88980407 | UCEERR_CTXSTACKFRSTTARGETNULL |
UCEERR_CTXSTACKFRSTTARGETNULL |
| 0x88980408 | UCEERR_CONNECTIONIDLOOKUPFAILED |
UCEERR_CONNECTIONIDLOOKUPFAILED |
| 0x88980409 | UCEERR_BLOCKSFULL |
UCEERR_BLOCKSFULL |
| 0x8898040A | UCEERR_MEMORYFAILURE |
UCEERR_MEMORYFAILURE |
| 0x8898040B | UCEERR_PACKETRECORDOUTOFRANGE |
UCEERR_PACKETRECORDOUTOFRANGE |
| 0x8898040C | UCEERR_ILLEGALRECORDTYPE |
UCEERR_ILLEGALRECORDTYPE |
| 0x8898040D | UCEERR_OUTOFHANDLES |
UCEERR_OUTOFHANDLES |
| 0x8898040E | UCEERR_UNCHANGABLE_UPDATE_ATTEMPTED |
UCEERR_UNCHANGABLE_UPDATE_ATTEMPTED |
| 0x8898040F | UCEERR_NO_MULTIPLE_WORKER_THREADS |
UCEERR_NO_MULTIPLE_WORKER_THREADS |
| 0x88980410 | UCEERR_REMOTINGNOTSUPPORTED |
UCEERR_REMOTINGNOTSUPPORTED |
| 0x88980411 | UCEERR_MISSINGENDCOMMAND |
UCEERR_MISSINGENDCOMMAND |
| 0x88980412 | UCEERR_MISSINGBEGINCOMMAND |
UCEERR_MISSINGBEGINCOMMAND |
| 0x88980413 | UCEERR_CHANNELSYNCTIMEDOUT |
UCEERR_CHANNELSYNCTIMEDOUT |
| 0x88980414 | UCEERR_CHANNELSYNCABANDONED |
UCEERR_CHANNELSYNCABANDONED |
| 0x88980415 | UCEERR_UNSUPPORTEDTRANSPORTVERSION |
UCEERR_UNSUPPORTEDTRANSPORTVERSION |
| 0x88980416 | UCEERR_TRANSPORTUNAVAILABLE |
UCEERR_TRANSPORTUNAVAILABLE |
| 0x88980417 | UCEERR_FEEDBACK_UNSUPPORTED |
UCEERR_FEEDBACK_UNSUPPORTED |
| 0x88980418 | UCEERR_COMMANDTRANSPORTDENIED |
UCEERR_COMMANDTRANSPORTDENIED |
| 0x88980419 | UCEERR_GRAPHICSSTREAMUNAVAILABLE |
UCEERR_GRAPHICSSTREAMUNAVAILABLE |
| 0x88980420 | UCEERR_GRAPHICSSTREAMALREADYOPEN |
UCEERR_GRAPHICSSTREAMALREADYOPEN |
| 0x88980421 | UCEERR_TRANSPORTDISCONNECTED |
UCEERR_TRANSPORTDISCONNECTED |
| 0x88980422 | UCEERR_TRANSPORTOVERLOADED |
UCEERR_TRANSPORTOVERLOADED |
| 0x88980423 | UCEERR_PARTITION_ZOMBIED |
UCEERR_PARTITION_ZOMBIED |
| 0x88980500 | MILAVERR_NOCLOCK |
MILAVERR_NOCLOCK |
| 0x88980501 | MILAVERR_NOMEDIATYPE |
MILAVERR_NOMEDIATYPE |
| 0x88980502 | MILAVERR_NOVIDEOMIXER |
MILAVERR_NOVIDEOMIXER |
| 0x88980503 | MILAVERR_NOVIDEOPRESENTER |
MILAVERR_NOVIDEOPRESENTER |
| 0x88980504 | MILAVERR_NOREADYFRAMES |
MILAVERR_NOREADYFRAMES |
| 0x88980505 | MILAVERR_MODULENOTLOADED |
MILAVERR_MODULENOTLOADED |
| 0x88980506 | MILAVERR_WMPFACTORYNOTREGISTERED |
MILAVERR_WMPFACTORYNOTREGISTERED |
| 0x88980507 | MILAVERR_INVALIDWMPVERSION |
MILAVERR_INVALIDWMPVERSION |
| 0x88980508 | MILAVERR_INSUFFICIENTVIDEORESOURCES |
MILAVERR_INSUFFICIENTVIDEORESOURCES |
| 0x88980509 | MILAVERR_VIDEOACCELERATIONNOTAVAILABLE |
MILAVERR_VIDEOACCELERATIONNOTAVAILABLE |
| 0x8898050A | MILAVERR_REQUESTEDTEXTURETOOBIG |
MILAVERR_REQUESTEDTEXTURETOOBIG |
| 0x8898050B | MILAVERR_SEEKFAILED |
MILAVERR_SEEKFAILED |
| 0x8898050C | MILAVERR_UNEXPECTEDWMPFAILURE |
MILAVERR_UNEXPECTEDWMPFAILURE |
| 0x8898050D | MILAVERR_MEDIAPLAYERCLOSED |
MILAVERR_MEDIAPLAYERCLOSED |
| 0x8898050E | MILAVERR_UNKNOWNHARDWAREERROR |
MILAVERR_UNKNOWNHARDWAREERROR |
| 0x8898060E | MILEFFECTSERR_UNKNOWNPROPERTY |
MILEFFECTSERR_UNKNOWNPROPERTY |
| 0x8898060F | MILEFFECTSERR_EFFECTNOTPARTOFGROUP |
MILEFFECTSERR_EFFECTNOTPARTOFGROUP |
| 0x88980610 | MILEFFECTSERR_NOINPUTSOURCEATTACHED |
MILEFFECTSERR_NOINPUTSOURCEATTACHED |
| 0x88980611 | MILEFFECTSERR_CONNECTORNOTCONNECTED |
MILEFFECTSERR_CONNECTORNOTCONNECTED |
| 0x88980612 | MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT |
MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT |
| 0x88980613 | MILEFFECTSERR_RESERVED |
MILEFFECTSERR_RESERVED |
| 0x88980614 | MILEFFECTSERR_CYCLEDETECTED |
MILEFFECTSERR_CYCLEDETECTED |
| 0x88980615 | MILEFFECTSERR_EFFECTINMORETHANONEGRAPH |
MILEFFECTSERR_EFFECTINMORETHANONEGRAPH |
| 0x88980616 | MILEFFECTSERR_EFFECTALREADYINAGRAPH |
MILEFFECTSERR_EFFECTALREADYINAGRAPH |
| 0x88980617 | MILEFFECTSERR_EFFECTHASNOCHILDREN |
MILEFFECTSERR_EFFECTHASNOCHILDREN |
| 0x88980618 | MILEFFECTSERR_ALREADYATTACHEDTOLISTENER |
MILEFFECTSERR_ALREADYATTACHEDTOLISTENER |
| 0x88980619 | MILEFFECTSERR_NOTAFFINETRANSFORM |
MILEFFECTSERR_NOTAFFINETRANSFORM |
| 0x8898061A | MILEFFECTSERR_EMPTYBOUNDS |
MILEFFECTSERR_EMPTYBOUNDS |
| 0x8898061B | MILEFFECTSERR_OUTPUTSIZETOOLARGE |
MILEFFECTSERR_OUTPUTSIZETOOLARGE |
| 0x88980700 | DWMERR_STATE_TRANSITION_FAILED |
DWMERR_STATE_TRANSITION_FAILED |
| 0x88980701 | DWMERR_THEME_FAILED |
DWMERR_THEME_FAILED |
| 0x88980702 | DWMERR_CATASTROPHIC_FAILURE |
DWMERR_CATASTROPHIC_FAILURE |
| 0x88980800 | DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED |
DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED |
| 0x88980801 | DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED |
DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED |
| 0x88980802 | DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED |
DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED |
| 0x88982F04 | 编解码器处于错误的状态。 |
The codec is in the wrong state. |
| 0x88982F05 | 值超出范围。 |
The value is out of range. |
| 0x88982F07 | 图像格式未知。 |
The image format is unknown. |
| 0x88982F0B | SDK 版本不受支持。 |
The SDK version is unsupported. |
| 0x88982F0C | 组件未初始化。 |
The component is not initialized. |
| 0x88982F0D | 已经存在未完成的读取锁定或写入锁定。 |
There is already an outstanding read or write lock. |
| 0x88982F40 | 无法找到指定的位图属性。 |
The specified bitmap property cannot be found. |
| 0x88982F41 | 位图编解码器不支持位图属性。 |
The bitmap codec does not support the bitmap property. |
| 0x88982F42 | 位图属性大小无效。 |
The bitmap property size is invalid. |
| 0x88982F43 | 发生了未知错误。 |
An unknown error has occurred. |
| 0x88982F44 | 位图编解码器不支持缩略图。 |
The bitmap codec does not support a thumbnail. |
| 0x88982F45 | 位图调色板不可用。 |
The bitmap palette is unavailable. |
| 0x88982F46 | 请求了过多的扫描行。 |
Too many scanlines were requested. |
| 0x88982F49 | 位图边界与位图分辨率不相符。 |
The bitmap bounds do not match the bitmap dimensions. |
| 0x88982F50 | 无法找不到组件。 |
The component cannot be found. |
| 0x88982F51 | 位图大小超出有效的范围。 |
The bitmap size is outside the valid range. |
| 0x88982F52 | 要写入位图中的元数据过多。 |
There is too much metadata to be written to the bitmap. |
| 0x88982F60 | 图像无法识别。 |
The image is unrecognized. |
| 0x88982F61 | 图像标题无法识别。 |
The image header is unrecognized. |
| 0x88982F62 | 位图边框丢失。 |
The bitmap frame is missing. |
| 0x88982F63 | 图像元数据头无法识别。 |
The image metadata header is unrecognized. |
| 0x88982F70 | 流数据无法识别。 |
The stream data is unrecognized. |
| 0x88982F71 | 无法写入流。 |
Failed to write to the stream. |
| 0x88982F72 | 无法读取流。 |
Failed to read from the stream. |
| 0x88982F73 | 流不可用。 |
The stream is not available. |
| 0x88982F80 | 位图像素格式不受支持。 |
The bitmap pixel format is unsupported. |
| 0x88982F81 | 操作不受支持。 |
The operation is unsupported. |
| 0x88982F8A | 组件注册无效。 |
The component registration is invalid. |
| 0x88982F8B | 组件初始化失败。 |
The component initialization has failed. |
| 0x88982F8C | 分配的缓冲区不够。 |
The buffer allocated is insufficient. |
| 0x88982F8D | 存在重复的元数据。 |
Duplicate metadata is present. |
| 0x88982F8E | 位图属性类型异常。 |
The bitmap property type is unexpected. |
| 0x88982F8F | 大小异常。 |
The size is unexpected. |
| 0x88982F90 | 属性查询无效。 |
The property query is invalid. |
| 0x88982F91 | 元数据类型异常。 |
The metadata type is unexpected. |
| 0x88982F92 | 指定的位图属性仅在根级别有效。 |
The specified bitmap property is only valid at root level. |
| 0x88982F93 | 查询字符串包含无效字符。 |
The query string contains an invalid character. |
| 0x88982F94 | Windows 编解码器从 Win32 系统接收到一个错误。 |
Windows Codecs received an error from the Win32 system. |
| 0x88982F95 | 请求的详细信息级别不存在。 |
The requested level of detail is not present. |
| 0x88982F96 | 扫描索引无效。 |
The scan index is invalid. |
| 0x88985000 | 指示输入文件 (例如字体文件) 中的错误。 |
Indicates an error in an input file such as a font file. |
| 0x88985001 | 指示以 DirectWrite 代码开始的错误，此错误是意外出现，但是可以恢复。 |
Indicates an error originating in DirectWrite code, which is not expected to occur but is safe to recover from. |
| 0x88985002 | 指示指定的字体不存在。 |
Indicates the specified font does not exist. |
| 0x88985003 | 无法打开字体文件，原因是文件、目录、网络位置、驱动器或其他存储文字不存在或不可用。 |
A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable. |
| 0x88985004 | 字体文件存在，但是由于访问被拒绝、共享冲突或类似错误而无法打开。 |
A font file exists but could not be opened due to access denied, sharing violation, or similar error. |
| 0x88985005 | 由于系统中的更改，字体集已过时。 |
A font collection is obsolete due to changes in the system. |
| 0x88985006 | 给定的接口已注册。 |
The given interface is already registered. |
| 0x88985007 | 字体缓存包含无效数据。 |
The font cache contains invalid data. |
| 0x88985008 | 字体缓存文件对应于不同的 DirectWrite 版本。 |
A font cache file corresponds to a different version of DirectWrite. |
| 0x88985009 | 这种类型的字体不支持这个操作。 |
The operation is not supported for this type of font. |
| 0x8898500A | 文本呈现器接口的版本不兼容。 |
The version of the text renderer interface is not compatible. |
| 0x8898500B | 流方向与读取方向冲突。它们必须彼此垂直。 |
The flow direction conflicts with the reading direction. They must be perpendicular to each other. |
| 0x8898500C | 字体或字形运行不包含任何彩色字形。 |
The font or glyph run does not contain any colored glyphs. |
| 0x88990001 | 对象未处于正确的状态来处理此方法。 |
The object was not in the correct state to process the method. |
| 0x88990002 | 对象尚未初始化。 |
The object has not yet been initialized. |
| 0x88990004 | 几何扫描仪无法处理数据。 |
The geometry scanner failed to process the data. |
| 0x88990005 | Direct2D 无法访问屏幕。 |
Direct2D could not access the screen. |
| 0x88990006 | 无法确定有效的显示状态。 |
A valid display state could not be determined. |
| 0x88990007 | 提供的矢量为零。 |
The supplied vector is zero. |
| 0x88990008 | 出现了内部错误 (Direct2D 错误)。对于已检验版本，我们将做出声明。应用程序应该关闭此 Direct2D 实例并且应考虑重新启动其进程。 |
An 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. |
| 0x88990009 | Direct2D 需要呈现的显示格式不受硬件设备支持。 |
The display format Direct2D needs to render is not supported by the hardware device. |
| 0x8899000B | 没有硬件呈现设备可用于此操作。 |
No hardware rendering device is available for this operation. |
| 0x8899000C | 存在可以恢复的演示错误。调用方需要重新创建、重新渲染整个帧，并重新尝试显示。 |
There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present. |
| 0x8899000F | 请求的 DirectX 表面大小超出最大的纹理大小。 |
Requested DirectX surface size exceeded maximum texture size. |
| 0x88990010 | 请求的 Direct2D 版本不受支持。 |
The requested Direct2D version is not supported. |
| 0x88990011 | 无效的编号。 |
Invalid number. |
| 0x88990012 | 一起使用的对象必须创建自相同的工厂实例。 |
Objects used together must be created from the same factory instance. |
| 0x88990013 | 层资源在任何时间点仅可以使用一次。 |
A layer resource can only be in use once at any point in time. |
| 0x88990014 | 弹出调用与相应的推送调用不相符。 |
The pop call did not match the corresponding push call. |
| 0x88990015 | 在错误的呈现器目标上实现资源。 |
The resource was realized on the wrong render target. |
| 0x88990016 | 推送和弹出调用不平衡。 |
The push and pop calls were unbalanced. |
| 0x88990017 | 应用层或剪裁矩形时尝试从呈现器目标进行复制。 |
Attempt to copy from a render target while a layer or clip rect is applied. |
| 0x88990018 | 画笔类型与调用不兼容。 |
The brush types are incompatible for the call. |
| 0x88990019 | 发生未知的 win32 错误。 |
An unknown win32 failure occurred. |
| 0x8899001A | 呈现器目标与 GDI 不兼容。 |
The render target is not compatible with GDI. |
| 0x8899001B | 文本客户端绘制效果对象的类型不正确。 |
A text client drawing effect object is of the wrong type. |
| 0x8899001C | 相应的 DrawText 或 DrawTextLayout 调用返回后，应用程序包含对 IDWriteTextRenderer 接口的引用。IDWriteTextRenderer 实例将无效。 |
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. |
| 0x8899001D | 请求的大小大于在 Direct3D 设备的当前功能级别保证受支持的纹理大小。 |
The requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level. |
| 0x8899001E | 图表中存在配置错误。 |
There was a configuration error in the graph. |
| 0x8899001F | 图表中存在内部配置错误。 |
There was a internal configuration error in the graph. |
| 0x88990020 | 图表中存在循环。 |
There was a cycle in the graph. |
| 0x88990021 | 无法使用带 D2D1_BITMAP_OPTIONS_CANNOT_DRAW 选项的位图进行绘制。 |
Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option. |
| 0x88990022 | 操作无法完成，原因是目标位图有未完成的引用。 |
The operation cannot complete while there are outstanding references to the target bitmap. |
| 0x88990023 | 操作失败，原因是原始目标当前未绑定为目标。 |
The operation failed because the original target is not currently bound as a target. |
| 0x88990024 | 无法将图像设置为目标，原因是它是一种效果或是未设置 D2D1_BITMAP_OPTIONS_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. |
| 0x88990025 | 无法使用当前绑定为目标位图的位图进行绘制。 |
Cannot draw with a bitmap that is currently bound as the target bitmap. |
| 0x88990026 | D3D 设备没有足够的功能来执行请求的操作。 |
D3D Device does not have sufficient capabilities to perform the requested action. |
| 0x88990027 | 无法使用上下文当前平铺设置对图进行渲染。 |
The graph could not be rendered with the context's current tiling settings. |
| 0x88990028 | 提供给取消注册程序的 CLSID 与注册效果不相符。 |
The CLSID provided to Unregister did not correspond to a registered effect. |
| 0x88990029 | 指定的属性不存在。 |
The specified property does not exist. |
| 0x8899002A | 指定的子属性不存在。 |
The specified sub-property does not exist. |
| 0x8899002B | 打印作业关闭之后调用的 AddPage 或 Close。 |
AddPage or Close called after print job is already closed. |
| 0x8899002C | 创建打印控制时出错。指示包目标类型 (代表打印机格式) 不受 Direct2D 打印控制支持。 |
Error during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control. |
| 0x8899002D | 效果尝试使用具有过多输入的转换。 |
An effect attempted to use a transform with too many inputs. |
| 0x8899002E | 对请求的字形图像进行解码或分析时遇到错误。 |
An error was encountered while decoding or parsing the requested glyph image. |
| 0x89010001 | 此操作已被更高优先级的操作取代。之后必须恢复该操作。 |
The operation was preempted by a higher priority operation. It must be resumed later. |
| 0x89020001 | 函数无法执行，因为已将其删除或作为垃圾回收。 |
Function could not execute because it was deleted or garbage collected. |
| 0xC0090001 | 当前没有审核指定的事件。 |
The specified event is currently not being audited. |
| 0xC0090002 | SID 筛选操作删除了所有 SID。 |
The SID filtering operation removed all SIDs. |
| 0xC0090003 | 已禁用调用应用程序的业务规则脚本。 |
Business rule scripts are disabled for the calling application. |
| 0xC02605E8 | 函数失败，因为当前会话正在更改其类型。当前会话正在更改其类型时，无法调用该函数。当前存在三种类型的会话: 控制台、断开连接和远程。 |
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. |
| 0xC0261003 | 获取的监视器描述符的校验和无效。 |
Checksum of the obtained monitor descriptor is invalid. |
| 0xC0261004 | 监视器描述符包含无效的标准计时块。 |
Monitor descriptor contains an invalid standard timing block. |
| 0xC0261005 | 为 MSMonitorClass WMI 子类之一进行的 WMI 数据块注册失败。 |
WMI data block registration failed for one of the MSMonitorClass WMI subclasses. |
| 0xC0261006 | 提供的监视器描述符块已损坏或不包含监视器的详细序列号。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number. |
| 0xC0261007 | 提供的监视器描述符块已损坏，或者不包含监视器的用户好记的名称。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name. |
| 0xC0261008 | 在指定的(偏移，大小)区域没有监视器描述符数据。 |
There is no monitor descriptor data at the specified (offset, size) region. |
| 0xC0261009 | 监视器描述符包含无效的详细计时块。 |
Monitor descriptor contains an invalid detailed timing block. |
| 0xC026100A | 监视器描述符包含的制造日期无效。 |
Monitor descriptor contains invalid manufacture date. |
| 0xC0262000 | 创建非托管主分配需要独占模式所有权。 |
Exclusive mode ownership is needed to create unmanaged primary allocation. |
| 0xC0262001 | 驱动程序需要更多 DMA 缓冲区空间以完成请求的操作。 |
The driver needs more DMA buffer space in order to complete the requested operation. |
| 0xC0262002 | 指定的显示适配器句柄无效。 |
Specified display adapter handle is invalid. |
| 0xC0262003 | 指定的显示适配器及其所有状态已重置。 |
Specified display adapter and all of its state has been reset. |
| 0xC0262004 | 驱动程序堆栈与预期的驱动程序模型不匹配。 |
The driver stack doesn't match the expected driver model. |
| 0xC0262005 | 已经显示，但导致桌面模式更改 |
Present happened but ended up into the changed desktop mode |
| 0xC0262006 | 由于桌面封闭，因此无法显示任何内容 |
Nothing to present due to desktop occlusion |
| 0xC0262007 | 由于拒绝桌面访问，因此无法显示 |
Not able to present due to denial of desktop access |
| 0xC0262008 | 无法显示颜色转换 |
Not able to present with color convertion |
| 0xC0262009 | 内核驱动程序检测到它和用户模式驱动程序之间的版本不匹配。 |
The kernel driver detected a version mismatch between it and the user mode driver. |
| 0xC026200B | 当前重定向被禁用(桌面窗口管理子系统关闭)。 |
Present redirection is disabled (desktop windowing management subsystem is off). |
| 0xC026200C | 以前的独占 VidPn 源所有者已释放其所有权 |
Previous exclusive VidPn source owner has released its ownership |
| 0xC026200D | 无法使用 Window DC 进行演示 |
Window DC is not available for presentation |
| 0xC026200E | 已禁用无窗口显示(桌面窗口管理子系统已关闭)。 |
Windowless present is disabled (desktop windowing management subsystem is off). |
| 0xC0262100 | 可用视频内存不足，无法完成操作。 |
Not enough video memory available to complete the operation. |
| 0xC0262101 | 无法探测和锁定分配的基础内存。 |
Couldn't probe and lock the underlying memory of an allocation. |
| 0xC0262102 | 分配当前正忙。 |
The allocation is currently busy. |
| 0xC0262103 | 正在引用的对象已达到最大引用计数，无法进一步引用。 |
An object being referenced has reach the maximum reference count already and can't be reference further. |
| 0xC0262104 | 由于当前的某个现有条件，问题无法解决。应稍后重试解决此问题。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again later. |
| 0xC0262105 | 由于当前的某个现有条件，问题无法解决。应立即重试解决此问题。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately. |
| 0xC0262106 | 分配无效。 |
The allocation is invalid. |
| 0xC0262107 | 当前没有更多取消调配的孔径可用。 |
No more unswizzling aperture are currently available. |
| 0xC0262108 | 当前分配无法由孔径取消调配。 |
The current allocation can't be unswizzled by an aperture. |
| 0xC0262109 | 请求失败，因为无法收回已固定的分配。 |
The request failed because a pinned allocation can't be evicted. |
| 0xC0262110 | 无法从分配的当前段位置使用该分配进行指定的操作。 |
The allocation can't be used from its current segment location for the specified operation. |
| 0xC0262111 | 锁定的分配无法用于当前的命令缓冲区。 |
A locked allocation can't be used in the current command buffer. |
| 0xC0262112 | 正在引用的分配已永久关闭。 |
The allocation being referenced has been closed permanently. |
| 0xC0262113 | 正在引用的分配实例无效。 |
An invalid allocation instance is being referenced. |
| 0xC0262114 | 正在引用的分配句柄无效。 |
An invalid allocation handle is being referenced. |
| 0xC0262115 | 正在引用的分配不属于当前设备。 |
The allocation being referenced doesn't belong to the current device. |
| 0xC0262116 | 指定的分配已丢失其内容。 |
The specified allocation lost its content. |
| 0xC0262200 | 在给定的设备上检测到 GPU 异常。无法计划该设备。 |
GPU exception is detected on the given device. The device is not able to be scheduled. |
| 0xC0262300 | 指定的 VidPN 拓扑无效。 |
Specified VidPN topology is invalid. |
| 0xC0262301 | 指定的 VidPN 拓扑有效，但此型号的显示适配器不支持。 |
Specified VidPN topology is valid but is not supported by this model of the display adapter. |
| 0xC0262302 | 指定的 VidPN 拓扑有效，但由于其资源的当前分配，此时不受显示适配器支持。 |
Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources. |
| 0xC0262303 | 指定的 VidPN 句柄无效。 |
Specified VidPN handle is invalid. |
| 0xC0262304 | 指定的视频显示源无效。 |
Specified video present source is invalid. |
| 0xC0262305 | 指定的视频显示目标无效。 |
Specified video present target is invalid. |
| 0xC0262306 | 不支持指定的 VidPN 模态(例如，其中至少两个固定模式的功能无效)。 |
Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional). |
| 0xC0262308 | 指定的 VidPN 源模式集无效。 |
Specified VidPN source mode set is invalid. |
| 0xC0262309 | 指定的 VidPN 目标模式集无效。 |
Specified VidPN target mode set is invalid. |
| 0xC026230A | 指定的视频信号频率无效。 |
Specified video signal frequency is invalid. |
| 0xC026230B | 指定的视频信号活动区域无效。 |
Specified video signal active region is invalid. |
| 0xC026230C | 指定的视频信号总区域无效。 |
Specified video signal total region is invalid. |
| 0xC0262310 | 指定的视频显示源模式无效。 |
Specified video present source mode is invalid. |
| 0xC0262311 | 指定的视频显示目标模式无效。 |
Specified video present target mode is invalid. |
| 0xC0262312 | 固定的模式必须保持在 VidPN 的功能模态枚举上的集中。 |
Pinned mode must remain in the set on VidPN's cofunctional modality enumeration. |
| 0xC0262313 | 指定的视频显示路径已经存在于 VidPN 的拓扑中。 |
Specified video present path is already in VidPN's topology. |
| 0xC0262314 | 指定的模式已经存在于模式集中。 |
Specified mode is already in the mode set. |
| 0xC0262315 | 指定的视频显示源集无效。 |
Specified video present source set is invalid. |
| 0xC0262316 | 指定的视频显示目标集无效。 |
Specified video present target set is invalid. |
| 0xC0262317 | 指定的视频显示源已经存在于视频显示源集中。 |
Specified video present source is already in the video present source set. |
| 0xC0262318 | 指定的视频显示目标已经存在于视频显示目标集中。 |
Specified video present target is already in the video present target set. |
| 0xC0262319 | 指定的 VidPN 显示路径无效。 |
Specified VidPN present path is invalid. |
| 0xC026231A | 微型端口没有对指定 VidPN 的拓扑的增量的建议。 |
Miniport has no recommendation for augmentation of the specified VidPN's topology. |
| 0xC026231B | 指定的监视器频率范围集无效。 |
Specified monitor frequency range set is invalid. |
| 0xC026231C | 指定的监视器频率范围无效。 |
Specified monitor frequency range is invalid. |
| 0xC026231D | 指定的频率范围不在指定的监视器频率范围集中。 |
Specified frequency range is not in the specified monitor frequency range set. |
| 0xC026231F | 指定的频率范围已经存在于指定的监视器频率范围集中。 |
Specified frequency range is already in the specified monitor frequency range set. |
| 0xC0262320 | 指定的模式集已经过时。请重新获取新的模式集。 |
Specified mode set is stale. Please reacquire the new mode set. |
| 0xC0262321 | 指定的监视器源模式集无效。 |
Specified monitor source mode set is invalid. |
| 0xC0262322 | 指定的监视器源模式无效。 |
Specified monitor source mode is invalid. |
| 0xC0262323 | 关于在当前显示适配器配置下提供有效 VidPN 的请求，微型端口无任何建议。 |
Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration. |
| 0xC0262324 | 集中的另一模式已经在使用指定模式的 ID。 |
ID of the specified mode is already used by another mode in the set. |
| 0xC0262325 | 系统无法确定显示适配器和与其连接的监视器都支持的模式。 |
System failed to determine a mode that is supported by both the display adapter and the monitor connected to it. |
| 0xC0262326 | 视频显示目标的数目必须大于或等于视频显示源的数目。 |
Number of video present targets must be greater than or equal to the number of video present sources. |
| 0xC0262327 | 指定的显示路径不在 VidPN 的拓扑中。 |
Specified present path is not in VidPN's topology. |
| 0xC0262328 | 显示适配器必须至少有一个视频显示源。 |
Display adapter must have at least one video present source. |
| 0xC0262329 | 显示适配器必须至少有一个视频显示目标。 |
Display adapter must have at least one video present target. |
| 0xC026232A | 指定的监视器描述符集无效。 |
Specified monitor descriptor set is invalid. |
| 0xC026232B | 指定的监视器描述符无效。 |
Specified monitor descriptor is invalid. |
| 0xC026232C | 指定的描述符不在指定的监视器描述符集中。 |
Specified descriptor is not in the specified monitor descriptor set. |
| 0xC026232D | 指定的描述符已经存在于指定的监视器描述符集中。 |
Specified descriptor is already in the specified monitor descriptor set. |
| 0xC026232E | 集中的另一描述符已经在使用指定监视器描述符的 ID。 |
ID of the specified monitor descriptor is already used by another descriptor in the set. |
| 0xC026232F | 指定的视频显示目标子集类型无效。 |
Specified video present target subset type is invalid. |
| 0xC0262330 | 如界面语义所定义，两个或多个指定的资源彼此不相关。 |
Two or more of the specified resources are not related to each other, as defined by the interface semantics. |
| 0xC0262331 | 集中的另一源已经在使用指定视频显示源的 ID。 |
ID of the specified video present source is already used by another source in the set. |
| 0xC0262332 | 集中的另一目标已经在使用指定视频现有目标的 ID。 |
ID of the specified video present target is already used by another target in the set. |
| 0xC0262333 | 指定的 VidPN 源无法使用，因为没有可用的 VidPN 目标与其连接。 |
Specified VidPN source cannot be used because there is no available VidPN target to connect it to. |
| 0xC0262334 | 新到的监视器无法关联显示适配器。 |
Newly arrived monitor could not be associated with a display adapter. |
| 0xC0262335 | 问题中的显示适配器没有关联的 VidPN 管理器。 |
Display adapter in question does not have an associated VidPN manager. |
| 0xC0262336 | 问题中的显示适配器的 VidPN 管理器没有活动的 VidPN。 |
VidPN manager of the display adapter in question does not have an active VidPN. |
| 0xC0262337 | 指定的 VidPN 拓扑已过时。请重新获取新的拓扑。 |
Specified VidPN topology is stale. Please reacquire the new topology. |
| 0xC0262338 | 指定的视频显示目标上未连接监视器。 |
There is no monitor connected on the specified video present target. |
| 0xC0262339 | 指定的源不是指定的 VidPN 拓扑的一部分。 |
Specified source is not part of the specified VidPN's topology. |
| 0xC026233A | 指定的主表面大小无效。 |
Specified primary surface size is invalid. |
| 0xC026233B | 指定的可见区域大小无效。 |
Specified visible region size is invalid. |
| 0xC026233C | 指定的步幅无效。 |
Specified stride is invalid. |
| 0xC026233D | 指定的像素格式无效。 |
Specified pixel format is invalid. |
| 0xC026233E | 指定的颜色基础无效。 |
Specified color basis is invalid. |
| 0xC026233F | 指定的像素值访问模式无效。 |
Specified pixel value access mode is invalid. |
| 0xC0262340 | 所指定目标不是所指定 VidPN 的拓扑的一部分。 |
Specified target is not part of the specified VidPN's topology. |
| 0xC0262341 | 无法获取显示模式管理界面。 |
Failed to acquire display mode management interface. |
| 0xC0262342 | 指定的 VidPN 源已经由 DMM 客户端拥有，在该客户端将其释放之前，无法使用。 |
Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it. |
| 0xC0262343 | 指定的 VidPN 处于活动中，无法访问。 |
Specified VidPN is active and cannot be accessed. |
| 0xC0262344 | 指定的 VidPN 显示路径重要性顺序无效。 |
Specified VidPN present path importance ordinal is invalid. |
| 0xC0262345 | 指定的 VidPN 显示路径内容规格转换无效。 |
Specified VidPN present path content geometry transformation is invalid. |
| 0xC0262346 | 指定的内容规格转换在相应的 VidPN 显示路径中不受支持。 |
Specified content geometry transformation is not supported on the respective VidPN present path. |
| 0xC0262347 | 指定的伽马校正无效。 |
Specified gamma ramp is invalid. |
| 0xC0262348 | 在各自的 VidPN 显示路径上不支持指定的伽马校正。 |
Specified gamma ramp is not supported on the respective VidPN present path. |
| 0xC0262349 | 多示例在相应的 VidPN 显示路径中不受支持。 |
Multi-sampling is not supported on the respective VidPN present path. |
| 0xC026234A | 指定的模式不在指定的模式集中。 |
Specified mode is not in the specified mode set. |
| 0xC026234D | 指定的 VidPN 拓扑建议原因无效。 |
Specified VidPN topology recommendation reason is invalid. |
| 0xC026234E | 指定的 VidPN 显示路径内容类型无效。 |
Specified VidPN present path content type is invalid. |
| 0xC026234F | 指定的 VidPN 显示路径副本保护类型无效。 |
Specified VidPN present path copy protection type is invalid. |
| 0xC0262350 | 给定的 VidPN 源/目标在任何给定的时间最多可以存在一个未分配的模式集。 |
No more than one unassigned mode set can exist at any given time for a given VidPN source/target. |
| 0xC0262352 | 指定的扫描行排序类型无效。 |
Specified scanline ordering type is invalid. |
| 0xC0262353 | 指定的 VidPN 不允许拓扑更改。 |
Topology changes are not allowed for the specified VidPN. |
| 0xC0262354 | 所有可用的重要性序号已用于指定的拓扑。 |
All available importance ordinals are already used in specified topology. |
| 0xC0262355 | 指定的主表面具有与当前主表面不同的专用格式属性 |
Specified primary surface has a different private format attribute than the current primary surface |
| 0xC0262356 | 指定的模式修剪算法无效 |
Specified mode pruning algorithm is invalid |
| 0xC0262357 | 指定的监视器原始功能无效。 |
Specified monitor capability origin is invalid. |
| 0xC0262358 | 指定的监视器频率范围限制无效。 |
Specified monitor frequency range constraint is invalid. |
| 0xC0262359 | 现有路径的数量已达到支持的最大数量。 |
Maximum supported number of present paths has been reached. |
| 0xC026235A | 对于指定的 VidPN 拓扑的指定源，微型端口请求取消其增量。 |
Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology. |
| 0xC026235B | 未识别指定的客户端类型。 |
Specified client type was not recognized. |
| 0xC026235C | 此适配器上未设置客户端 VidPN (例如，此适配器上没有发生任何在用户模式下启动的模式更改)。 |
Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet). |
| 0xC0262400 | 指定的显示适配器子设备已经具有与其连接的外部设备。 |
Specified display adapter child device already has an external device connected to it. |
| 0xC0262401 | 指定的显示适配器子设备不支持描述符暴露。 |
Specified display adapter child device does not support descriptor exposure. |
| 0xC0262430 | 显示适配器未链接到任何其他适配器。 |
The display adapter is not linked to any other adapters. |
| 0xC0262431 | 尚未枚举链接配置中的主导适配器。 |
Lead adapter in a linked configuration was not enumerated yet. |
| 0xC0262432 | 尚未枚举链接的配置中的某些链适配器。 |
Some chain adapters in a linked configuration were not enumerated yet. |
| 0xC0262433 | 由于未知故障，链接的适配器的链启动未准备就绪。 |
The chain of linked adapters is not ready to start because of an unknown failure. |
| 0xC0262434 | 当链链接尚未启动时，尝试启动前导链接显示适配器。 |
An attempt was made to start a lead link display adapter when the chain links were not started yet. |
| 0xC0262435 | 当链链接断电时，尝试给前导链接显示适配器通电。 |
An attempt was made to power up a lead link display adapter when the chain links were powered down. |
| 0xC0262436 | 发现适配器链接处于不一致状态。不是所有适配器都处于预期的 PNP/电源状态。 |
The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state. |
| 0xC0262438 | 尝试启动的驱动程序与 POSTed 显示适配器的驱动程序不同。 |
The driver trying to start is not the same as the driver for the POSTed display adapter. |
| 0xC026243B | 正在尝试的操作要求显示适配器处于静止状态。 |
An operation is being attempted that requires the display adapter to be in a quiescent state. |
| 0xC0262500 | 驱动程序不支持 OPM。 |
The driver does not support OPM. |
| 0xC0262501 | 驱动程序不支持 COPP。 |
The driver does not support COPP. |
| 0xC0262502 | 驱动程序不支持 UAB。 |
The driver does not support UAB. |
| 0xC0262503 | 指定的加密参数无效。 |
The specified encrypted parameters are invalid. |
| 0xC0262505 | 传递到此函数的 GDI 显示设备不具有任何活动的视频输出。 |
The GDI display device passed to this function does not have any active video outputs. |
| 0xC026250B | 内部错误引起该操作失败。 |
An internal error caused this operation to fail. |
| 0xC026250C | 函数失败，因为调用方传递进无效的 OPM 用户模式句柄。 |
The function failed because the caller passed in an invalid OPM user mode handle. |
| 0xC026250E | 无法返回证书，因为传递到函数的证书缓冲区过小。 |
A certificate could not be returned because the certificate buffer passed to the function was too small. |
| 0xC026250F | 无法创建视频输出，因为帧缓冲区处于跨越模式。 |
A video output could not be created because the frame buffer is in spanning mode. |
| 0xC0262510 | 无法创建视频输出，因为帧缓冲区处于影院模式。 |
A video output could not be created because the frame buffer is in theater mode. |
| 0xC0262511 | 函数出现错误，原因是显示适配器的硬件功能性扫描验证图形硬件失败。 |
The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware. |
| 0xC0262512 | 传递给此函数的“HDCP 系统可更新性消息”不符合 HDCP 1.1 规范第 5 部分的要求。 |
The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification. |
| 0xC0262513 | 视频输出无法启用高带宽数字内容保护(HDCP)系统，因为它不支持 HDCP。 |
The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP. |
| 0xC0262514 | 视频输出无法启用模拟版权保护(ACP)，因为它并支持 ACP。 |
The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP. |
| 0xC0262515 | 视频输出无法启用内容生成管理系统模拟(CGMS-A)保护技术，因为它不支持 CGMS-A。 |
The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A. |
| 0xC0262516 | IOPMVideoOutput::GetInformation 方法无法返回正在使用的 SRM 的版本，因为应用程序从未将一个 SRM 成功传递到视频输出。 |
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. |
| 0xC0262517 | IOPMVideoOutput::Configure 方法无法启用指定的输出保护技术，因为输出的屏幕分辨率太高。 |
The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high. |
| 0xC0262518 | IOPMVideoOutput::Configure 方法无法启用 HDCP，因为其他的物理输出已在使用显示适配器的 HDCP 硬件。 |
The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs. |
| 0xC026251A | 操作系统异步毁坏此 OPM 视频输出，原因是该操作系统的状态已发生更改。出现此错误通常是由于以下原因: 与此视频输出相关联的监视器 PDO 已移除；与此视频输出相关联的监视器 PDO 已停用；视频输出的会话已成为非控制台会话或视频输出的桌面已成为非活动桌面。 |
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. |
| 0xC026251B | 方法失败，因为会话正在更改其类型。会话正在更改其类型时，无法调用任何 IOPMVideoOutput 方法。当前存在三种类型的会话: 控制台、断开连接和远程。 |
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. |
| 0xC026251C | IOPMVideoOutput::COPPCompatibleGetInformation、IOPMVideoOutput::GetInformation 或 IOPMVideoOutput::Configure 方法失败。当调用程序尝试使用 COPP 特定的命令，而视频输出仅具有 OPM 语义时会返回该错误。 |
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. |
| 0xC026251D | 如果传入的序列号不是所需的序列号，或者传入的 OMAC 值无效，则 IOPMVideoOutput::GetInformation 和 IOPMVideoOutput::COPPCompatibleGetInformation 方法会返回该错误。 |
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. |
| 0xC026251E | 由于显示器驱动程序内部出现错误，因此该方法失败。 |
The method failed because an unexpected error occurred inside of a display driver. |
| 0xC026251F | IOPMVideoOutput::COPPCompatibleGetInformation、IOPMVideoOutput::GetInformation 或 IOPMVideoOutput::Configure 方法失败。当调用程序尝试使用 OPM 特定的命令，而视频输出仅具有 COPP 语义时会返回该错误。 |
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. |
| 0xC0262520 | 由于显示器驱动程序不支持 OPM_GET_ACP_AND_CGMSA_SIGNALING 和 OPM_SET_ACP_AND_CGMSA_SIGNALING GUID，IOPMVideoOutput::COPPCompatibleGetInformation 或 IOPMVideoOutput::Configure 方法失败。 |
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. |
| 0xC0262521 | 如果传入的序列号不是所需的序列号，或者传入的 OMAC 值无效，IOPMVideoOutput::Configure 函数会返回该错误代码。 |
The 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. |
| 0xC0262580 | 连接到指定视频输出的监视器没有 I2C 总线。 |
The monitor connected to the specified video output does not have an I2C bus. |
| 0xC0262581 | I2C 总线上的设备没有指定的地址。 |
No device on the I2C bus has the specified address. |
| 0xC0262582 | 将数据传输到 I2C 总线上的设备时出错。 |
An error occurred while transmitting data to the device on the I2C bus. |
| 0xC0262583 | 从 I2C 总线上的设备接收数据时出错。 |
An error occurred while receiving data from the device on the I2C bus. |
| 0xC0262584 | 该监视器不支持指定的 VCP 代码。 |
The monitor does not support the specified VCP code. |
| 0xC0262585 | 从监视器接收到的数据无效。 |
The data received from the monitor is invalid. |
| 0xC0262586 | 函数失败，原因是操作系统使用 DDC/CI Get Timing Report Timing Message 命令获取监视器的计时报表时，监视器返回的计时状态字节无效。 |
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. |
| 0xC0262589 | 操作失败，原因是 DDC/CI 消息的命令字段中的值无效。 |
An operation failed because a DDC/CI message had an invalid value in its command field. |
| 0xC026258A | 由于 DDC/CI 消息的字段长度包含无效的值，因此出现错误。 |
An error occurred because the field length of a DDC/CI message contained an invalid value. |
| 0xC026258B | 出现错误，原因是 DDC/CI 消息中的校验和字段与该消息计算出的校验和值不匹配。该错误表示数据从监视器传输到计算机时被损坏。 |
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. |
| 0xC026258C | 由于向函数传递了无效的监视器句柄，因此该函数失败。 |
This function failed because an invalid monitor handle was passed to it. |
| 0xC026258D | 操作系统异步毁坏了与此句柄相对应的监视器，原因是操作系统的状态已更改。发生此错误的原因通常为: 与此句柄相关联的监视器 PDO 已移除；与此句柄相关联的监视器 PDO 已停用；或已发生显示模式更改。当 Windows 向应用程序发送 WM_DISPLAYCHANGE Windows 消息时，显示模式将更改。 |
The 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. |
| 0xC02625D8 | VCP 连续代码的当前值大于其最大值。此错误代码表明监视器返回的值无效。 |
A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value. |
| 0xC02625DF | SetMonitorColorTemperature()的调用者给它传递了一种当前监视器不支持的色温。该错误表示此监视器违反了 MCCS 2.0 规范或 MCCS 2.0 修订版 1 规范。 |
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. |
| 0xC02625E0 | 仅当程序运行在本地控制台会话中时才能使用此函数。如果程序运行在远程桌面会话或终端服务器会话中时，则无法使用此函数。 |
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. |
| 0xC02625E1 | 该函数无法找到与指定的 GDI 显示设备名称相对应的实际 GDI 显示设备。 |
This function cannot find an actual GDI display device which corresponds to the specified GDI display device name. |
| 0xC02625E2 | 函数失败，原因是未将指定的 GDI 显示设备连接到 Windows 桌面。 |
The function failed because the specified GDI display device was not attached to the Windows desktop. |
| 0xC02625E3 | 该函数不支持 GDI 镜像显示设备，因为 GDI 镜像显示设备没有与其关联的任何物理监视器。 |
This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them. |
| 0xC02625E4 | 由于向函数传递了无效的指针参数，该函数失败。如果指针参数为 NULL、指向无效地址、指向内核模式地址或者没有正确对齐，则指针参数无效。 |
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. |
| 0xC02625E5 | 由于指定的 GDI 设备没有与其关联的任何监视器，因此该函数失败。 |
The function failed because the specified GDI device did not have any monitors associated with it. |
| 0xC02625E6 | 传递到函数的数组无法包含该函数必须将其复制到数组的所有数据。 |
An array passed to the function cannot hold all of the data that the function must copy into the array. |
| 0xC02625E7 | 内部错误导致此操作失败。 |
An internal error caused an operation to fail. |
| 0xC034100F | 由于本地策略设置，TCP 连接不可卸载。 |
The TCP connection is not offloadable because of a local policy setting. |
| 0xC0341012 | Chimney 卸载目标无法卸载 TCP 连接。 |
The TCP connection is not offloadable by the Chimney Offload target. |
| 0xC0341013 | IP 路径对象处于无法卸载的状态。 |
The IP Path object is not in an offloadable state. |
| 0xC0350002 | 虚拟机监控程序不支持该操作，因为不支持此指定的虚拟化调用代码。 |
The hypervisor does not support the operation because the specified hypercall code is not supported. |
| 0xC0350003 | 虚拟机监控程序不支持此操作，因为不支持虚拟化调用输入注册表的编码。 |
The hypervisor does not support the operation because the encoding for the hypercall input register is not supported. |
| 0xC0350004 | 虚拟机监控程序无法执行此操作，因为某个参数的对齐方式无效。 |
The hypervisor could not perform the operation because a parameter has an invalid alignment. |
| 0xC0350005 | 虚拟机监控程序无法执行此操作，因为指定的参数无效。 |
The hypervisor could not perform the operation because an invalid parameter was specified. |
| 0xC0350006 | 拒绝对指定对象的访问。 |
Access to the specified object was denied. |
| 0xC0350007 | 虚拟机监控程序无法执行此操作，因为此分区正在进入或处于无效状态。 |
The hypervisor could not perform the operation because the partition is entering or in an invalid state. |
| 0xC0350008 | 不允许在当前状态下操作。 |
The operation is not allowed in the current state. |
| 0xC0350009 | 虚拟机监控程序未识别指定的分区属性。 |
The hypervisor does not recognize the specified partition property. |
| 0xC035000A | 指定的分区属性值超出范围或违反固定值。 |
The specified value of a partition property is out of range or violates an invariant. |
| 0xC035000B | 虚拟机监控程序池中没有足够的内存，无法完成此操作。 |
There is not enough memory in the hypervisor pool to complete the operation. |
| 0xC035000C | 超过了分区层次结构的最大分区深度。 |
The maximum partition depth has been exceeded for the partition hierarchy. |
| 0xC035000D | 具有指定分区 ID 的分区不存在。 |
A partition with the specified partition Id does not exist. |
| 0xC035000E | 虚拟机监控程序无法执行此操作，因为指定的 VP 索引无效。 |
The hypervisor could not perform the operation because the specified VP index is invalid. |
| 0xC0350011 | 虚拟机监控程序无法执行此操作，因为指定的端口标识符无效。 |
The hypervisor could not perform the operation because the specified port identifier is invalid. |
| 0xC0350012 | 虚拟机监控程序无法执行此操作，因为指定的连接标识符无效。 |
The hypervisor could not perform the operation because the specified connection identifier is invalid. |
| 0xC0350013 | 没有提供足够的缓冲区，无法发送消息。 |
Not enough buffers were supplied to send a message. |
| 0xC0350014 | 上一个虚拟中断尚未被确认。 |
The previous virtual interrupt has not been acknowledged. |
| 0xC0350015 | 为指示的操作使用的虚拟处理器未处于正常状态。 |
A virtual processor is not in the correct state for the indicated operation. |
| 0xC0350016 | 上一个虚拟中断已被确认。 |
The previous virtual interrupt has already been acknowledged. |
| 0xC0350017 | 指示的分区未处于进行保存或还原的有效状态。 |
The indicated partition is not in a valid state for saving or restoring. |
| 0xC0350018 | 虚拟机监控程序无法完成此操作，因为综合中断控制器(SynIC)的所需功能已禁用。 |
The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled. |
| 0xC0350019 | 虚拟机监控程序无法执行此操作，因为该对象或值已在使用中，或已被用于无法允许完成此操作的目的。 |
The 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. |
| 0xC035001A | 邻近域信息无效。 |
The proximity domain information is invalid. |
| 0xC035001B | 尝试检索调试数据失败，因为没有数据可用。 |
An attempt to retrieve debugging data failed because none was available. |
| 0xC035001C | 要用于调试的物理连接自上次操作以来尚未记录任何接收活动。 |
The physical connection being used for debuggging has not recorded any receive activity since the last operation. |
| 0xC035001D | 没有足够资源，无法完成操作。 |
There are not enough resources to complete the operation. |
| 0xC035001E | 虚拟机监控程序功能对于该用户来说不可用。 |
A hypervisor feature is not available to the user. |
| 0xC0350033 | 指定的缓冲区太小，无法包含所有的请求数据。 |
The specified buffer was too small to contain all of the requested data. |
| 0xC0350038 | 当前使用的域达到平台 I/O 重新映射硬件支持的最大域数。没有可用的域，无法将该设备分配给此分区。 |
The 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. |
| 0xC035003C | 验证处理器的 CPUID 数据失败。 |
Validation of CPUID data of the processor failed. |
| 0xC035003D | 验证处理器的 XSAVE CPUID 数据失败。 |
Validation of XSAVE CPUID data of the processor failed. |
| 0xC035003E | 处理器未在超时期限内响应。 |
Processor did not respond within the timeout period. |
| 0xC035003F | 已在 BIOS 中启用 SMX。 |
SMX has been enabled in the BIOS. |
| 0xC0350050 | 提供的注册值无效。 |
The supplied register value is invalid. |
| 0xC0350051 | 提供的虚拟信任级别的状态不正确，无法执行请求的操作。 |
The supplied virtual trust level is not in the correct state to perform the requested operation. |
| 0xC0350055 | 不执行功能(NX)不存在或未在 BIOS 中启用。 |
No execute feature (NX) is not present or not enabled in the BIOS. |
| 0xC0350057 | 提供的设备 ID 无效。 |
The supplied device ID is invalid. |
| 0xC0350058 | 在当前设备状态下不允许此操作。 |
The operation is not allowed in the current device state. |
| 0xC0350060 | 提供的页面请求指定了来宾无权执行的内存访问。 |
The supplied page request specifies a memory access that the guest does not have permissions to perform. |
| 0xC035006F | 具有指定 CPU 组 ID 的 CPU 组不存在。 |
A CPU group with the specified CPU group Id does not exist. |
| 0xC0350070 | 由于 CPU 组正在进入或处于无效状态，虚拟机监控程序无法执行该操作。 |
The hypervisor could not perform the operation because the CPU group is entering or in an invalid state. |
| 0xC0350071 | 请求的操作失败。 |
The requested operation failed. |
| 0xC0350072 | 虚拟机监控程序无法执行此操作，因为嵌套虚拟化处于活动状态时不允许此操作。 |
The hypervisor could not perform the operation because it is not allowed with nested virtualization active. |
| 0xC0351000 | 该系统上没有虚拟机监控程序。 |
No hypervisor is present on this system. |
| 0xC0370001 | 已注册虚拟基础结构驱动程序的处理程序。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370002 | 已注册的虚拟基础结构驱动程序的处理程序数量超出了最大值。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370003 | 虚拟基础结构驱动程序的消息队列已满，无法接收新的消息。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370004 | 不存在用于处理虚拟基础结构驱动程序的消息的处理程序。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370005 | 虚拟基础结构驱动程序的分区或消息队列的名称无效。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370006 | 虚拟基础结构驱动程序的分区名超出最大值。 |
The partition name of the virtualization infrastructure driver exceeds the maximum. |
| 0xC0370007 | 虚拟基础结构驱动程序的消息队列名称超出最大值。 |
The message queue name of the virtualization infrastructure driver exceeds the maximum. |
| 0xC0370008 | 无法为虚拟基础结构驱动程序创建分区，因为已存在具有相同名称的另一分区。 |
Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists. |
| 0xC0370009 | 虚拟基础结构驱动程序遇到错误。请求的分区不存在。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC037000A | 虚拟基础结构驱动程序遇到错误。无法找到请求的分区。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC037000B | 已存在与该虚拟化基础结构驱动程序相同的消息队列名称。 |
A message queue with the same name already exists for the virtualization infrastructure driver. |
| 0xC037000C | 无法映射虚拟基础结构驱动程序的内存块页面，因为已达到页面映射限制。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC037000D | 虚拟基础结构驱动程序的内存块仍在使用中，无法毁坏。 |
The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed. |
| 0xC037000E | 无法解锁来宾操作系统内存地址的页面数组，因为它与之前的锁定请求不匹配。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC037000F | 非统一内存访问 (NUMA) 节点设置与系统 NUMA 拓扑不相符。为了启动虚拟机，你需要修改 NUMA 配置。 |
The 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. |
| 0xC0370010 | 非统一内存访问(NUMA)节点索引与系统 NUMA 拓扑中的有效索引不匹配。 |
The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology. |
| 0xC0370011 | 虚拟基础结构驱动程序的内存块已与消息队列关联。 |
The memory block for the virtualization infrastructure driver is already associated with a message queue. |
| 0xC0370012 | 此句柄不是虚拟基础结构驱动程序的有效内存块句柄。 |
The handle is not a valid memory block handle for the virtualization infrastructure driver. |
| 0xC0370013 | 请求超出了虚拟基础结构驱动程序的内存块页面限制。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370014 | 此句柄不是虚拟基础结构驱动程序的有效消息队列句柄。 |
The handle is not a valid message queue handle for the virtualization infrastructure driver. |
| 0xC0370015 | 此句柄不是虚拟基础结构驱动程序的有效页面范围句柄。 |
The handle is not a valid page range handle for the virtualization infrastructure driver. |
| 0xC0370016 | 无法安装客户端通知，因为没有任何虚拟基础结构驱动程序消息队列与内存块关联。 |
Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block. |
| 0xC0370017 | 请求锁定或映射内存块页面失败，因为已达到虚拟基础结构驱动程序内存块限制。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370018 | 此句柄不是用于虚拟基础结构驱动程序的有效父级分区映射句柄。 |
The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver. |
| 0xC0370019 | 无法在内存块上创建通知，因为正在使用该内存块。 |
Notifications cannot be created on the memory block because it is use. |
| 0xC037001A | 虚拟基础结构驱动程序的消息队列已关闭。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC037001B | 无法将虚拟处理器添加到分区，因为该分区已达到最大使用量。 |
Cannot add a virtual processor to the partition because the maximum has been reached. |
| 0xC037001C | 无法立即停止虚拟处理器，因为出现了挂起截获。 |
Cannot stop the virtual processor immediately because of a pending intercept. |
| 0xC037001D | 虚拟处理器的状态无效。重新启动虚拟机可能会解决此问题。如果问题仍然存在，请尝试重新启动物理计算机。 |
Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037001E | 已达到虚拟基础结构驱动程序的内核模式客户端的最大数量。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC037001F | 已初始化虚拟基础结构驱动程序的此内核模式界面。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370020 | 无法为虚拟化基础结构驱动程序多次设置或重置内存块属性。重新启动虚拟机可能会解决此问题。如果问题仍然存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370021 | 此页面范围的内存映射 I/O 不再存在。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
The 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. |
| 0xC0370022 | 锁定或解除锁定请求使用的来宾操作系统内存地址无效。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370023 | 无法销毁或重用为虚拟基础结构驱动程序设置的保留页面，因为它正在使用中。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370024 | 为虚拟基础结构驱动程序设置的保留页面太小，无法用于锁定请求。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370025 | 无法锁定或映射虚拟基础结构驱动程序的内存块页面，因为已使用保留页面设置页将其锁定。重新启动虚拟机可能会解决此问题。如果问题继续存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370026 | 无法创建虚拟化基础结构驱动程序的内存块，因为所请求页面的数量超过限制。重新启动虚拟机可能会解决此问题。如果问题仍然存在，请尝试重新启动物理计算机。 |
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. |
| 0xC0370027 | 无法还原此虚拟机，因为无法读取保存的状态数据。请删除保存的状态数据，然后尝试启动虚拟机。 |
Cannot 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. |
| 0xC0370028 | 无法还原此虚拟机，因为未识别从保存的状态数据读取的项目。请删除保存的状态数据，然后尝试启动该虚拟机。 |
Cannot 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. |
| 0xC0370029 | 无法将此虚拟机还原为保存的状态，因为虚拟机监控程序不兼容。请删除保存的状态数据，然后尝试启动该虚拟机。 |
Cannot 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. |
| 0xC037002A | 指定的 VTL 无权访问该资源。 |
The specified VTL does not have the permission to access the resource. |
| 0xC0370100 | 启动时计算系统意外终止。 |
The compute system unexpectedly terminated while starting. |
| 0xC0370101 | 容器的操作系统与主机的操作系统不匹配。 |
The operating system of the container does not match the operating system of the host. |
| 0xC0370102 | 由于未安装 Hyper-V，虚拟机无法启动。 |
A Virtual Machine could not be started because Hyper-V is not installed. |
| 0xC0370103 | 启动异步操作的调用成功，将在后台执行相应操作。 |
The call to start an asynchronous operation succeeded and the operation is performed in the background. |
| 0xC0370104 | 已超出支持的通知回调数。 |
The supported number of notification callbacks has been exceeded. |
| 0xC0370105 | 请求的计算系统操作在当前状态下无效。 |
The requested compute system operation is not valid in the current state. |
| 0xC0370106 | 计算系统已意外退出。 |
The compute system exited unexpectedly. |
| 0xC0370107 | 计算系统被强制终止。 |
The compute system was forcefully terminated. |
| 0xC0370108 | 无法通过托管容器的虚拟机建立连接。 |
A connection could not be established with the Virtual Machine hosting the Container. |
| 0xC0370109 | 由于未从托管容器的虚拟机收到响应，操作超时。 |
The operation timed out because a response was not received from the Virtual Machine hosting the Container. |
| 0xC037010A | 与托管容器的虚拟机的连接已关闭。 |
The connection with the Virtual Machine hosting the container was closed. |
| 0xC037010B | Hyper-V 计算服务收到了未知内部消息。 |
An unknown internal message was received by the Hyper-V Compute Service. |
| 0xC037010C | 不支持 Hyper-V 主机与来宾计算服务之间的通信协议版本。 |
The communication protocol version between the Hyper-V Host and Guest Compute Services is not supported. |
| 0xC037010D | 该 JSON 文档无效。 |
The JSON document is invalid. |
| 0xC037010E | 具有指定标识符的计算系统不存在。 |
A Compute System with the specified identifier does not exist. |
| 0xC037010F | 具有指定标识符的计算系统已存在。 |
A Compute System with the specified identifier already exists. |
| 0xC0370110 | 具有指定标识符的计算系统确实已停止。 |
The Compute System with the specified identifier did already stop. |
| 0xC0370111 | Hyper-V 主机和来宾计算服务之间发生通信协议错误。 |
A communication protocol error has occurred between the Hyper-V Host and Guest Compute Service. |
| 0xC0370200 | 找不到具有给定名称的虚拟交换机。 |
A virtual switch with the given name was not found. |
| 0xC0380001 | 配置数据库已满。 |
The configuration database is full. |
| 0xC0380002 | 磁盘上的配置数据已损坏。 |
The configuration data on the disk is corrupted. |
| 0xC0380003 | 磁盘上的配置与内存中的配置不同步。 |
The configuration on the disk is not insync with the in-memory configuration. |
| 0xC0380004 | 无法用新配置更新大多数磁盘。 |
A majority of disks failed to be updated with the new configuration. |
| 0xC0380005 | 磁盘包含非简单卷。 |
The disk contains non-simple volumes. |
| 0xC0380006 | 迁移列表中多次指定了同一磁盘。 |
The same disk was specified more than once in the migration list. |
| 0xC0380007 | 该磁盘已经是动态磁盘。 |
The disk is already dynamic. |
| 0xC0380008 | 指定的磁盘 ID 无效。具有指定磁盘 ID 的磁盘不存在。 |
The specified disk id is invalid. There are no disks with the specified disk id. |
| 0xC0380009 | 指定的磁盘是无效磁盘。无法在无效磁盘上完成操作。 |
The specified disk is an invalid disk. Operation cannot complete on an invalid disk. |
| 0xC038000A | 无法删除指定的磁盘，因为它是最后保留的备用磁盘。 |
The specified disk(s) cannot be removed since it is the last remaining voter. |
| 0xC038000B | 指定磁盘的磁盘布局无效。 |
The specified disk has an invalid disk layout. |
| 0xC038000C | 磁盘布局包含出现在基本分区之后的非基本分区。这是无效的磁盘布局。 |
The disk layout contains non-basic partitions which appear after basic paritions. This is an invalid disk layout. |
| 0xC038000D | 磁盘布局包含非柱面对齐的分区。 |
The disk layout contains partitions which are not cylinder aligned. |
| 0xC038000E | 磁盘布局包含小于最小大小的分区。 |
The disk layout contains partitions which are samller than the minimum size. |
| 0xC038000F | 磁盘布局包含位于逻辑驱动器之间的主分区。这是无效的磁盘布局。 |
The disk layout contains primary partitions in between logical drives. This is an invalid disk layout. |
| 0xC0380010 | 磁盘布局包含的分区数量超过了所支持的最大数量。 |
The disk layout contains more than the maximum number of supported partitions. |
| 0xC0380011 | 缺少指定的磁盘。无法在缺少的磁盘上完成操作。 |
The specified disk is missing. The operation cannot complete on a missing disk. |
| 0xC0380012 | 指定的磁盘非空。 |
The specified disk is not empty. |
| 0xC0380013 | 没有执行此操作所需的足够可用空间。 |
There is not enough usable space for this operation. |
| 0xC0380014 | 坏扇区的强制重设置向量失败。 |
The force revectoring of bad sectors failed. |
| 0xC0380015 | 指定的磁盘具有无效的扇区大小。 |
The specified disk has an invalid sector size. |
| 0xC0380016 | 指定的磁盘集包含存在于该集外部的磁盘上的卷。 |
The specified disk set contains volumes which exist on disks outside of the set. |
| 0xC0380017 | 卷布局中的磁盘为丛中多个成员提供盘区。 |
A disk in the volume layout provides extents to more than one member of a plex. |
| 0xC0380018 | 卷布局中的磁盘对多个丛提供范围。 |
A disk in the volume layout provides extents to more than one plex. |
| 0xC0380019 | 该系统上不支持动态磁盘。 |
Dynamic disks are not supported on this system. |
| 0xC038001A | 指定的范围已经由其他卷使用。 |
The specified extent is already used by other volumes. |
| 0xC038001B | 指定的卷被保留，只能扩展到连续范围。指定的增长卷的范围与指定的卷不连续。 |
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. |
| 0xC038001C | 指定的卷范围不在磁盘的公用区域内。 |
The specified volume extent is not within the public region of the disk. |
| 0xC038001D | 指定的卷范围未进行扇区对齐。 |
The specifed volume extent is not sector aligned. |
| 0xC038001E | 指定的分区重叠了 EBR (MBR 磁盘上扩展分区的第一个轨道)。 |
The specified parition overlaps an EBR (the first track of an extended partition on a MBR disks). |
| 0xC038001F | 指定的范围长度无法用于构建具有指定长度的卷。 |
The specified extent lengths cannot be used to construct a volume with specified length. |
| 0xC0380020 | 系统不支持容错卷。 |
The system does not support fault tolerant volumes. |
| 0xC0380021 | 指定的交错长度无效。 |
The specified interleave length is invalid. |
| 0xC0380022 | 已经达到最大注册用户数。 |
There is already a maximum number of registered users. |
| 0xC0380023 | 指定的成员已经与其他活动成员同步。无需重新生成。 |
The specified member is already in-sync with the other active members. It does not need to be regenerated. |
| 0xC0380024 | 多次指定了同一成员索引。 |
The same member index was specified more than once. |
| 0xC0380025 | 指定的成员索引大于或等于卷丛中的成员数。 |
The specified member index is greater or equal than the number of members in the volume plex. |
| 0xC0380026 | 缺少指定的成员。无法重新生成它。 |
The specified member is missing. It cannot be regenerated. |
| 0xC0380027 | 指定的成员未分离。无法替换未分离的成员。 |
The specified member is not detached. Cannot replace a member which is not detached. |
| 0xC0380028 | 指定的成员已在重新生成。 |
The specified member is already regenerating. |
| 0xC0380029 | 属于该磁盘组的所有磁盘均出现故障。 |
All disks belonging to the pack failed. |
| 0xC038002A | 当前没有要进行通知的注册用户。任务编号不相关，除非存在注册用户。 |
There are currently no registered users for notifications. The task number is irrelevant unless there are registered users. |
| 0xC038002B | 指定的通知用户不存在。注销要通知的用户失败。 |
The specified notification user does not exist. Failed to unregister user for notifications. |
| 0xC038002C | 通知已重置。用于当前用户的通知无效。请注销并重新注册以获得通知。 |
The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications. |
| 0xC038002D | 指定的成员数无效。 |
The specified number of members is invalid. |
| 0xC038002E | 指定的丛数无效。 |
The specified number of plexes is invalid. |
| 0xC038002F | 指定的源磁盘组和目标磁盘组相同。 |
The specified source and target packs are identical. |
| 0xC0380030 | 指定的磁盘组 ID 无效。没有指定磁盘组 ID 的磁盘组。 |
The specified pack id is invalid. There are no packs with the specified pack id. |
| 0xC0380031 | 指定的磁盘组无效。无法使用无效的磁盘组完成操作。 |
The specified pack is the invalid pack. The operation cannot complete with the invalid pack. |
| 0xC0380032 | 指定的磁盘组名称无效。 |
The specified pack name is invalid. |
| 0xC0380033 | 指定的磁盘组脱机。 |
The specified pack is offline. |
| 0xC0380034 | 指定的磁盘组已经具有状态良好磁盘的仲裁。 |
The specified pack already has a quorum of healthy disks. |
| 0xC0380035 | 磁盘组没有状态良好磁盘的仲裁。 |
The pack does not have a quorum of healthy disks. |
| 0xC0380036 | 指定的磁盘具有不受支持的分区形式。仅支持 MBR 和 GPT 分区形式。 |
The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported. |
| 0xC0380037 | 更新磁盘的分区布局失败。 |
Failed to update the disk's partition layout. |
| 0xC0380038 | 指定的丛已经与其他活动丛同步。不需要重新生成它。 |
The specified plex is already in-sync with the other active plexes. It does not need to be regenerated. |
| 0xC0380039 | 多次指定了同一丛索引。 |
The same plex index was specified more than once. |
| 0xC038003A | 指定的丛索引大于或等于卷中的丛数。 |
The specified plex index is greater or equal than the number of plexes in the volume. |
| 0xC038003B | 指定的丛是卷中的最后一个活动丛。无法删除该丛，否则卷将脱机。 |
The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline. |
| 0xC038003C | 缺少指定的丛。 |
The specified plex is missing. |
| 0xC038003D | 当前正在重新生成指定的丛。 |
The specified plex is currently regenerating. |
| 0xC038003E | 指定的丛类型无效。 |
The specified plex type is invalid. |
| 0xC038003F | 仅在 RAID-5 丛上支持该操作。 |
The operation is only supported on RAID-5 plexes. |
| 0xC0380040 | 仅在简单丛上支持该操作。 |
The operation is only supported on simple plexes. |
| 0xC0380041 | 错误设置了 VM_VOLUME_LAYOUT 输入结构中的“大小”字段。 |
The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set. |
| 0xC0380042 | 已有针对通知的挂起请求。请求更多通知之前，请等待返回现有请求。 |
There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications. |
| 0xC0380043 | 当前有一个正在进行的事务。 |
There is currently a transaction in process. |
| 0xC0380044 | 在卷管理器外发生意外的布局更改。 |
An unexpected layout change occurred outside of the volume manager. |
| 0xC0380045 | 指定的卷包含丢失的磁盘。 |
The specified volume contains a missing disk. |
| 0xC0380046 | 指定的卷 ID 无效。没有具有指定卷 ID 的卷。 |
The specified volume id is invalid. There are no volumes with the specified volume id. |
| 0xC0380047 | 指定的卷长度无效。 |
The specified volume length is invalid. |
| 0xC0380048 | 指定的卷大小不是扇区大小的倍数。 |
The specified size for the volume is not a multiple of the sector size. |
| 0xC0380049 | 仅在镜像卷上支持该操作。 |
The operation is only supported on mirrored volumes. |
| 0xC038004A | 指定的卷没有保留分区。 |
The specified volume does not have a retain partition. |
| 0xC038004B | 指定的卷处于脱机状态。 |
The specified volume is offline. |
| 0xC038004C | 指定的卷已经含有保留分区。 |
The specified volume already has a retain partition. |
| 0xC038004D | 指定的范围数无效。 |
The specified number of extents is invalid. |
| 0xC038004E | 加入卷的所有磁盘必须具有相同的扇区大小。 |
All disks participating to the volume must have the same sector size. |
| 0xC038004F | 启动磁盘出现故障。 |
The boot disk experienced failures. |
| 0xC0380050 | 磁盘组的配置处于脱机状态。 |
The configuration of the pack is offline. |
| 0xC0380051 | 磁盘组的配置处于联机状态。 |
The configuration of the pack is online. |
| 0xC0380052 | 指定的磁盘组不是主磁盘组。 |
The specified pack is not the primary pack. |
| 0xC0380053 | 无法用日志的新内容更新所有磁盘。 |
All disks failed to be updated with the new content of the log. |
| 0xC0380054 | 丛中指定的磁盘数无效。 |
The specified number of disks in a plex is invalid. |
| 0xC0380055 | 丛成员中指定的磁盘数无效。 |
The specified number of disks in a plex member is invalid. |
| 0xC0380056 | 镜像卷不支持该操作。 |
The operation is not supported on mirrored volumes. |
| 0xC0380057 | 仅在简单丛和跨区丛上支持该操作。 |
The operation is only supported on simple and spanned plexes. |
| 0xC0380058 | 磁盘组没有有效的日志副本。 |
The pack has no valid log copies. |
| 0xC0380059 | 主磁盘组已存在。 |
A primary pack is already present. |
| 0xC038005A | 指定的磁盘数无效。 |
The specified number of disks is invalid. |
| 0xC038005B | 系统不支持镜像卷。 |
The system does not support mirrored volumes. |
| 0xC038005C | 系统不支持 RAID-5 卷。 |
The system does not support RAID-5 volumes. |
| 0xC0390002 | 枚举的条目已超过允许的阈值。 |
Entries enumerated have exceeded the allowed threshold. |
| 0xC03A0001 | 虚拟硬盘损坏。虚拟硬盘驱动器页脚丢失。 |
The virtual hard disk is corrupted. The virtual hard disk drive footer is missing. |
| 0xC03A0002 | 虚拟硬盘损坏。虚拟硬盘驱动器页脚校验和与磁盘上的校验和不匹配。 |
The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum. |
| 0xC03A0003 | 虚拟硬盘损坏。虚拟硬盘中的虚拟硬盘驱动器页脚损坏。 |
The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted. |
| 0xC03A0004 | 系统不识别此虚拟硬盘的文件格式。 |
The system does not recognize the file format of this virtual hard disk. |
| 0xC03A0005 | 该版本不支持此版本的文件格式。 |
The version does not support this version of the file format. |
| 0xC03A0006 | 虚拟硬盘损坏。稀疏标头校验和与磁盘上的校验和不匹配。 |
The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum. |
| 0xC03A0007 | 系统不支持此版本的虚拟硬盘。不支持此版本的稀疏标头。 |
The system does not support this version of the virtual hard disk.This version of the sparse header is not supported. |
| 0xC03A0008 | 虚拟硬盘损坏。虚拟硬盘中的稀疏标头损坏。 |
The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt. |
| 0xC03A0009 | 未能写入虚拟硬盘，因为系统未能在虚拟硬盘中分配新的块。 |
Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk. |
| 0xC03A000A | 虚拟硬盘损坏。虚拟硬盘中的块分配表损坏。 |
The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt. |
| 0xC03A000B | 系统不支持此版本的虚拟硬盘。块大小无效。 |
The system does not support this version of the virtual hard disk. The block size is invalid. |
| 0xC03A000C | 虚拟硬盘已损坏。 块位图与虚拟磁盘中出现的块数据不匹配。 |
The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk. |
| 0xC03A000D | 虚拟硬盘的链已断开。系统无法找到差异磁盘的父级虚拟硬盘。 |
The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk. |
| 0xC03A000E | 虚拟硬盘的链已损坏。父级虚拟硬盘的标识符和差异磁盘的标识符不匹配。 |
The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk. |
| 0xC03A000F | 虚拟硬盘链已损坏。父虚拟硬盘的时间戳与差异磁盘的时间戳不匹配。 |
The 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. |
| 0xC03A0010 | 读取虚拟硬盘的元数据失败。 |
Failed to read the metadata of the virtual hard disk. |
| 0xC03A0011 | 未能写入虚拟硬盘的元数据。 |
Failed to write to the metadata of the virtual hard disk. |
| 0xC03A0012 | 虚拟硬盘的大小无效。 |
The size of the virtual hard disk is not valid. |
| 0xC03A0013 | 此虚拟硬盘的文件大小无效。 |
The file size of this virtual hard disk is not valid. |
| 0xC03A0014 | 找不到指定文件的虚拟磁盘支持提供程序。 |
A virtual disk support provider for the specified file was not found. |
| 0xC03A0015 | 指定的磁盘不是虚拟磁盘。 |
The specified disk is not a virtual disk. |
| 0xC03A0016 | 虚拟硬盘链无法访问。尚未授予此进程访问差异磁盘的父虚拟硬盘的权限。 |
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. |
| 0xC03A0017 | 虚拟硬盘链已损坏。父虚拟硬盘和差异磁盘的虚拟大小不匹配。 |
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. |
| 0xC03A0018 | 虚拟硬盘链已损坏。表明差异磁盘位于其自己的父链中。 |
The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain. |
| 0xC03A0019 | 虚拟硬盘链无法访问。打开虚拟硬盘而进一步打开此链时出错。 |
The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain. |
| 0xC03A001A | 由于虚拟磁盘系统限制，无法完成请求的操作。虚拟硬盘文件必须是未压缩和未加密的文件，并且不能是稀疏文件。 |
The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse. |
| 0xC03A001B | 无法在此类型的虚拟磁盘上执行请求的操作。 |
The requested operation cannot be performed on a virtual disk of this type. |
| 0xC03A001C | 无法在处于当前状态的虚拟磁盘上执行请求的操作。 |
The requested operation cannot be performed on the virtual disk in its current state. |
| 0xC03A001D | 不支持虚拟磁盘所在的物理磁盘的扇区大小。 |
The sector size of the physical disk on which the virtual disk resides is not supported. |
| 0xC03A001E | 其他所有者已经拥有了该磁盘。 |
The disk is already owned by a different owner. |
| 0xC03A001F | 该磁盘必须为脱机或只读状态。 |
The disk must be offline or read-only. |
| 0xC03A0020 | 此虚拟磁盘未初始化更改跟踪。 |
Change Tracking is not initialized for this virtual disk. |
| 0xC03A0021 | 更改跟踪文件的大小已超出大小上限。 |
Size of change tracking file exceeded the maximum size limit. |
| 0xC03A0022 | VHD 文件由于压缩、扩展或脱机更新而发生更改。 |
VHD file is changed due to compaction, expansion, or offline updates. |
| 0xC03A0023 | 虚拟磁盘的更改跟踪未处于有效状态，因而无法执行此请求。更改跟踪可能已终止，或者已处于请求的状态。 |
Change 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. |
| 0xC03A0024 | 虚拟磁盘的更改跟踪文件未处于有效状态。 |
Change Tracking file for the virtual disk is not in a valid state. |
| 0xC03A0025 | 无法完成请求的调整大小操作，原因是它可能截断了位于虚拟磁盘上的用户数据。 |
The requested resize operation could not be completed because it might truncate user data residing on the virtual disk. |
| 0xC03A0026 | 无法完成请求的操作，原因是无法确定虚拟磁盘的安全大小下限。这可能是因为分区表丢失或损坏。 |
The 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. |
| 0xC03A0027 | 无法完成请求的操作，原因是无法安全地进一步减小虚拟磁盘的大小。 |
The requested operation could not be completed because the virtual disk's size cannot be safely reduced further. |
| 0xC03A0028 | 虚拟磁盘文件中的空间不足，无法存储所提供的元数据项目。 |
There is not enough space in the virtual disk file for the provided metadata item. |
| 0xC03A0029 | 指定的更改跟踪标识符无效。 |
The specified change tracking identifier is not valid. |
| 0xC03A002A | 为指定的虚拟硬盘禁用了更改跟踪，因此未提供任何更改跟踪信息。 |
Change tracking is disabled for the specified virtual hard disk, so no change tracking information is available. |
| 0xC03A0030 | 没有可用的更改跟踪数据与指定的更改跟踪标识符相关联。 |
There is no change tracking data available associated with the specified change tracking identifier. |
| 0xC03B0001 | 该端口已分配 |
The port is already allocated |
| 0xC03B0002 | 给定网络不支持端口映射 |
Port mapping is not supported on the given network |
| 0xC05C0000 | 此特有错误代码与感知数据一同存储在服务器端。 |
The proper error code with sense data was stored on server side. |
| 0xC05CFF00 | 请求的错误数据在服务器上不可用。 |
The requested error data is not available on the server. |
| 0xC05CFF01 | Unit Attention 数据可供发起程序查询。 |
Unit Attention data is available for the initiator to query. |
| 0xC05CFF02 | 此设备的数据容量已更改，同时生成一个 Unit Attention 条件。 |
The data capacity of the device has changed, resulting in a Unit Attention condition. |
| 0xC05CFF03 | 此前的操作已导致这个发起程序的预留被占用，同时生成一个 Unit Attention 条件。 |
A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF04 | 此前的操作已导致这个发起程序的预留被释放，同时生成一个 Unit Attention 条件。 |
A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition. |
| 0xC05CFF05 | 此前的操作已导致这个发起程序的注册被占用，同时生成一个 Unit Attention 条件。 |
A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF06 | 此设备的数据存储格式已更改，同时生成一个 Unit Attention 条件。 |
The data storage format of the device has changed, resulting in a Unit Attention condition. |
| 0xC05CFF07 | 由于存在预留冲突，因此不允许当前的发起程序执行 SCSI 命令。 |
The current initiator is not allowed to perform the SCSI command because of a reservation conflict. |
| 0xC05CFF08 | 只有在固定或动态 VHDX 格式虚拟硬盘中才支持由多个虚拟机共享一个虚拟硬盘。 |
Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks. |
| 0xC05CFF09 | 服务器版本与请求的版本不匹配。 |
The server version does not match the requested version. |
| 0xC05CFF0A | 无法在虚拟磁盘上执行请求的操作，因为当前正在共享模式下使用该磁盘。 |
The requested operation cannot be performed on the virtual disk as it is currently used in shared mode. |
| 0xC05CFF0B | 由于缺少发起程序 ID，打开的共享 VHDX 无效。请检查是否存在相关的“连续可用性”故障。 |
Invalid Shared VHDX open due to lack of initiator ID. Check for related Continuous Availability failures. |
| 0xC05CFF0C | 由于缺少后备存储文件，请求的操作失败。 |
The requested operation failed due to a missing backing storage file. |
| 0xC05D0000 | 无法协商预身份验证完整性哈希函数。 |
Failed to negotiate a preauthentication integrity hash function. |
| 0xC05D0001 | 当前群集功能级别不支持此 SMB 方言。 |
The current cluster functional level does not support this SMB dialect. |
| 0xC0E80000 | 安全内核无法识别此命令 |
The command was not recognized by the security core |
| 0xC0EA0001 | 找不到适用的应用许可证。 |
No applicable app licenses found. |
| 0xC0EA0002 | 找不到 CLiP 许可证。 |
CLiP license not found. |
| 0xC0EA0003 | 找不到 CLiP 设备许可证。 |
CLiP device license not found. |
| 0xC0EA0004 | CLiP 许可证的签名无效。 |
CLiP license has an invalid signature. |
| 0xC0EA0005 | CLiP 密钥持有者许可证无效或缺失。 |
CLiP keyholder license is invalid or missing. |
| 0xC0EA0006 | CLiP 许可证已过期。 |
CLiP license has expired. |
| 0xC0EA0007 | CLiP 许可证由未知源签名。 |
CLiP license is signed by an unknown source. |
| 0xC0EA0008 | CLiP 许可证未签名。 |
CLiP license is not signed. |
| 0xC0EA0009 | CLiP 许可证硬件 ID 超出允许范围。 |
CLiP license hardware ID is out of tolerance. |
| 0xC0EA000A | CLiP 许可证设备 ID 与绑定设备许可证中的设备 ID 不匹配。 |
CLiP license device ID does not match the device ID in the bound device license. |