| 0x0 | STATUS_SUCCESS |
STATUS_SUCCESS |
| 0x1 | STATUS_WAIT_1 |
STATUS_WAIT_1 |
| 0x2 | STATUS_WAIT_2 |
STATUS_WAIT_2 |
| 0x3 | STATUS_WAIT_3 |
STATUS_WAIT_3 |
| 0x3F | STATUS_WAIT_63 |
STATUS_WAIT_63 |
| 0x80 | STATUS_ABANDONED_WAIT_0 |
STATUS_ABANDONED_WAIT_0 |
| 0xBF | STATUS_ABANDONED_WAIT_63 |
STATUS_ABANDONED_WAIT_63 |
| 0xC0 | STATUS_USER_APC |
STATUS_USER_APC |
| 0xFF | 请求的操作已由前面的操作完成。 |
The requested action was completed by an earlier operation. |
| 0x100 | STATUS_KERNEL_APC |
STATUS_KERNEL_APC |
| 0x101 | STATUS_ALERTED |
STATUS_ALERTED |
| 0x102 | STATUS_TIMEOUT |
STATUS_TIMEOUT |
| 0x103 | 尚未完成请求的操作。 |
The operation that was requested is pending completion. |
| 0x104 | 因为文件名产生符号链接，所以需由对象管理器重新运行分析操作。 |
A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. |
| 0x105 | 枚举 API 的返回值表示后续的调用尚有更多的信息。 |
Returned by enumeration APIs to indicate more information is available to successive calls. |
| 0x106 | 指示并非将所有的参考特权或组指派给调用方。例如，允许禁用所有的特权而不必明确知道指派的是哪个特权。 |
Indicates not all privileges or groups referenced are assigned to the caller.This allows, for example, all privileges to be disabled without having to know exactly which privileges are assigned. |
| 0x107 | 尚未解释某些信息。 |
Some of the information to be translated has not been translated. |
| 0x108 | 在 oplock 中断进行中完成一项打开/创建操作。 |
An open/create operation completed while an oplock break is underway. |
| 0x109 | 文件系统已装入新卷。 |
A new volume has been mounted by a file system. |
| 0x10A | 此成功等级状态表明注册表子目录树的事务状态已存在，但之前事务确认已终止。现已完成确认。 |
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. |
| 0x10B | 表示由于关闭句柄而产生的提示更改请求已完成。 |
This indicates that a notify change request has been completed due to closing the handle which made the notify change request. |
| 0x10C | 表示将完成一项提示更改请求且信息不传回调用方的缓冲区内。调用方现在需要枚举文件来查找更改。 |
This indicates that a notify change request is being completed and that the information is not being returned in the caller's buffer.The caller now needs to enumerate the files to find the changes. |
| 0x10D | {没有配额}本帐户没有设置系统配额的限制。 |
{No Quotas}No system quota limits are specifically set for this account. |
| 0x10E | {主要传输连接故障}试图连接到主要传输上的远程服务器 %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. |
| 0x110 | 页面错误为传输错误。 |
Page fault was a transition fault. |
| 0x111 | 页面错误为请求 0 错误。 |
Page fault was a demand zero fault. |
| 0x114 | 可以从次要存储设备上读取以弥补页面错误。 |
Page fault was satisfied by reading from a secondary storage device. |
| 0x115 | 操作时锁定高速缓存页。 |
Cached page was locked during operation. |
| 0x116 | 页面文件中有故障转储。 |
Crash dump exists in paging file. |
| 0x117 | 指定的缓冲区含有的都是零。 |
Specified buffer contains all zeros. |
| 0x119 | 设备已经完成“查询停止”，并且它的资源需求已更改。 |
The device has succeeded a query-stop and its resource requirements have changed. |
| 0x120 | 转换器已经将这些资源转换到全局空间，不应该运行更多的转换。 |
The translator has translated these resources into the global space and no further translations should be performed. |
| 0x121 | 目录服务在本地评价了组成员身份，因为它无法与全局编录服务器联系。 |
The directory service evaluated group memberships locally, as it was unable to contact a global catalog server. |
| 0x122 | 终止的进程没有线程来终止。 |
A process being terminated has no threads to terminate. |
| 0x123 | 指定的进程不是作业的一部分。 |
The specified process is not part of a job. |
| 0x124 | 指定的进程是作业的一部分。 |
The specified process is part of a job. |
| 0x125 | {卷影复制服务}系统准备好进入休眠。 |
{Volume Shadow Copy Service}The system is now ready for hibernation. |
| 0x126 | 文件系统或文件系统筛选器驱动程序已经成功完成 FsFilter 操作。 |
A file system or file system filter driver has successfully completed an FsFilter operation. |
| 0x127 | 指定的中断矢量已经连接。 |
The specified interrupt vector was already connected. |
| 0x128 | 指定的中断矢量仍处于连接状态。 |
The specified interrupt vector is still connected. |
| 0x129 | 当前进程是克隆进程。 |
The current process is a cloned process. |
| 0x12A | 该文件被锁定，且该文件的所有用户都只能执行读取操作。 |
The file was locked and all users of the file can only read. |
| 0x12B | 该文件被锁定，且该文件至少有一个用户可以执行写操作。 |
The file was locked and at least one user of the file can write. |
| 0x12C | 文件映像哈希有效。 |
The file image hash is valid. |
| 0x12D | 该文件目录哈希有效。 |
The file catalog hash is valid. |
| 0x12E | 文件哈希有效并使用了强代码完整性。 |
The file hash is valid and uses strong code integrity. |
| 0x12F | 至少一部分 IO 范围与幻像文件范围相交。 |
At least a portion of IO range intersects with a ghosted file range. |
| 0x202 | 指定的 ResourceManager 未对该事务下的资源进行更改或更新。 |
The specified ResourceManager made no changes or updates to the resource under this transaction. |
| 0x210 | 指定的信号缓冲区在成功插入数据包前为空。 |
The specified ring buffer was empty before the packet was successfully inserted. |
| 0x211 | 指定的信号缓冲区在成功删除数据包前为空。 |
The specified ring buffer was full before the packet was successfully removed. |
| 0x212 | 指定的信号缓冲区降到其未完成事务的配额之下。 |
The specified ring buffer has dropped below its quota of outstanding transactions. |
| 0x213 | 指定的信号缓冲区因删除了当前数据包现在已为空。 |
The specified ring buffer has, with the removal of the current packet, now become empty. |
| 0x214 | 无论指定的信号缓冲区之前为空或者为满，都表示调用程序应该向对方终点发送信号。 |
The specified ring buffer was either previously empty or previously full which implies that the caller should signal the opposite endpoint. |
| 0x215 | 与此句柄相关联的操作锁定现在与其他句柄相关联。 |
The oplock that was associated with this handle is now associated with a different handle. |
| 0x216 | 此操作锁定所关联的句柄已关闭。操作锁定现已中断。 |
The handle with which this oplock was associated has been closed. The oplock is now broken. |
| 0x367 | 操作被阻止，正在等待操作锁定完成。 |
An operation is blocked waiting for an oplock. |
| 0x368 | 应该由对象管理器在全局根目录执行重分析，以便对容器名称空间进行转义。 |
A reparse should be performed by the Object Manager from the global root to escape the container name space. |
| 0x00010001 | 调试程序处理了异常现象 |
Debugger handled exception |
| 0x00010002 | 调试程序继续运行 |
Debugger continued |
| 0x001C0001 | 由筛选器完成 IO。 |
The IO was completed by a filter. |
| 0x00293000 | 远程 TPM 上下文交换未完成。上下文应传输到目标并且应该连续。 |
The remote TPM context exchange is not complete. The context should be transported to the target and continued. |
| 0x00293001 | 远程 TPM 操作已完成。 |
The remote TPM operation is complete. |
| 0x00350059 | 设备有已放弃的挂起页面请求。 |
The device had pending page requests which were discarded. |
| 0x00E70000 | 修复成功。 |
The repair was successful. |
| 0x00E70001 | 操作已暂停。 |
The operation has been paused. |
| 0x00E70002 | 操作已完成。 |
The operation is complete. |
| 0x00E70003 | 应将此操作重定向到另一个节点。 |
The operation should be redirected to another node. |
| 0x40000000 | {对象已存在}试图创建一名称已存在的对象。 |
{Object Exists}An attempt was made to create an object and the object name already existed. |
| 0x40000001 | {暂停线程}暂停线程时将暂时终止线程。当继续线程时即取消终止。 |
{Thread Suspended}A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded. |
| 0x40000002 | {工作组范围错误}试图设置超过工作组所允许的最小或最大值范围。 |
{Working Set Range Error}An attempt was made to set the working set minimum or maximum to values which are outside of the allowable range. |
| 0x40000003 | {映像重定位}无法在映像文件中指定的地址映射该映像文件。必须对映像文件进行本地修正。 |
{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. |
| 0x40000004 | 这个信息等级状态表示某个特定注册表的子目录树事务处理状态不存在，且必须创建。 |
This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created. |
| 0x40000005 | {段加载}一个虚拟 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. |
| 0x40000006 | {本地会话项}本地 RPC 连接请求用户会话项。本会话项返回一常数值且非本连接的唯一值。 |
{Local Session Key}A user session key was requested for a local RPC connection. The session key returned is a constant value and not unique to this connection. |
| 0x40000007 | {无效的当前目录}过程无法切换到启动当前目录 %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. |
| 0x40000008 | {完成串行 IOCTL}通过另一个写入串行端口以完成串行 I/O 操作。(IOCTL_SERIAL_XOFF_COUNTER 到达 0。) |
{Serial IOCTL Complete}A serial I/O operation was completed by another write to a serial port.(The IOCTL_SERIAL_XOFF_COUNTER reached zero.) |
| 0x40000009 | {注册表故障恢复}必须使用日志或另一副本以恢复包含系统注册表数据的文件。恢复成功。 |
{Registry Recovery}One of the files containing the system's Registry data had to be recovered by use of a log or alternate copy. The recovery was successful. |
| 0x4000000A | {冗余读取}若要完成读取请求，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. |
| 0x4000000B | {冗余写入}若要完成写入请求，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. |
| 0x4000000C | {串行 IOCTL 传输超时}到达传输超时过期而结束串行 I/O 操作。(IOCTL_SERIAL_XOFF_COUNTER 未到达 0。) |
{Serial IOCTL Timeout}A serial I/O operation completed because the time-out period expired. (The IOCTL_SERIAL_XOFF_COUNTER had not reached zero.) |
| 0x4000000D | {密码太复杂}Windows 密码太复杂，无法将其转换为 LAN Manager 密码。返回的 LAN Manager 密码是空字符串。 |
{Password Too Complex}The Windows password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string. |
| 0x4000000E | {机器类型不匹配}映像文件 %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. |
| 0x4000000F | {已接收部分数据}网络已向客户端传输部分数据。稍后再传送其余数据。 |
{Partial Data Received}The network transport returned partial data to its client. The remaining data will be sent later. |
| 0x40000010 | {已接收发送的数据}网络传输传回数据至客户端并在远程系统上标记已发送。 |
{Expedited Data Received}The network transport returned data to its client that was marked as expedited by the remote system. |
| 0x40000011 | {已接收发送的部分数据}网络传输已传回部分数据至客户端且标记为远程系统发送的数据。稍后再传送其余数据。 |
{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. |
| 0x40000012 | {TDI 事件完成}TDI 标示已成功完成。 |
{TDI Event Done}The TDI indication has completed successfully. |
| 0x40000013 | {TDI 事件尚未完成}TDI 标示进入等待状态。 |
{TDI Event Pending}The TDI indication has entered the pending state. |
| 0x40000014 | 正在检查 %wZ 上的文件系统 |
Checking file system on %wZ |
| 0x40000015 | {致命的应用程序退出}%hs |
{Fatal Application Exit}%hs |
| 0x40000016 | 一个预定义的句柄引用指定的注册表项。 |
The specified registry key is referenced by a predefined handle. |
| 0x40000017 | {解除页面锁定}页面锁定的保护状态更改为“不允许访问”且从内存及过程中解除页面锁定。 |
{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. |
| 0x40000018 | %hs |
%hs |
| 0x40000019 | {页面锁定}要锁定的页面已锁定。 |
{Page Locked}One of the pages to lock was already locked. |
| 0x4000001A | 弹出应用程序: %1: %2 |
Application popup: %1 : %2 |
| 0x4000001B | STATUS_ALREADY_WIN32 |
STATUS_ALREADY_WIN32 |
| 0x4000001C | Win32 x86 仿真子系统使用的异常状态代码。 |
Exception status code used by Win32 x86 emulation subsystem. |
| 0x40000023 | {计算机类型不匹配}映像文件 %hs 无效，但它对另一种计算机类型有效。 |
{Machine Type Mismatch}The image file %hs is valid, but is for a machine type other than the current machine. |
| 0x40000024 | 执行了一次转交，没有可以运行的线程。 |
A yield execution was performed and no thread was available to run. |
| 0x40000025 | 定时器 API 可还原标志被忽略。 |
The resumable flag to a timer API was ignored. |
| 0x40000026 | 仲裁程序已经将这些资源的仲裁顺延到它的父系上 |
The arbiter has deferred arbitration of these resources to its parent |
| 0x40000027 | 设备“%hs”在其插槽检测到一个 CardBus 卡，但是该系统上的固件的配置不允许在 CardBus 模式下运行 CardBus 控制器。该操作系统在这个控制器上只接受 16 位(R2)电脑机卡。 |
The device \"%hs\" has detected a CardBus card in its slot, but the firmware on this system is not configured to allow the CardBus controller to be run in CardBus mode.The operating system will currently accept only 16-bit (R2) pc-cards on this controller. |
| 0x40000029 | 在此多处理器系统中的 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. |
| 0x4000002A | 系统进入休眠。 |
The system was put into hibernation. |
| 0x4000002B | 系统从休眠中恢复。 |
The system was resumed from hibernation. |
| 0x4000002C | Windows 检测到系统固件 (BIOS) 已经更新 [以前的固件日期 = %2, 当前固件日期 %3]。 |
Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]. |
| 0x4000002D | 设备驱动程序正在泄露导致系统降级的锁定 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. |
| 0x4000002E | 已经从另一侧的队列中检索取消的 ALPC 消息。 |
The ALPC message being canceled has already been retrieved from the queue on the other side. |
| 0x4000002F | 系统电源状态正从 %2 转换为 %3。 |
The system power state is transitioning from %2 to %3. |
| 0x40000030 | 接收操作成功。请检查 ALPC 完成列表以获取收到的消息。 |
The receive operation was successful. Check the ALPC completion list for the received message. |
| 0x40000031 | 系统电源状态正从 %2 转换为 %3，但可能进入 %4。 |
The system power state is transitioning from %2 to %3 but could enter %4. |
| 0x40000032 | 对 %1 的访问由策略规则 %2 监视。 |
Access to %1 is monitored by policy rule %2. |
| 0x40000033 | 有效的休眠文件已经变得无效，应该放弃该文件。 |
A valid hibernation file has been invalidated and should be abandoned. |
| 0x40000034 | 已禁用调用应用程序的业务规则脚本。 |
Business rule scripts are disabled for the calling application. |
| 0x40000035 | 已成功读取请求数据的指定副本。 |
The specified copy of the requested data was successfully read. |
| 0x40000036 | {映像重定位}虽然映射映像文件的地址不同于映像文件中指定的地址，但系统仍会自动对映像进行修正。 |
{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. |
| 0x40000294 | 系统已经恢复 |
The system has awoken |
| 0x40000370 | 目录服务正在关闭。 |
The Directory Service is shutting down. |
| 0x40000807 | 卷处于联机时无法进行修复。请安排使卷脱机，以便能够对其进行修复。 |
The volume repair could not be performed while it is online.Please schedule to take the volume offline so that it can be repaired. |
| 0x4000A144 | 在运行级别切换的服务启动阶段，一个或多个服务无法启动。 |
One or more services failed to start during the service startup phase of a run level switch. |
| 0x40010001 | 调试程序会以后答复。 |
Debugger will reply later. |
| 0x40010002 | 调试程序无法提供句柄。 |
Debugger cannot provide handle. |
| 0x40010003 | 调试程序终止了线程。 |
Debugger terminated thread. |
| 0x40010004 | 调试程序终止了过程。 |
Debugger terminated process. |
| 0x40010005 | 调试程序得到了控件 C。 |
Debugger got control C. |
| 0x40010006 | 调试程序打印了控件 C 上的异常现象。 |
Debugger printed exception on control C. |
| 0x40010007 | 调试程序收到了 RIP 异常现象。 |
Debugger received RIP exception. |
| 0x40010008 | 调试程序收到了控件中断。 |
Debugger received control break. |
| 0x40010009 | 调试程序命令通信异常。 |
Debugger command communication exception. |
| 0x4001000A | 调试程序打印了控件 C 上的异常。 |
Debugger printed exception on control C. |
| 0x40020056 | 已经分配只在这台计算机上有效的 UUID。 |
A UUID that is valid only on this computer has been allocated. |
| 0x400200AF | 一些待发数据仍停留在请求缓冲区内。 |
Some data remains to be sent in the request buffer. |
| 0x400A0004 | 客户端驱动器映射服务已连接在终端连接上。 |
The Client Drive Mapping Service Has Connected on Terminal Connection. |
| 0x400A0005 | 已在终端连接上中断客户端驱动器映射服务。 |
The Client Drive Mapping Service Has Disconnected on Terminal Connection. |
| 0x4015000D | 内核模式组件正在释放激活上下文上的参照。 |
A kernel mode component is releasing a reference on an activation context. |
| 0x40190001 | 提交事务的尝试已完成，但由于启发，事务树的某些部分可能未成功提交。因此可能没有提交事务中已修改的某些数据，从而导致事务不一致。如果可能的话，请检查关联数据的一致性。 |
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. |
| 0x40190034 | 事务性资源管理器已经一致。无需恢复。 |
The transactional resource manager is already consistent. Recovery is not needed. |
| 0x40190035 | 事务性资源管理器已经启动。 |
The transactional resource manager has already been started. |
| 0x401A000C | 日志服务遇到错误，原因: 日志流没有重新启动区。 |
Log service encountered a log stream with no restart area. |
| 0x401B00EC | {显示驱动程序从故障中恢复}检测到 %hs 显示驱动程序并且从故障中恢复。部分图形操作可能已经失败。下一次启动计算机时显示的对话框让你能够将有关此故障的数据上载到 Microsoft。 |
{Display Driver Recovered From Failure}The %hs display driver has detected and recovered from a failure. Some graphical operations may have failed. The next time you reboot the machine a dialog will be displayed giving you a chance to upload data about this failure to Microsoft. |
| 0x401E000A | 指定的缓冲区不够大，无法包含整个请求的数据集。部分数据已占满缓冲区大小。调用方需要根据部分写入缓冲区的内容指定的大小来提供缓冲区(特定于接口)。 |
Specified buffer is not big enough to contain entire requested dataset. Partial data populated upto the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific). |
| 0x401E0201 | 跳过 DMA 缓冲区引用的分配准备。 |
Skip preparation of allocations referenced by the DMA buffer. |
| 0x401E0307 | 没有任何模式固定在指定 VidPN 源/目标上。 |
No mode is pinned on the specified VidPN source/target. |
| 0x401E031E | 指定的模式集没有为它的一种模式指定首选项。 |
Specified mode set does not specify preference for one of its modes. |
| 0x401E034B | 指定的数据集(例如，模式集、频率范围集、描述符集和拓扑等)为空。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty. |
| 0x401E034C | 指定的数据集(例如，模式集、频率范围集、描述符集和拓扑等)不包含任何其他元素。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements. |
| 0x401E0351 | 指定的内容转换没有固定在指定的 VidPN 当前路径上。 |
Specified content transformation is not pinned on the specified VidPN present path. |
| 0x401E042F | 无法可靠地检测到是否存在子设备。 |
Child device presence was not reliably detected. |
| 0x401E0437 | 启动主链接适配器已被暂时延迟。 |
Starting the leadlink adapter has been deferred temporarily. |
| 0x401E0439 | 在同一轮询级别上为子级轮询显示适配器过于频繁。 |
The display adapter is being polled for children too frequently at the same polling level. |
| 0x401E043A | 启动适配器的操作已经被暂时延迟。 |
Starting the adapter has been deferred temporarily. |
| 0x401E043C | 我们可以依赖于驱动程序返回的子设备状态。 |
We can depend on the child device presence returned by the driver. |
| 0x40230001 | 该请求稍后将通过 NDIS 状态指示来完成。 |
The request will be completed later by NDIS status indication. |
| 0x80000001 | {异常}防护页面异常已访问标记数据结构(如堆栈或数组)结尾的内存页面。 |
{EXCEPTION}Guard Page ExceptionA page of memory that marks the end of a data structure, such as a stack or an array, has been accessed. |
| 0x80000002 | {异常}定位错误加载或保存指令所检测的数据类型定位错误。 |
{EXCEPTION}Alignment FaultA datatype misalignment was detected in a load or store instruction. |
| 0x80000003 | {异常}中断点已到达中断点。 |
{EXCEPTION}BreakpointA breakpoint has been reached. |
| 0x80000004 | {异常}单步已完成单步或跟踪操作。 |
{EXCEPTION}Single StepA single step or trace operation has just been completed. |
| 0x80000005 | {缓冲区溢出}数据过大以致于无法装入所指定的缓冲区。 |
{Buffer Overflow}The data was too large to fit into the specified buffer. |
| 0x80000006 | {无其他文件}已无其他符合该文件格式的文件。 |
{No More Files}No more files were found which match the file specification. |
| 0x80000007 | {内核调试程序}由中断触发的系统调试程序。 |
{Kernel Debugger Awakened}the system debugger was awakened by an interrupt. |
| 0x8000000A | {已关闭句柄}依操作请求而自动关闭的对象句柄。 |
{Handles Closed}Handles to objects have been automatically closed as a result of the requested operation. |
| 0x8000000B | {非继承的 ACL}访问控制列表(ACL)中不包含可继承的组件。 |
{Non-Inheritable ACL}An access control list (ACL) contains no components that can be inherited. |
| 0x8000000C | {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. |
| 0x8000000D | {部分复制}因保护冲突无法复制所有请求的字节。 |
{Partial Copy}Due to protection conflicts not all the requested bytes could be copied. |
| 0x8000000E | {缺纸}打印机缺纸。 |
{Out of Paper}The printer is out of paper. |
| 0x8000000F | {没有打开设备电源}没有打开打印机电源。 |
{Device Power Is Off}The printer power has been turned off. |
| 0x80000010 | {设备脱机}打印机脱机。 |
{Device Offline}The printer has been taken offline. |
| 0x80000011 | {设备在使用中}设备在使用中。 |
{Device Busy}The device is currently busy. |
| 0x80000012 | {无其他 EA}无法取得该文件的其他扩展属性(EA)。 |
{No More EAs}No more extended attributes (EAs) were found for the file. |
| 0x80000013 | {无效的 EA}指定的扩展属性(EA)名称中至少包含一个无效的字符。 |
{Illegal EA}The specified extended attribute (EA) name contains at least one illegal character. |
| 0x80000014 | {不一致的 EA 列表}扩展属性(EA)列表不一致。 |
{Inconsistent EA List}The extended attribute (EA) list is inconsistent. |
| 0x80000015 | {无效的 EA 标志}设置无效的扩展属性(EA)标志。 |
{Invalid EA Flag}An invalid extended attribute (EA) flag was set. |
| 0x80000016 | {验证磁盘}已更换保存媒体，验证操作正在进行中，因而该设备无法执行除验证操作以外的读取或写入操作。 |
{Verifying Disk}The media has changed and a verify operation is in progress so no reads or writes may be performed to the device, except those used in the verify operation. |
| 0x80000017 | {过多的信息}指定的访问控制列表(ACL)中包含过多的信息。 |
{Too Much Information}The specified access control list (ACL) contained more information than was expected. |
| 0x80000018 | 这个警告等级状态指出事务状态已经存在于注册表子目录树，但之前事务确认操作已中止。确认操作并未完成，也未还原到上一步的操作。(它可能还处在确认状态)。 |
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). |
| 0x8000001A | {无其他项目}列举操作中已无其他项目。 |
{No More Entries}No more entries are available from an enumeration operation. |
| 0x8000001B | {发现文件标记}检测到一文件标记。 |
{Filemark Found}A filemark was detected. |
| 0x8000001C | {媒体已更改}媒体可能已更改。 |
{Media Changed}The media may have changed. |
| 0x8000001D | {重置 I/O 总线}检测到重置 I/O 总线。 |
{I/O Bus Reset}An I/O bus reset was detected. |
| 0x8000001E | {媒体退出}媒体已运行完毕。 |
{End of Media}The end of the media was encountered. |
| 0x8000001F | 检测到磁带或分区的开头。 |
Beginning of tape or partition has been detected. |
| 0x80000021 | 已达磁带的设置标记。 |
A tape access reached a setmark. |
| 0x80000022 | 已达磁带访问时的数据写入尾端。 |
During a tape access, the end of the data written is reached. |
| 0x80000023 | 重定向程序正使用中，不能卸装。 |
The redirector is in use and cannot be unloaded. |
| 0x80000024 | 服务器在使用中且无法卸载。 |
The server is in use and cannot be unloaded. |
| 0x80000025 | 已断开指定的连接。 |
The specified connection has already been disconnected. |
| 0x80000026 | 一个长跳转已经运行。 |
A long jump has been executed. |
| 0x80000027 | 清洗磁带在磁带库中。 |
A cleaner cartridge is present in the tape library. |
| 0x80000028 | 即插即用查询未成功。 |
The Plug and Play query operation was not successful. |
| 0x80000029 | 帧合并已经执行。 |
A frame consolidation has been executed. |
| 0x8000002A | {注册表配置单元已恢复}注册表配置单元(文件):%hs曾经损坏而且已经恢复。可能丢失一些数据。 |
{Registry Hive Recovered}Registry hive (file):%hswas corrupted and it has been recovered. Some data might have been lost. |
| 0x8000002B | 应用程序正在试图从模块 %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? |
| 0x8000002C | 应用程序正在从模块 %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? |
| 0x8000002D | 到达符号链接后停止创建操作。 |
The create operation stopped after reaching a symbolic link. |
| 0x8000002E | 无法授予所请求级别的操作锁定。较低级别的操作锁定可能可用。 |
An oplock of the requested level cannot be granted. An oplock of a lower level may be available. |
| 0x8000002F | {无 ACE 条件}指定的访问控制项(ACE)不包含某个条件。 |
{No ACE Condition}The specified access control entry (ACE) does not contain a condition. |
| 0x80000030 | {正在确定的支持}设备的命令支持检测正在进行。 |
{Support Being Determined}Device's command support detection is in progress. |
| 0x80000031 | 该设备需要重启电源。 |
The device needs to be power cycled. |
| 0x80000032 | 所请求的操作没有响应。已执行错误样式清除。 |
The action requested resulted in no work being done. Error-style clean-up has been performed. |
| 0x80000288 | 设备已经指出清洗操作是必需的。 |
The device has indicated that cleaning is necessary. |
| 0x80000289 | 设备已经指出其门处于打开状态。需要进一步操作，确保门已关闭并且安全。 |
The device has indicated that its door is open. Further operations require it closed and secured. |
| 0x80000803 | Windows 发现文件“%hs”有损坏。现在此文件已经修复。请检查文件中的数据是否因损坏而丢失。 |
Windows discovered a corruption in the file \"%hs\".This file has now been repaired.Please check if any data in the file was lost because of the corruption. |
| 0x8000A127 | 请求取消屏蔽的中断未被屏蔽。 |
The interrupt requested to be unmasked is not masked. |
| 0x8000CF00 | 云文件属性 Blob 可能已损坏。磁盘上的校验和与计算得出的校验和不匹配。 |
The Cloud File property blob is possibly corrupt. The on-disk checksum does not match the computed checksum. |
| 0x8000CF04 | 由于云文件属性 Blob 太大，无法完成该操作。 |
The operation could not be completed because the Cloud File property blob is too large. |
| 0x8000CF05 | 由于超出了云文件属性 Blob 的最大数目，无法完成该操作。 |
The operation could not be completed because the maximum number of Cloud File property blobs would be exceeded. |
| 0x80010001 | 调试程序没有处理异常现象。 |
Debugger did not handle the exception. |
| 0x80130001 | 群集节点已经开始。 |
The cluster node is already up. |
| 0x80130002 | 群集节点已经坏了。 |
The cluster node is already down. |
| 0x80130003 | 群集网络已经联机。 |
The cluster network is already online. |
| 0x80130004 | 群集网络已经脱机。 |
The cluster network is already offline. |
| 0x80130005 | 群集节点已经是该群集的成员。 |
The cluster node is already a member of the cluster. |
| 0x80190009 | 无法将日志设置为请求的大小。 |
The log could not be set to the requested size. |
| 0x80190029 | 文件中没有事务元数据。 |
There is no transaction metadata on the file. |
| 0x80190031 | 无法恢复文件，因为文件上仍然有打开的句柄。 |
The file can't be recovered because there is a handle still open on it. |
| 0x80190041 | 事务元数据已经存在于该文件中，无法取代。 |
Transaction metadata is already present on this file and cannot be superseded. |
| 0x80190042 | 无法输入事务处理范围，因为尚未启动范围处理程序。 |
A transaction scope could not be entered because the scope handler has not been initialized. |
| 0x801B00EB | {显示器驱动程序停止响应，并且已经恢复}%hs 显示器驱动程序已停止正常工作。恢复已经执行。 |
{Display Driver Stopped Responding and recovered}The %hs display driver has stopped working normally. The recovery had been performed. |
| 0x801C0001 | {缓冲区过小}缓冲区过小以致于无法包含项目。无法在缓冲区写入任何的信息。 |
{Buffer too small}The buffer is too small to contain the entry. No information has been written to the buffer. |
| 0x80210001 | 卷元数据读取或写入不完整。 |
Volume Metadata read or write is incomplete. |
| 0x80210002 | 因为卷处于临时状态，BitLocker 加密密钥被忽略。 |
BitLocker encryption keys were ignored because the volume was in a transient state. |
| 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. |
| 0x803F0001 | GDI 句柄可能已被应用程序泄漏。 |
GDI handles were potentially leaked by the application. |
| 0x80430006 | 此计算机上未启用安全启动。 |
Secure Boot is not enabled on this machine. |
| 0xC0000001 | {操作失败}请求的操作不成功。 |
{Operation Failed}The requested operation was unsuccessful. |
| 0xC0000002 | {未运行}未运行请求的操作。 |
{Not Implemented}The requested operation is not implemented. |
| 0xC0000003 | {无效的参数}指定的信息类别为无效的指定对象信息类别。 |
{Invalid Parameter}The specified information class is not a valid information class for the specified object. |
| 0xC0000004 | 指定的信息记录长度与请求的信息类别长度不符合。 |
The specified information record length does not match the length required for the specified information class. |
| 0xC0000005 | 0x%p 指令引用了 0x%p 内存。该内存不能为 %s。 |
The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. |
| 0xC0000006 | 0x%p 指令引用的 0x%p 内存。因 0x%x 的错误状态而无法将请求的数据放入内存。 |
The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. |
| 0xC0000007 | 过程的页面文件配额已用尽。 |
The pagefile quota for the process has been exhausted. |
| 0xC0000008 | 指定无效的句柄。 |
An invalid HANDLE was specified. |
| 0xC0000009 | 调用 NtCreateThread 时指定无效的起始堆栈。 |
An invalid initial stack was specified in a call to NtCreateThread. |
| 0xC000000A | 调用 NtCreateThread 时指定无效的起始地址。 |
An invalid initial start address was specified in a call to NtCreateThread. |
| 0xC000000B | 指定无效的客户端 ID。 |
An invalid Client ID was specified. |
| 0xC000000C | 试图取消或设置与 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. |
| 0xC000000D | 发送无效的参数给服务或功能。 |
An invalid parameter was passed to a service or function. |
| 0xC000000E | 指定不存在的设备。 |
A device which does not exist was specified. |
| 0xC000000F | {无法找到文件}文件 %hs 不存在。 |
{File Not Found}The file %hs does not exist. |
| 0xC0000010 | 指定的请求为目标设备的无效操作。 |
The specified request is not a valid operation for the target device. |
| 0xC0000011 | 已到达文件结尾标记。文件中标记之后没有有效的数据。 |
The end-of-file marker has been reached. There is no valid data in the file beyond this marker. |
| 0xC0000012 | {错误卷}驱动器中有错误卷。请插入卷 %hs 于驱动器 %hs 中。 |
{Wrong Volume}The wrong volume is in the drive.Please insert volume %hs into drive %hs. |
| 0xC0000013 | {没有磁盘}驱动器中没有磁盘。请在驱动器 %hs 中插入磁盘。 |
{No Disk}There is no disk in the drive.Please insert a disk into drive %hs. |
| 0xC0000014 | {未知的磁盘格式}驱动器 %hs 中的软盘尚未格式化。请检查该软盘，必要时请重新格式化。 |
{Unknown Disk Format}The disk in drive %hs is not formatted properly.Please check the disk, and reformat if necessary. |
| 0xC0000015 | {无法找到扇区}指定的扇区不存在。 |
{Sector Not Found}The specified sector does not exist. |
| 0xC0000016 | {仍在使用中}指定的 I/O 请求包(IRP)因 I/O 操作尚未完成而无法处理。 |
{Still Busy}The specified I/O request packet (IRP) cannot be disposed of because the I/O operation is not complete. |
| 0xC0000017 | {没有足够配额}没有足够的虚拟内存或分页文件配额以完成指定的操作。 |
{Not Enough Quota}Not enough virtual memory or paging file quota is available to complete the specified operation. |
| 0xC0000018 | {地址范围冲突}指定的地址范围与地址空间冲突。 |
{Conflicting Address Range}The specified address range conflicts with the address space. |
| 0xC0000019 | 无法查看未映射的地址范围。 |
Address range to unmap is not a mapped view. |
| 0xC000001A | 无法释放虚拟内存。 |
Virtual memory cannot be freed. |
| 0xC000001B | 无法删除指定的区域。 |
Specified section cannot be deleted. |
| 0xC000001C | 在系统服务调用中指定无效的系统服务。 |
An invalid system service was specified in a system service call. |
| 0xC000001D | {异常}无效的命令试图运行无效的指令。 |
{EXCEPTION}Illegal InstructionAn attempt was made to execute an illegal instruction. |
| 0xC000001E | {无效的锁定顺序}试图运行无效的锁定顺序。 |
{Invalid Lock Sequence}An attempt was made to execute an invalid lock sequence. |
| 0xC000001F | {无效映射}试图创建大于区域的区域查看。 |
{Invalid Mapping}An attempt was made to create a view for a section which is bigger than the section. |
| 0xC0000020 | {损坏的文件}无法读取内存区域的指定映射文件属性。 |
{Bad File}The attributes of the specified mapping file for a section of memory cannot be read. |
| 0xC0000021 | {已确认}指定的地址范围已确认。 |
{Already Committed}The specified address range is already committed. |
| 0xC0000022 | {无法访问}过程已请求访问一对象，但未给访问权限。 |
{Access Denied}A process has requested access to an object, but has not been granted those access rights. |
| 0xC0000024 | {错误类型}请求的操作所请求的对象类型与在请求中指定的对象类型不匹配。 |
{Wrong Type}There is a mismatch between the type of object required by the requested operation and the type of object that is specified in the request. |
| 0xC0000025 | {异常}无法继续Windows 无法从异常中继续。 |
{EXCEPTION}Cannot ContinueWindows cannot continue from this exception. |
| 0xC0000026 | 由异常处理程序返回一无效的异常部署。 |
An invalid exception disposition was returned by an exception handler. |
| 0xC0000027 | 解除异常代码。 |
Unwind exception code. |
| 0xC0000028 | 在解除操作期间遇到一个无效或不正确配置的堆栈。 |
An invalid or unaligned stack was encountered during an unwind operation. |
| 0xC0000029 | 在解除操作期间遇到一个无效的解除目标。 |
An invalid unwind target was encountered during an unwind operation. |
| 0xC000002A | 试图解除一个未被锁定的内存页面锁定。 |
An attempt was made to unlock a page of memory which was not locked. |
| 0xC000002B | I/O 操作时期的设备奇偶校验错误。 |
Device parity error on I/O operation. |
| 0xC000002C | 试图解除未确认的虚拟内存的信任。 |
An attempt was made to decommit uncommitted virtual memory. |
| 0xC000002D | 试图更改尚未提交的内存的属性。 |
An attempt was made to change the attributes on memory that has not been committed. |
| 0xC000002E | 指定给 NtCreatePort 的无效对象属性或指定给 NtConnectPort 的无效端口属性。 |
Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort |
| 0xC000002F | 发送给 NtRequestPort 或 NtRequestWaitReplyPort 的消息长度大于端口允许的最大长度。 |
Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port. |
| 0xC0000030 | 指定了无效的参数组合。 |
An invalid combination of parameters was specified. |
| 0xC0000031 | 试图降低配额限制，使低于当前的使用率。 |
An attempt was made to lower a quota limit below the current usage. |
| 0xC0000032 | {磁盘损坏}磁盘的文件系统结构已损坏且无法使用。请在卷 %hs 上运行 Chkdsk 工具。 |
{Corrupt Disk}The file system structure on the disk is corrupt and unusable.Please run the Chkdsk utility on the volume %hs. |
| 0xC0000033 | 对象名无效。 |
Object Name invalid. |
| 0xC0000034 | 找不到对象名。 |
Object Name not found. |
| 0xC0000035 | 对象名已存在。 |
Object Name already exists. |
| 0xC0000036 | 设置了“请勿打扰”标志的端口尝试向已暂停进程中的端口发送消息。该进程未被唤醒，并且该消息未送达。 |
A port with the 'do not disturb' flag set attempted to send a message to a port in a suspended process.The process was not woken, and the message was not delivered. |
| 0xC0000037 | 尝试给已断开连接的通讯端口发送消息。 |
Attempt to send a message to a disconnected communication port. |
| 0xC0000038 | 试图连接到已附加到其他设备的设备。 |
An attempt was made to attach to a device that was already attached to another device. |
| 0xC0000039 | 对象路径组件不是目录对象。 |
Object Path Component was not a directory object. |
| 0xC000003A | {无法取得路径}路径 %hs 不存在。 |
{Path Not Found}The path %hs does not exist. |
| 0xC000003C | {数据超限}发生数据越出错误。 |
{Data Overrun}A data overrun error occurred. |
| 0xC000003D | {数据延迟}发生数据延迟错误。 |
{Data Late}A data late error occurred. |
| 0xC000003E | {数据错误}发生数据读取或写入错误。 |
{Data Error}An error in reading or writing data occurred. |
| 0xC000003F | {CRC 不正确}发生循环冗余检验(CRC)的校验和错误。 |
{Bad CRC}A cyclic redundancy check (CRC) checksum error occurred. |
| 0xC0000040 | {区域过长}指定的区域过长以致于无法映射文件。 |
{Section Too Large}The specified section is too big to map the file. |
| 0xC0000041 | NtConnectPort 请求被拒绝。 |
The NtConnectPort request is refused. |
| 0xC0000042 | 操作所请求的端口句柄类型无效。 |
The type of port handle is invalid for the operation requested. |
| 0xC0000043 | 因共享访问标志不兼容而无法打开文件。 |
A file cannot be opened because the share access flags are incompatible. |
| 0xC0000044 | 配额不足，无法完成操作 |
Insufficient quota exists to complete the operation |
| 0xC0000045 | 指定的页面保护无效。 |
The specified page protection was not valid. |
| 0xC0000046 | 试图释放一线程所产生的衍生对象，该线程不是这个衍生对象的拥有者。 |
An attempt to release a mutant object was made by a thread that was not the owner of the mutant object. |
| 0xC0000047 | 试图释放已超过最大计数的信号灯。 |
An attempt was made to release a semaphore such that its maximum count would have been exceeded. |
| 0xC0000048 | 已试图设置进程的 DebugPort 或 ExceptionPort，但该进程中已存在端口，或试图设置文件的 CompletionPort，但文件中已设置端口，或已试图设置 ALPC 端口的相关完成端口，但该端口已设置。 |
An attempt to set a process's DebugPort or ExceptionPort was made, but a port already exists in the process or an attempt to set a file's CompletionPort made, but a port was already set in the file or an attempt to set an ALPC port's associated completion port was made, but it is already set. |
| 0xC0000049 | 试图在未映射映像的区域中查询映像信息。 |
An attempt was made to query image information on a section which does not map an image. |
| 0xC000004A | 已尝试在一个线程的暂停计数达到最大时将其暂停。 |
An attempt was made to suspend a thread whose suspend count was at its maximum. |
| 0xC000004B | 试图访问已开始终止的线程。 |
An attempt was made to access a thread that has begun termination. |
| 0xC000004C | 试图设置无效的工作组限制值(如最小值大于最大值)。 |
An attempt was made to set the working set limit to an invalid value (minimum greater than maximum, etc). |
| 0xC000004D | 创建映射文件的区域同已存在且映射同一文件的区域不兼容。 |
A section was created to map a file which is not compatible to an already existing section which maps the same file. |
| 0xC000004E | 区域的视图指定了和初始视图的保护不兼容的保护。 |
A view to a section specifies a protection which is incompatible with the initial view's protection. |
| 0xC000004F | 因文件系统不支持 EA 导致操作的 EA 失败。 |
An operation involving EAs failed because the file system does not support EAs. |
| 0xC0000050 | 因为 EA 集太大，EA 操作失败。 |
An EA operation failed because EA set is too large. |
| 0xC0000051 | 因为名称或 EA 索引无效，EA 操作失败。 |
An EA operation failed because the name or EA index is invalid. |
| 0xC0000052 | EA 请求的文件中没有 EA。 |
The file for which EAs were requested has no EAs. |
| 0xC0000053 | EA 已损坏并且不可读。 |
The EA is corrupt and non-readable. |
| 0xC0000054 | 由于文件锁定冲突而无法为要求的读取/写入授权。 |
A requested read/write cannot be granted due to a conflicting file lock. |
| 0xC0000055 | 由于其他存在的锁定而无法授予所需的文件锁定。 |
A requested file lock cannot be granted due to other existing locks. |
| 0xC0000056 | 延迟删除操作请求一文件对象的非关闭操作。 |
A non close operation has been requested of a file object with a delete pending. |
| 0xC0000057 | 试图设置文件的控制属性。目标文件系统不支持该属性。 |
An attempt was made to set the control attribute on a file. This attribute is not supported in the target file system. |
| 0xC0000058 | 表示已遇到或指定一服务未知的修定号码。该号码可能超过服务所知的最近修正。 |
Indicates a revision number encountered or specified is not one known by the service. It may be a more recent revision than the service is aware of. |
| 0xC0000059 | 表明两个修订级别是不兼容的。 |
Indicates two revision levels are incompatible. |
| 0xC000005A | 表示某一特定的安全性 ID 可能无法指派为一对象的所有者。 |
Indicates a particular Security ID may not be assigned as the owner of an object. |
| 0xC000005B | 表示某一特定的安全性 ID 可能无法指派为一对象的主要组。 |
Indicates a particular Security ID may not be assigned as the primary group of an object. |
| 0xC000005C | 目前未模仿客户端的线程试图在模仿令牌上操作。 |
An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client. |
| 0xC000005D | 可能无法禁用强制组。 |
A mandatory group may not be disabled. |
| 0xC000005E | 我们无法使用此凭据登录，因为你的域不可用。请确保你的设备已连接到你组织的网络，然后重试。如果你以前使用其他凭据登录到了此设备，则可以使用该凭据登录。 |
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. |
| 0xC000005F | 指定的登录会话不存在。可能已被终止。 |
A specified logon session does not exist. It may already have been terminated. |
| 0xC0000060 | 指定的特权不存在。 |
A specified privilege does not exist. |
| 0xC0000061 | 客户端没有所需的特权。 |
A required privilege is not held by the client. |
| 0xC0000062 | 提供的名称不是正确格式的帐户名。 |
The name provided is not a properly formed account name. |
| 0xC0000063 | 指定的帐户已存在。 |
The specified account already exists. |
| 0xC0000064 | 指定的帐户不存在。 |
The specified account does not exist. |
| 0xC0000065 | 指定的组已存在。 |
The specified group already exists. |
| 0xC0000066 | 指定的组不存在。 |
The specified group does not exist. |
| 0xC0000067 | 指定的用户帐户已存在于指定的组帐户中。同时用于指出由于组包含成员而不能将其删除。 |
The specified user account is already in the specified group account. Also used to indicate a group cannot be deleted because it contains a member. |
| 0xC0000068 | 指定的用户帐户不是指定组帐户的成员。 |
The specified user account is not a member of the specified group account. |
| 0xC0000069 | 表示请求的操作将禁用或删除管理员帐户，或禁止管理员帐户登录。为了防止出现无法管理系统的情况，禁止执行此操作。 |
Indicates the requested operation would disable, delete or could prevent logon for an administration account.This is not allowed to prevent creating a situation in which the system cannot be administrated. |
| 0xC000006A | 当试图更新密码时，本返回状态表示所提供的当前密码不正确。 |
When trying to update a password, this return status indicates that the value provided as the current password is not correct. |
| 0xC000006B | 当试图更新密码时，本返回状态表示所提供的新密码中包含不被允许的值。 |
When trying to update a password, this return status indicates that the value provided for the new password contains values that are not allowed in passwords. |
| 0xC000006C | 当试图更新密码时，本状态表示已违反某些密码更新规则。例如，密码不符合长度标准。 |
When trying to update a password, this status indicates that some password update rule has been violated. For example, the password may not meet length criteria. |
| 0xC000006D | 登录无效。可能原因为无效的用户名或验证信息。 |
The attempted logon is invalid. This is either due to a bad username or authentication information. |
| 0xC000006E | 表示参考的用户名及验证信息合法，但某些用户帐户限制验证没有成功(如日期时间限制)。 |
Indicates a referenced user name and authentication information are valid, but some user account restriction has prevented successful authentication (such as time-of-day restrictions). |
| 0xC000006F | 用户帐户设有时间限制而无法在此期间内登录。 |
The user account has time restrictions and may not be logged onto at this time. |
| 0xC0000070 | 用户帐户设有时间限制而无法从源工作站登录。 |
The user account is restricted such that it may not be used to log on from the source workstation. |
| 0xC0000071 | 用户帐户的密码已过期。 |
The user account's password has expired. |
| 0xC0000072 | 参考帐户当前已禁用且无法登录。 |
The referenced account is currently disabled and may not be logged on to. |
| 0xC0000073 | 尚未解释任何信息。 |
None of the information to be translated has been translated. |
| 0xC0000074 | LUID 请求的数量无法分配单一单位。 |
The number of LUIDs requested may not be allocated with a single allocation. |
| 0xC0000075 | 表示不需要再分配任何的 LUID。 |
Indicates there are no more LUIDs to allocate. |
| 0xC0000076 | 表示特定用途的次权限值无效。 |
Indicates the sub-authority value is invalid for the particular use. |
| 0xC0000077 | 表示 ACL 结构无效。 |
Indicates the ACL structure is not valid. |
| 0xC0000078 | 表示 SID 结构无效。 |
Indicates the SID structure is not valid. |
| 0xC0000079 | 表示 SECURITY_DESCRIPTOR 结构无效。 |
Indicates the SECURITY_DESCRIPTOR structure is not valid. |
| 0xC000007A | 指出在 DLL 中找不到指定的过程地址。 |
Indicates the specified procedure address cannot be found in the DLL. |
| 0xC000007B | {损坏的映像}%hs 没有被指定在 Windows 上运行，或者它包含错误。请尝试使用原始安装介质重新安装程序，或联系你的系统管理员或软件供应商以获取支持。错误状态 0x%08lx。 |
{Bad Image}%hs is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x%08lx. |
| 0xC000007C | 已尝试参考一个不存在的令牌。这样的典型情况是在一个线程没有模仿客户端的时候参考和它关联的令牌。 |
An attempt was made to reference a token that doesn't exist.This is typically done by referencing the token associated with a thread when the thread is not impersonating a client. |
| 0xC000007D | 表示试图创建一继承的 ACL 或 ACE 失败。导致其发生的因素很多。其中最可能的原因为以 SID 替换创建者标识而无法与 ACE 或 ACL 相配合。 |
Indicates that an attempt to build either an inherited ACL or ACE was not successful.This can be caused by a number of things. One of the more probable causes is the replacement of a CreatorId with an SID that didn't fit into the ACE or ACL. |
| 0xC000007E | 未锁定在 NtUnlockFile 中的指定范围。 |
The range specified in NtUnlockFile was not locked. |
| 0xC000007F | 由于磁盘已满，操作失败。如果这是精简预配的卷，则支持此卷的物理存储已用尽。 |
An operation failed because the disk was full.If this is a thinly provisioned volume the physical storage backing this volume has been exhausted. |
| 0xC0000080 | GUID 分配服务器此时已禁用。 |
The GUID allocation server is [already] disabled at the moment. |
| 0xC0000081 | GUID 分配服务器此时已启用。 |
The GUID allocation server is [already] enabled at the moment. |
| 0xC0000082 | 一次从分配服务器请求太多的 GUID。 |
Too many GUIDs were requested from the allocation server at once. |
| 0xC0000083 | 因权限代理已用尽而无法分配 GUID。 |
The GUIDs could not be allocated because the Authority Agent was exhausted. |
| 0xC0000084 | 所提供的值是无效的标识符颁发机构的值。 |
The value provided was an invalid value for an identifier authority. |
| 0xC0000085 | 标识符权限值中无任何可用的权限代理值。 |
There are no more authority agent values available for the given identifier authority value. |
| 0xC0000086 | 指定了无效的卷标。 |
An invalid volume label has been specified. |
| 0xC0000087 | 无法扩展映射区域。 |
A mapped section could not be extended. |
| 0xC0000088 | 无法在指定清除的区域中映射数据文件。 |
Specified section to flush does not map a data file. |
| 0xC0000089 | 表示指定的映像文件中不包含资源部分。 |
Indicates the specified image file did not contain a resource section. |
| 0xC000008A | 指出在映像文件中找不到指定的资源类型。 |
Indicates the specified resource type cannot be found in the image file. |
| 0xC000008B | 指出在映像文件中找不到指定的资源名称。 |
Indicates the specified resource name cannot be found in the image file. |
| 0xC000008C | {异常}数组越界。 |
{EXCEPTION}Array bounds exceeded. |
| 0xC000008D | {异常}浮点的非正规操作数。 |
{EXCEPTION}Floating-point denormal operand. |
| 0xC000008E | {异常}除以 0 的浮点运算。 |
{EXCEPTION}Floating-point division by zero. |
| 0xC000008F | {异常}浮点运算的不精确值。 |
{EXCEPTION}Floating-point inexact result. |
| 0xC0000090 | {异常}浮点运算的无效操作。 |
{EXCEPTION}Floating-point invalid operation. |
| 0xC0000091 | {异常}浮点运算溢出。 |
{EXCEPTION}Floating-point overflow. |
| 0xC0000092 | {异常}浮点运算堆栈检测。 |
{EXCEPTION}Floating-point stack check. |
| 0xC0000093 | {异常}浮点运算下溢。 |
{EXCEPTION}Floating-point underflow. |
| 0xC0000094 | {异常}整数除 0。 |
{EXCEPTION}Integer division by zero. |
| 0xC0000095 | {异常}整数溢出。 |
{EXCEPTION}Integer overflow. |
| 0xC0000096 | {异常}特权指令。 |
{EXCEPTION}Privileged instruction. |
| 0xC0000097 | 试图安装超过系统支持的分页文件数。 |
An attempt was made to install more paging files than the system supports. |
| 0xC0000098 | 文件卷标已在外部被改变，打开的文件不再有效。 |
The volume for a file has been externally altered such that the opened file is no longer valid. |
| 0xC0000099 | 当内存块分配用以未来更新使用时，如将内存分配为保持自由访问控制及主要组信息，后续的更新可能会超过原始所分配的内存数量。因为配额可能已分配给许多含有对象句柄的过程，所以最好不更改已分配内存的大小。相反地，一项请求多于已分配内存的请求将失败且会返回 STATUS_ALLOTED_SPACE_EXCEEDED 错误。 |
When a block of memory is allotted for future updates, such as the memory allocated to hold discretionary access control and primary group information, successive updates may exceed the amount of memory originally allotted.Since quota may already have been charged to several processes which have handles to the object, it is not reasonable to alter the size of the allocated memory.Instead, a request that requires more memory than has been allotted must fail and the STATUS_ALLOTED_SPACE_EXCEEDED error returned. |
| 0xC000009A | 系统资源不够，无法完成 API。 |
Insufficient system resources exist to complete the API. |
| 0xC000009B | 已尝试打开 DFS 退出路径控制文件。 |
An attempt has been made to open a DFS exit path control file. |
| 0xC000009C | STATUS_DEVICE_DATA_ERROR |
STATUS_DEVICE_DATA_ERROR |
| 0xC000009D | STATUS_DEVICE_NOT_CONNECTED |
STATUS_DEVICE_NOT_CONNECTED |
| 0xC000009E | STATUS_DEVICE_POWER_FAILURE |
STATUS_DEVICE_POWER_FAILURE |
| 0xC000009F | 当基址不为区域基址且已指定 0 的区域大小时，无法释放虚拟内存。 |
Virtual memory cannot be freed as base address is not the base of the region and a region size of zero was specified. |
| 0xC00000A0 | 试图释放未分配的虚拟内存。 |
An attempt was made to free virtual memory which is not allocated. |
| 0xC00000A1 | 工作组大小不足，无法允许所请求的页面锁定。 |
The working set is not big enough to allow the requested pages to be locked. |
| 0xC00000A2 | {写保护错误}因磁盘有写保护而无法写入磁盘。请在驱动器 %hs 中删除卷 %hs 的写保护。 |
{Write Protect Error}The disk cannot be written to because it is write protected. Please remove the write protection from the volume %hs in drive %hs. |
| 0xC00000A3 | {驱动器未就绪}驱动器未就绪；可能未关闭驱动器门。请检查驱动器 %hs 并确定已插入磁盘且驱动器门已关闭。 |
{Drive Not Ready}The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed. |
| 0xC00000A4 | 指定的特性无效，或不与组的特性兼容。 |
The specified attributes are invalid, or incompatible with the attributes for the group as a whole. |
| 0xC00000A5 | 指定的模拟等级无效。同时也表示未提供所请求的模拟等级。 |
A specified impersonation level is invalid.Also used to indicate a required impersonation level was not provided. |
| 0xC00000A6 | 试图打开一匿名等级令牌。匿名等级令牌可能无法打开。 |
An attempt was made to open an Anonymous level token.Anonymous tokens may not be opened. |
| 0xC00000A7 | 请求的验证信息类别无效。 |
The validation information class requested was invalid. |
| 0xC00000A8 | 令牌对象类型不适合其用途。 |
The type of a token object is inappropriate for its attempted use. |
| 0xC00000AA | 试图在未分配的地址上执行指令，且主机系统不支持未分配的命令引用。 |
An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references. |
| 0xC00000AB | 已达到了最大的命名管道范例数量。 |
The maximum named pipe instance count has been reached. |
| 0xC00000AC | 在侦听状态中找不到已命名管道的范例。 |
An instance of a named pipe cannot be found in the listening state. |
| 0xC00000AD | 命名管道不处于连接或关闭状态。 |
The named pipe is not in the connected or closing state. |
| 0xC00000AE | 已指定管道运行操作，但当前已存在 I/O 操作队列，所以无法更改为队列操作。 |
The specified pipe is set to complete operations and there are current I/O operations queued so it cannot be changed to queue operations. |
| 0xC00000AF | 指定的句柄对命名管道的服务器端不开放。 |
The specified handle is not open to the server end of the named pipe. |
| 0xC00000B0 | 指定的命名管道处于断开连接状态。 |
The specified named pipe is in the disconnected state. |
| 0xC00000B1 | 指定的命名管道处于关闭状态。 |
The specified named pipe is in the closing state. |
| 0xC00000B2 | 指定的命名管道处于连接状态。 |
The specified named pipe is in the connected state. |
| 0xC00000B3 | 指定的命名管道处于侦听状态。 |
The specified named pipe is in the listening state. |
| 0xC00000B4 | 指定的命名管道不处于消息模式。 |
The specified named pipe is not in message mode. |
| 0xC00000B5 | {设备超时}在 %hs 上指定的 I/O 操作无法在超时过期之前完成。 |
{Device Timeout}The specified I/O operation on %hs was not completed before the time-out period expired. |
| 0xC00000B6 | 指定的文件已被另一个过程关闭。 |
The specified file has been closed by another process. |
| 0xC00000B7 | 未启动配置文件。 |
Profiling not started. |
| 0xC00000B8 | 未停止配置文件。 |
Profiling not stopped. |
| 0xC00000B9 | 传送的 ACL 不包含最低要求的信息。 |
The passed ACL did not contain the minimum required information. |
| 0xC00000BA | 指定的目标文件为目录，但调用方指定其为除目录外的任何值。 |
The file that was specified as a target is a directory and the caller specified that it could be anything but a directory. |
| 0xC00000BB | 不支持该请求。 |
The request is not supported. |
| 0xC00000BC | 远程计算机未处于侦听状态。 |
This remote computer is not listening. |
| 0xC00000BD | 网络上有重名。 |
A duplicate name exists on the network. |
| 0xC00000BE | 无法定位网络路径。 |
The network path cannot be located. |
| 0xC00000BF | 网络很忙。 |
The network is busy. |
| 0xC00000C0 | 此设备不存在。 |
This device does not exist. |
| 0xC00000C1 | 已达到网络 BIOS 命令限制。 |
The network BIOS command limit has been reached. |
| 0xC00000C2 | 出现了 I/O 适配器硬件错误。 |
An I/O adapter hardware error has occurred. |
| 0xC00000C3 | 网络响应不正确。 |
The network responded incorrectly. |
| 0xC00000C4 | 出现了意外的网络错误。 |
An unexpected network error occurred. |
| 0xC00000C5 | 远程适配器不兼容。 |
The remote adapter is not compatible. |
| 0xC00000C6 | 打印机队列已满。 |
The printer queue is full. |
| 0xC00000C7 | 服务器上没有储存等待打印的文件的空间。 |
Space to store the file waiting to be printed is not available on the server. |
| 0xC00000C8 | 已取消请求打印的文件。 |
The requested print file has been canceled. |
| 0xC00000C9 | 网络名已删除。 |
The network name was deleted. |
| 0xC00000CA | 拒绝网络访问。 |
Network access is denied. |
| 0xC00000CB | {不正确的网络资源类型}指定的设备类型(如 LPT)与远程资源上的实际设备类型相冲突。 |
{Incorrect Network Resource Type}The specified device type (LPT, for example) conflicts with the actual device type on the remote resource. |
| 0xC00000CC | {无法找到网络名}无法在远程服务器上找到指定共享名。 |
{Network Name Not Found}The specified share name cannot be found on the remote server. |
| 0xC00000CD | 超出本地计算机网络适配器卡的名称限制。 |
The name limit for the local computer network adapter card was exceeded. |
| 0xC00000CE | 超出了网络 BIOS 会话限制。 |
The network BIOS session limit was exceeded. |
| 0xC00000CF | 已暂停文件共享。 |
File sharing has been temporarily paused. |
| 0xC00000D0 | 已达到计算机的连接数最大值，无法再同此远程计算机连接。 |
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. |
| 0xC00000D1 | 已暂停打印机或磁盘重定向。 |
Print or disk redirection is temporarily paused. |
| 0xC00000D2 | 出现了网络数据错误。 |
A network data fault occurred. |
| 0xC00000D3 | 使用中的配置文件对象的数量已到达最大值且无法再启动任何对象。 |
The number of active profiling objects is at the maximum and no more may be started. |
| 0xC00000D4 | {不正确的卷}请求更改名称的目标文件同请求所在的源位于不同的设备。 |
{Incorrect Volume}The target file of a rename request is located on a different device than the source of the rename request. |
| 0xC00000D5 | 指定的文件已重命名因而无法修改。 |
The file specified has been renamed and thus cannot be modified. |
| 0xC00000D6 | {网络请求超时}因为请求的超时间隔已过期，与远程服务器的会话被断开连接。 |
{Network Request Timeout}The session with a remote server has been disconnected because the time-out interval for a request has expired. |
| 0xC00000D7 | 表示试图在同安全设置无关的对象上运行操作。 |
Indicates an attempt was made to operate on the security of an object that does not have security associated with it. |
| 0xC00000D8 | 用于指出如果不阻止以等待 I/O，操作将无法继续进行。 |
Used to indicate that an operation cannot continue without blocking for I/O. |
| 0xC00000D9 | 用以表示已运行空管道中的读取操作。 |
Used to indicate that a read operation was done on an empty pipe. |
| 0xC00000DA | 无法从域控制器读取配置信息，因为计算机不可用，或者因为访问已被拒绝。 |
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. |
| 0xC00000DB | 表示一线程试图依默认值终止其本身(以 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. |
| 0xC00000DC | 表示 Sam 服务器处于运行操作的错误状态。 |
Indicates the Sam Server was in the wrong state to perform the desired operation. |
| 0xC00000DD | 表示域处于运行操作的错误状态。 |
Indicates the Domain was in the wrong state to perform the desired operation. |
| 0xC00000DE | 该操作只能在主域控制器执行。 |
This operation is only allowed for the Primary Domain Controller of the domain. |
| 0xC00000DF | 指定的域不存在。 |
The specified Domain did not exist. |
| 0xC00000E0 | 指定的域已存在。 |
The specified Domain already exists. |
| 0xC00000E1 | 试图超过该版本的每服务器上域数量限制。 |
An attempt was made to exceed the limit on the number of domains per server for this release. |
| 0xC00000E2 | 当 oplock 请求被拒绝后返回错误状态。 |
Error status returned when oplock request is denied. |
| 0xC00000E3 | 当无效的 oplock 确认被文件系统接收后返回错误状态。 |
Error status returned when an invalid oplock acknowledgment is received by a file system. |
| 0xC00000E4 | 该错误指出由于灾难性的媒体失败或磁盘数据结构损坏而无法完成所需的操作。 |
This error indicates that the requested operation cannot be completed due to a catastrophic media failure or on-disk data structure corruption. |
| 0xC00000E5 | 出现了内部错误。 |
An internal error occurred. |
| 0xC00000E6 | 表示已映射至非一般访问类型的访问屏蔽中，应包含一般的访问类型。 |
Indicates generic access types were contained in an access mask which should already be mapped to non-generic access types. |
| 0xC00000E7 | 表示不须设置安全描述符的特定格式(绝对或自我相对)。 |
Indicates a security descriptor is not in the necessary format (absolute or self-relative). |
| 0xC00000E8 | 在“预期”的时间点上访问用户缓冲区失败。由于调用方不希望接受其筛选器中的 STATUS_ACCESS_VIOLATION，因此定义了该代码。 |
An access to a user buffer failed at an \"expected\" point in time. This code is defined since the caller does not want to accept STATUS_ACCESS_VIOLATION in its filter. |
| 0xC00000E9 | 如果返回一个未在标准 FsRtl 筛选器中定义的 I/O 错误，该错误将转换为保证位于筛选器中的以下错误。在这种情况下，将会丢失信息，但筛选器能正确处理该异常情况。 |
If an I/O error is returned which is not defined in the standard FsRtl filter, it is converted to the following error which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. |
| 0xC00000EA | 如果返回一个未在标准 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. |
| 0xC00000ED | 请求的操作只准登录过程使用。该调用过程并未被记录为登录过程。 |
The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process. |
| 0xC00000EE | 已尝试用正在使用的 ID 启动新的会话管理器或 LSA 登录会话。 |
An attempt has been made to start a new session manager or LSA logon session with an ID that is already in use. |
| 0xC00000EF | 一个无效参数作为第一个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the first argument. |
| 0xC00000F0 | 一个无效参数作为第二个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the second argument. |
| 0xC00000F1 | 一个无效参数作为第三个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the third argument. |
| 0xC00000F2 | 一个无效参数作为第四个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the fourth argument. |
| 0xC00000F3 | 一个无效参数作为第五个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the fifth argument. |
| 0xC00000F4 | 一个无效参数作为第六个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the sixth argument. |
| 0xC00000F5 | 一个无效参数作为第七个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the seventh argument. |
| 0xC00000F6 | 一个无效参数作为第八个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the eighth argument. |
| 0xC00000F7 | 一个无效参数作为第九个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the ninth argument. |
| 0xC00000F8 | 一个无效参数作为第十个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the tenth argument. |
| 0xC00000F9 | 一个无效参数作为第十一个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the eleventh argument. |
| 0xC00000FA | 一个无效参数作为第十二个参数传递给了服务或函数。 |
An invalid parameter was passed to a service or function as the twelfth argument. |
| 0xC00000FB | 试图访问一个网络文件，但网络软件尚未启动。 |
An attempt was made to access a network file, but the network software was not yet started. |
| 0xC00000FC | 试图启动一个转发程序，但该转发程序已启动。 |
An attempt was made to start the redirector, but the redirector has already been started. |
| 0xC00000FD | 无法创建新的堆栈防护页面。 |
A new guard page for the stack cannot be created. |
| 0xC00000FE | 指定的身份验证数据包未知。 |
A specified authentication package is unknown. |
| 0xC00000FF | 在释放操作期间遇到格式不正确的功能表。 |
A malformed function table was encountered during an unwind operation. |
| 0xC0000100 | 表示无法在指定的环境区块中找到指定的环境变量名。 |
Indicates the specified environment variable name was not found in the specified environment block. |
| 0xC0000101 | 要删除的目录不是空的。 |
Indicates that the directory trying to be deleted is not empty. |
| 0xC0000102 | {损坏文件}文件或目录 %hs 已损坏且无法读取。请运行 Chkdsk 工具。 |
{Corrupt File}The file or directory %hs is corrupt and unreadable.Please run the Chkdsk utility. |
| 0xC0000103 | 要求的已打开文件不是目录。 |
A requested opened file is not a directory. |
| 0xC0000104 | 登录会话并非处于与请求操作一致的状态中。 |
The logon session is not in a state that is consistent with the requested operation. |
| 0xC0000105 | 发生了内部 LSA 错误。验证软件包请求创建登录会话，但指定了一个已有的登录会话 ID。 |
An internal LSA error has occurred. An authentication package has requested the creation of a Logon Session but the ID of an already existing Logon Session has been specified. |
| 0xC0000106 | 指定的名称字符串过长。 |
A specified name string is too long for its intended use. |
| 0xC0000107 | 用户试图强制关闭已重定向驱动器上的文件，但该驱动器上仍有打开的文件，且用户并未指定足够的权限等级。 |
The user attempted to force close the files on a redirected drive, but there were opened files on the drive, and the user did not specify a sufficient level of force. |
| 0xC0000108 | 用户试图强制关闭已重定向驱动器上的文件，但该驱动器上仍有打开的目录，且用户并未指定足够的权限等级。 |
The user attempted to force close the files on a redirected drive, but there were opened directories on the drive, and the user did not specify a sufficient level of force. |
| 0xC0000109 | RtlFindMessage 无法在消息表资源中定位所需的消息 ID。 |
RtlFindMessage could not locate the requested message ID in the message table resource. |
| 0xC000010A | 已尝试访问正在退出的过程。 |
An attempt was made to access an exiting process. |
| 0xC000010B | 为要求的 LogonType 提供了无效的值。 |
Indicates an invalid value has been provided for the LogonType requested. |
| 0xC000010C | 表示试图保护文件系统上的文件或目录且无法将安全描述符中的某一 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. |
| 0xC000010D | 试图通过一尚未读取的命名管道来运行模拟。 |
Indicates that an attempt has been made to impersonate via a named pipe that has not yet been read from. |
| 0xC000010E | 表示已加载指定的映像。 |
Indicates that the specified image is already loaded. |
| 0xC000010F | STATUS_ABIOS_NOT_PRESENT |
STATUS_ABIOS_NOT_PRESENT |
| 0xC0000110 | STATUS_ABIOS_LID_NOT_EXIST |
STATUS_ABIOS_LID_NOT_EXIST |
| 0xC0000111 | STATUS_ABIOS_LID_ALREADY_OWNED |
STATUS_ABIOS_LID_ALREADY_OWNED |
| 0xC0000112 | STATUS_ABIOS_NOT_LID_OWNER |
STATUS_ABIOS_NOT_LID_OWNER |
| 0xC0000113 | STATUS_ABIOS_INVALID_COMMAND |
STATUS_ABIOS_INVALID_COMMAND |
| 0xC0000114 | STATUS_ABIOS_INVALID_LID |
STATUS_ABIOS_INVALID_LID |
| 0xC0000115 | STATUS_ABIOS_SELECTOR_NOT_AVAILABLE |
STATUS_ABIOS_SELECTOR_NOT_AVAILABLE |
| 0xC0000116 | STATUS_ABIOS_INVALID_SELECTOR |
STATUS_ABIOS_INVALID_SELECTOR |
| 0xC0000117 | 试图为无 LDT 的过程更改 LDT 的大小。 |
Indicates that an attempt was made to change the size of the LDT for a process that has no LDT. |
| 0xC0000118 | 试图通过设置 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. |
| 0xC0000119 | LDT 信息的启动值不是选择器大小的整数倍。 |
Indicates that the starting value for the LDT information was not an integral multiple of the selector size. |
| 0xC000011A | 试图设置 Ldt 描述符时用户提供了无效的描述符。 |
Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors. |
| 0xC000011B | 指定的映像文件格式不对。它可能是 NE 格式。 |
The specified image file did not have the correct format. It appears to be NE format. |
| 0xC000011C | 指出注册表子目录树的事务状态与所请求操作不兼容。例如，在一个事务尚在运行中时请求启动一个新事务，或在当前未运行事务的情况下请求应用某个事务。 |
Indicates that the transaction state of a registry sub-tree is incompatible with the requested operation. For example, a request has been made to start a new transaction with one already in progress, or a request has been made to apply a transaction when one is not currently in progress. |
| 0xC000011D | 指出在注册表事务确认期间出错。数据库已处于可能不一致的未知状态。注册表事务的状态保留为 COMMITTING。 |
Indicates an error has occurred during a registry transaction commit. The database has been left in an unknown, but probably inconsistent, state. The state of the registry transaction is left as COMMITTING. |
| 0xC000011E | 试图以最大值为 0 的大小映射一大小为 0 的文件。 |
An attempt was made to map a file of size zero with the maximum size specified as zero. |
| 0xC000011F | 远程服务器打开过多的文件。该错误仅可由远程驱动器上的 Windows 转发程序返回。 |
Too many files are opened on a remote server.This error should only be returned by the Windows redirector on a remote drive. |
| 0xC0000120 | I/O 请求已取消。 |
The I/O request was canceled. |
| 0xC0000121 | 试图删除一无法删除的文件或目录。 |
An attempt has been made to remove a file or directory that cannot be deleted. |
| 0xC0000122 | 表示指定的远程计算机名语法错误。 |
Indicates a name specified as a remote computer name is syntactically invalid. |
| 0xC0000123 | 在删除文件之后对该文件执行除关闭以外的 I/O 请求，仅适用于在以 NtClose 关闭最后句柄之前未完成的请求。 |
An I/O request other than close was performed on a file after it has been deleted, which can only happen to a request which did not complete before the last handle was closed via NtClose. |
| 0xC0000124 | 指出已在与内置帐户不兼容的内置(特殊) SAM 帐户上尝试执行某个操作。例如，无法删除内置帐户。 |
Indicates an operation has been attempted on a built-in (special) SAM account which is incompatible with built-in accounts. For example, built-in accounts cannot be deleted. |
| 0xC0000125 | 无法在指定的内置特殊组上运行请求的操作。 |
The operation requested may not be performed on the specified group because it is a built-in special group. |
| 0xC0000126 | 因为指定的用户是内置特殊用户，无法对其执行要求的操作。 |
The operation requested may not be performed on the specified user because it is a built-in special user. |
| 0xC0000127 | 指出当组当前是其成员的主要组时，不能将其成员从中删除。 |
Indicates a member cannot be removed from a group because the group is currently the member's primary group. |
| 0xC0000128 | 试图用已关闭的文件对象来运行除关闭及其他特殊操作以外的 I/O 请求。 |
An I/O request other than close and several other special case operations was attempted using a file object that had already been closed. |
| 0xC0000129 | 表示执行请求操作的进程中有过多的线程。例如，只可在进程没有或仅有一个线程时分配主令牌。 |
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. |
| 0xC000012A | 试图在特定的进程中运行线程，但所指定的线程不在指定的进程中。 |
An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified. |
| 0xC000012B | 试图以使用中的令牌创建主要令牌。过程内一次只能有一个主要令牌。 |
An attempt was made to establish a token for use as a primary token but the token is already in use. A token can only be the primary token of one process at a time. |
| 0xC000012C | 超过页面文件配额。 |
Page file quota was exceeded. |
| 0xC000012D | {虚拟内存不足}你的系统虚拟内存不足。要确保 Windows 运行正常，请增加虚拟内存分页文件的大小。有关详细信息，请参阅“帮助”。 |
{Out of Virtual Memory}Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help. |
| 0xC000012E | 指定的映像文件的格式不正确，可能为 LE 格式。 |
The specified image file did not have the correct format, it appears to be LE format. |
| 0xC000012F | 指定的映像文件的格式不正确，没有初始 MZ。 |
The specified image file did not have the correct format, it did not have an initial MZ. |
| 0xC0000130 | 指定的映像文件的格式不正确，在 MZ 头中没有适当的 e_lfarlc。 |
The specified image file did not have the correct format, it did not have a proper e_lfarlc in the MZ header. |
| 0xC0000131 | 指定的映像文件格式不对，它可能是 16 位的 Windows 映像。 |
The specified image file did not have the correct format, it appears to be a 16-bit Windows image. |
| 0xC0000132 | 因在域中运行的其他 Netlogon 服务与指定的角色冲突而无法启动 Netlogon 服务。 |
The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role. |
| 0xC0000133 | 主域控制器上的时间和辅助域控制器或成员服务器上的时间相差很大。 |
The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by too large an amount. |
| 0xC0000134 | 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. |
| 0xC0000135 | 由于找不到 %hs，无法继续执行代码。重新安装程序可能会解决此问题。 |
The code execution cannot proceed because %hs was not found. Reinstalling the program may fix this problem. |
| 0xC0000136 | 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. |
| 0xC0000137 | {特权失败}无法更改过程的 I/O 权限。 |
{Privilege Failed}The I/O permissions for the process could not be changed. |
| 0xC0000138 | {找不到序数}无法定位序数 %ld 于动态链接库 %hs 上。 |
{Ordinal Not Found}The ordinal %ld could not be located in the dynamic link library %hs. |
| 0xC0000139 | {无法找到入口}无法定位程序输入点 %hs 于动态链接库 %hs 上。 |
{Entry Point Not Found}The procedure entry point %hs could not be located in the dynamic link library %hs. |
| 0xC000013A | {使用 CTRL+C 退出应用程序}使用 CTRL+C 终止应用程序。 |
{Application Exit by CTRL+C}The application terminated as a result of a CTRL+C. |
| 0xC000013B | {关闭虚电路}你计算机上的网络传输已关闭网络连接。原因可能为无法处理的 I/O 请求。 |
{Virtual Circuit Closed}The network transport on your computer has closed a network connection. There may or may not be I/O requests outstanding. |
| 0xC000013C | {关闭虚电路}远程计算机的网络传输已关闭网络连接。原因可能为无法处理的 I/O 请求。 |
{Virtual Circuit Closed}The network transport on a remote computer has closed a network connection. There may or may not be I/O requests outstanding. |
| 0xC000013D | {远程计算机资源不足}远程计算机的资源不足而无法完成网络请求。例如，远程计算机的内存不足而无法完成当前的请求。 |
{Insufficient Resources on Remote Computer}The remote computer has insufficient resources to complete the network request. For instance, there may not be enough memory available on the remote computer to carry out the request at this time. |
| 0xC000013E | {关闭虚电路}远程计算机上的现有连接(虚电路)已中断。可能是远程计算机的网络软件协议或网络硬件有错。 |
{Virtual Circuit Closed}An existing connection (virtual circuit) has been broken at the remote computer. There is probably something wrong with the network software protocol or the network hardware on the remote computer. |
| 0xC000013F | {关闭虚电路}因等待远程计算机的响应时间过长，你计算机上的网络传输已关闭网络连接。 |
{Virtual Circuit Closed}The network transport on your computer has closed a network connection because it had to wait too long for a response from the remote computer. |
| 0xC0000140 | 无效的传输连接句柄。 |
The connection handle given to the transport was invalid. |
| 0xC0000141 | 无效的传输地址句柄。 |
The address handle given to the transport was invalid. |
| 0xC0000142 | {DLL 初始化失败}动态链接库 %hs 初始化失败。过程非正常终止。 |
{DLL Initialization Failed}Initialization of the dynamic link library %hs failed. The process is terminating abnormally. |
| 0xC0000143 | {无法取得系统文件}必须的系统文件 %hs 损坏或丢失。 |
{Missing System File}The required system file %hs is bad or missing. |
| 0xC0000144 | {应用程序错误}应用程序发生异常 %s (0x%08lx)，位置为 0x%p。 |
{Application Error}The exception %s (0x%08lx) occurred in the application at location 0x%p. |
| 0xC0000145 | {应用程序错误}应用程序无法正常启动(0x%lx)。请单击“确定”关闭应用程序。 |
{Application Error}The application was unable to start correctly (0x%lx). Click OK to close the application. |
| 0xC0000146 | {无法创建页面文件}创建分页文件 %hs 失败(%lx)。而请求的文件大小为 %ld。 |
{Unable to Create Paging File}The creation of the paging file %hs failed (%lx). The requested size was %ld. |
| 0xC0000147 | {未指定页面文件}未在系统配置中指定分页文件。 |
{No Paging File Specified}No paging file was specified in the system configuration. |
| 0xC0000148 | {不正确的系统调用等级}发送一个无效的等级给指定的系统调用。 |
{Incorrect System Call Level}An invalid level was passed into the specified system call. |
| 0xC0000149 | {不正确的 LAN Manager 服务器密码}指定了一个不正确的 LAN Manager 2.x 或 MS-NET 服务器密码。 |
{Incorrect Password to LAN Manager Server}You specified an incorrect password to a LAN Manager 2.x or MS-NET server. |
| 0xC000014A | {异常}实模式应用程序发出浮点运算指令而浮点运算硬件不存在。 |
{EXCEPTION}A real-mode application issued a floating-point instruction and floating-point hardware is not present. |
| 0xC000014B | 因已关闭管道操作的另一端而使管道操作失败。 |
The pipe operation has failed because the other end of the pipe has been closed. |
| 0xC000014C | {注册表损坏}包含注册表数据的某一文件结构已损坏，或该文件的内存映像已损坏，或因替代备份或记录缺少或损坏而无法恢复该文件。 |
{The Registry Is Corrupt}The structure of one of the files that contains Registry data is corrupt, or the image of the file in memory is corrupt, or the file could not be recovered because the alternate copy or log was absent or corrupt. |
| 0xC000014D | 由注册表启动的 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. |
| 0xC000014E | 使用线程的特定客户端/服务器事件对对象运行事件对同步操作，但无任何事件对对象与该线程关联。 |
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. |
| 0xC000014F | 卷不包括已识别的文件系统。请确保已加载所有必需的文件系统驱动程序，并且卷未损坏。 |
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 corrupt. |
| 0xC0000150 | 串行设备初始化不成功。串行驱动程序将卸载。 |
No serial device was successfully initialized. The serial driver will unload. |
| 0xC0000151 | 指定的本地组不存在。 |
The specified local group does not exist. |
| 0xC0000152 | 指定的帐户名不是此组的成员。 |
The specified account name is not a member of the group. |
| 0xC0000153 | 指定的帐户名已是此组的成员。 |
The specified account name is already a member of the group. |
| 0xC0000154 | 指定的本地组已存在。 |
The specified local group already exists. |
| 0xC0000155 | 目标系统的本地安全策略不承认所请求的登录类型(如交互用户、网络用户、服务用户)。请询问系统管理员以取得允许的登录格式。 |
A requested type of logon (e.g., Interactive, Network, Service) is not granted by the target system's local security policy.Please ask the system administrator to grant the necessary form of logon. |
| 0xC0000156 | 超过单一系统所能保存的最大机密数。机密的长度及数量受限于美国国务院的出口管制。 |
The maximum number of secrets that may be stored in a single system has been exceeded. The length and number of secrets is limited to satisfy United States State Department export restrictions. |
| 0xC0000157 | 密码的长度超过允许的最大长度。机密的长度及数量受限于美国国务院的出口管制。 |
The length of a secret exceeds the maximum length allowed. The length and number of secrets is limited to satisfy United States State Department export restrictions. |
| 0xC0000158 | 本地安全权限(LSA)数据库包含内部的不一致。 |
The Local Security Authority (LSA) database contains an internal inconsistency. |
| 0xC0000159 | 请求的操作无法在全屏幕模式下运行。 |
The requested operation cannot be performed in fullscreen mode. |
| 0xC000015A | 在尝试登录期间，用户的安全上下文已累积过多的安全 ID。这种状况非常不寻常。请从某些全局组或本地组中删除该用户，以减少要合并到安全上下文中的安全 ID 数。 |
During a logon attempt, the user's security context accumulated too many security IDs. This is a very unusual situation. Remove the user from some global or local groups to reduce the number of security ids to incorporate into the security context. |
| 0xC000015B | 用户要求一种未授权的登录方式(例如，交互或网络)。管理员可以控制用户交互或通过网络登录。 |
A user has requested a type of logon (e.g., interactive or network) that has not been granted. An administrator has control over who may logon interactively and through the network. |
| 0xC000015C | 系统试图在注册表中加载或还原文件，而指定的文件不具有注册表文件的格式。 |
The system has attempted to load or restore a file into the registry, and the specified file is not in the format of a registry file. |
| 0xC000015D | 试图更改安全性帐户管理器中的用户密码而未提供必须的 Windows 交叉加密密码。 |
An attempt was made to change a user password in the security account manager without providing the necessary Windows cross-encrypted password. |
| 0xC000015E | Windows Server 的配置不正确。 |
A Windows Server has an incorrect configuration. |
| 0xC000015F | 试图通过设备控制直接访问容错驱动程序的次要信息副本，而该副本不在系统中。 |
An attempt was made to explicitly access the secondary copy of information via a device control to the Fault Tolerance driver and the secondary copy is not present in the system. |
| 0xC0000160 | 配置注册表节点显示一驱动程序服务项目类型不正确，且未包含必须的项目值。 |
A configuration registry node representing a driver service entry was ill-formed and did not contain required value entries. |
| 0xC0000161 | 出现无效字符。多字节字符集必须包含一前导字节且无结尾字节。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. |
| 0xC0000162 | 在多字节的目标代码页中，没有此 Unicode 字符可以映射到的字符。 |
No mapping for the Unicode character exists in the target multi-byte code page. |
| 0xC0000163 | 此 Unicode 字符没有在系统安装的 Unicode 字符集中定义。 |
The Unicode character is not defined in the Unicode character set installed on the system. |
| 0xC0000164 | 不能在软盘上创建页面文件。 |
The paging file cannot be created on a floppy diskette. |
| 0xC0000165 | {软盘错误}访问软盘时无法找到 ID 地址标记。 |
{Floppy Disk Error}While accessing a floppy disk, an ID address mark was not found. |
| 0xC0000166 | {软盘错误}访问软盘时扇区 ID 的磁道地址不同于控制器上所记录的磁道地址。 |
{Floppy Disk Error}While accessing a floppy disk, the track address from the sector ID field was found to be different than the track address maintained by the controller. |
| 0xC0000167 | {软盘错误}软盘控制器汇报了一个软盘驱动程序没有识别的错误。 |
{Floppy Disk Error}The floppy disk controller reported an error that is not recognized by the floppy disk driver. |
| 0xC0000168 | {软盘错误}访问软盘时，控制器通过其寄存器返回了不一致的结果。 |
{Floppy Disk Error}While accessing a floppy-disk, the controller returned inconsistent results via its registers. |
| 0xC0000169 | {硬盘错误}访问硬盘时，经过数次重试，重新校准操作还是没有成功。 |
{Hard Disk Error}While accessing the hard disk, a recalibrate operation failed, even after retries. |
| 0xC000016A | {硬盘错误}访问硬盘时，磁盘操作重试失败。 |
{Hard Disk Error}While accessing the hard disk, a disk operation failed even after retries. |
| 0xC000016B | {硬盘错误}访问硬盘时，磁盘控制器重置失败。 |
{Hard Disk Error}While accessing the hard disk, a disk controller reset was needed, but even that failed. |
| 0xC000016C | 试图打开一个与其他设备共享 IRQ 的设备。至少已打开一个使用该 IRQ 的其他设备。该设备所使用的特定总线类型不支持经由中断同时打开两个共享 IRQ 的设备。 |
An attempt was made to open a device that was sharing an IRQ with other devices.At least one other device that uses that IRQ was already opened.Two concurrent opens of devices that share an IRQ and only work via interrupts is not supported for the particular bus type that the devices use. |
| 0xC000016D | {FT 孤立}属于部分容错卷的磁盘无法访问。 |
{FT Orphaning}A disk that is part of a fault-tolerant volume can no longer be accessed. |
| 0xC000016E | 系统 BIOS 无法将系统中断连接到设备或该设备所连接的总线上。 |
The system bios failed to connect a system interrupt to the device or bus for which the device is connected. |
| 0xC0000172 | 磁带不能分区。 |
Tape could not be partitioned. |
| 0xC0000173 | 访问多卷分区的磁带时，当前块大小不正确。 |
When accessing a new tape of a multivolume partition, the current blocksize is incorrect. |
| 0xC0000174 | 在加载磁带时找不到磁带分区信息。 |
Tape partition information could not be found when loading a tape. |
| 0xC0000175 | 未能锁定弹出媒体机能。 |
Attempt to lock the eject media mechanism fails. |
| 0xC0000176 | 卸载媒体失败。 |
Unload media fails. |
| 0xC0000177 | 已检测到磁带尾端。 |
Physical end of tape was detected. |
| 0xC0000178 | {没有介质}驱动器中没有介质。请在驱动器 %hs 中插入介质。 |
{No Media}There is no media in the drive. Please insert media into drive %hs. |
| 0xC000017A | 该成员不存在，因此不能将其添加到本地组中或从本地组删除。 |
A member could not be added to or removed from the local group because the member does not exist. |
| 0xC000017B | 无法将新成员加入到本地组中，因为成员的帐户类型错误。 |
A new member could not be added to a local group because the member has the wrong account type. |
| 0xC000017C | 试图在已标记为删除的注册表项上运行无效的操作。 |
Illegal operation attempted on a registry key which has been marked for deletion. |
| 0xC000017D | 系统无法在注册表日志中分配所需空间。 |
System could not allocate required space in a registry log. |
| 0xC000017E | 指定的 Sid 太多。 |
Too many Sids have been specified. |
| 0xC000017F | 试图更改安全帐户管理器中的用户密码，但未提供必需的 LM 交互加密密码。 |
An attempt was made to change a user password in the security account manager without providing the necessary LM cross-encrypted password. |
| 0xC0000180 | 试图在一个已经有子项或数值的注册表项中创建符号链接。 |
An attempt was made to create a symbolic link in a registry key that already has subkeys or values. |
| 0xC0000181 | 试图在不稳定的父项下创建稳定的子项。 |
An attempt was made to create a Stable subkey under a Volatile parent key. |
| 0xC0000182 | I/O 设备的设置不正确或驱动程序的配置参数不正确。 |
The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect. |
| 0xC0000183 | 在两项驱动程序间或一项 I/O 驱动程序内检测到协议错误。 |
An error was detected between two drivers or within an I/O driver. |
| 0xC0000184 | 设备未处于运行本请求的有效状态。 |
The device is not in a valid state to perform this request. |
| 0xC0000185 | I/O 设备汇报了一个 I/O 错误。 |
The I/O device reported an I/O error. |
| 0xC0000186 | 在驱动程序与设备间检测到协议错误。 |
A protocol error was detected between the driver and the device. |
| 0xC0000188 | 日志文件空间不够，无法支持该操作。 |
Log file space is insufficient to support this operation. |
| 0xC0000189 | 在卸载卷后尝试对其进行写操作。 |
A write operation was attempted to a volume after it was dismounted. |
| 0xC000018A | 工作站在本地 LSA 数据库中没有主要域的信任机密。 |
The workstation does not have a trust secret for the primary domain in the local LSA database. |
| 0xC000018B | 在 Windows Server 上的 SAM 数据库没有该工作站信任关系的计算机帐户。 |
The SAM database on the Windows Server does not have a computer account for this workstation trust relationship. |
| 0xC000018C | 因主要域与受信任域间的信任关系失败而导致请求失败。 |
The logon request failed because the trust relationship between the primary domain and the trusted domain failed. |
| 0xC000018D | 因工作站与主要域间的信任关系失败而导致请求失败。 |
The logon request failed because the trust relationship between this workstation and the primary domain failed. |
| 0xC000018E | Eventlog 日志文件已损坏。 |
The Eventlog log file is corrupt. |
| 0xC000018F | 无法打开事件日志文件。事件日志服务未启动。 |
No Eventlog log file could be opened. The Eventlog service did not start. |
| 0xC0000190 | 网络登录失败。原因可能是无法获得验证权限。 |
The network logon failed. This may be because the validation authority can't be reached. |
| 0xC0000191 | 试图获得一个突变体，以致超过了其最大计数。 |
An attempt was made to acquire a mutant such that its maximum count would have been exceeded. |
| 0xC0000192 | 试图登录，但尚未启动 netlogon 服务。 |
An attempt was made to logon, but the netlogon service was not started. |
| 0xC0000193 | 用户帐户已过期。 |
The user's account has expired. |
| 0xC0000194 | {异常}可能的死锁条件。 |
{EXCEPTION}Possible deadlock condition. |
| 0xC0000195 | 不允许一个用户使用一个以上用户名与服务器或共享资源的多重连接。中断与此服务器或共享资源的所有连接，然后再试一次。 |
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. |
| 0xC0000196 | 试图与网络服务器建立会话，但目前与该服务器建立的会话太多。 |
An attempt was made to establish a session to a network server, but there are already too many sessions established to that server. |
| 0xC0000197 | 在读取过程之间更改了日志文件。 |
The log file has changed between reads. |
| 0xC0000198 | 所使用的帐户为域间信任帐户。请使用你的全局用户帐户或本地用户帐户以访问本服务器。 |
The account used is an Interdomain Trust account. Use your global user account or local user account to access this server. |
| 0xC0000199 | 所用的帐户是计算机帐户。请使用全局用户帐户或本地用户帐户访问该服务器。 |
The account used is a Computer Account. Use your global user account or local user account to access this server. |
| 0xC000019A | 所使用的帐户为服务器信任帐户。请使用你的全局用户帐户或本地用户帐户以访问本服务器。 |
The account used is an Server Trust account. Use your global user account or local user account to access this server. |
| 0xC000019B | 指定域的名称 或 SID 与该域的信任信息不一致。 |
The name or SID of the domain specified is inconsistent with the trust information for that domain. |
| 0xC000019C | 磁盘卷已经因为一个必须要但尚未加载的文件系统驱动程序而被访问。 |
A volume has been accessed for which a file system driver is required that has not yet been loaded. |
| 0xC000019D | 表明指定的映像已作为 DLL 加载。 |
Indicates that the specified image is already loaded as a DLL. |
| 0xC000019E | 由于全局注册表设置，在此卷上不能更改短名称设置。 |
Short name settings may not be changed on this volume due to the global registry setting. |
| 0xC000019F | 未在此卷上启用短名称。 |
Short names are not enabled on this volume. |
| 0xC00001A0 | 给定卷的安全流处于不一致状态。请在此卷上运行 CHKDSK。 |
The security stream for the given volume is in an inconsistent state.Please run CHKDSK on the volume. |
| 0xC00001A1 | 由于字节范围无效，无法处理请求的文件锁定操作。 |
A requested file lock operation cannot be processed due to an invalid byte range. |
| 0xC00001A2 | {ACE 条件无效}指定的访问控制项(ACE)包含无效的条件。 |
{Invalid ACE Condition}The specified access control entry (ACE) contains an invalid condition. |
| 0xC00001A3 | 支持此映像类型所需的子系统不存在。 |
The subsystem needed to support the image type is not present. |
| 0xC00001A4 | {无效的 ACE 条件}指定的文件已存在与之关联的 GUID 通知。 |
{Invalid ACE Condition}The specified file already has a notification GUID associated with it. |
| 0xC00001A5 | 检测到无效的异常处理程序例程。 |
An invalid exception handler routine has been detected. |
| 0xC00001A6 | 已经为该令牌指定了重复权限。 |
Duplicate privileges were specified for the token. |
| 0xC00001A7 | 不允许在文件系统的内部文件上执行请求的操作。 |
Requested action not allowed on a file system internal file. |
| 0xC00001A8 | 部分文件系统需要修复。 |
A portion of the file system requires repair. |
| 0xC00001A9 | 系统上未启用配额支持。 |
Quota support is not enabled on the system. |
| 0xC00001AA | 操作失败，因为该应用程序不是应用程序包的一部分。 |
The operation failed because the application is not part of an application package. |
| 0xC00001AB | 文件元数据优化已在进行中。 |
File metadata optimization is already in progress. |
| 0xC00001AC | 对象不同。 |
The objects are not identical. |
| 0xC00001AD | 该进程已终止，因为它无法分配更多的内存。 |
The process has terminated because it could not allocate additional memory. |
| 0xC00001AE | 该进程不是作业的一部分。 |
The process is not part of a job. |
| 0xC00001AF | 指定的 CPU 设置 ID 无效。 |
The specified CPU Set IDs are invalid. |
| 0xC0000201 | 由于未满足网络打开限制，远程打开操作失败。 |
A remote open failed because the network open restrictions were not satisfied. |
| 0xC0000202 | 没有指定登录会话的用户会话密钥。 |
There is no user session key for the specified logon session. |
| 0xC0000203 | 已删除远程用户会话。 |
The remote user session has been deleted. |
| 0xC0000204 | 指出在映像文件中找不到指定的 资源语言 ID。 |
Indicates the specified resource language ID cannot be found in theimage file. |
| 0xC0000205 | 服务器资源不足，无法完成请求。 |
Insufficient server resources exist to complete the request. |
| 0xC0000206 | 指定操作的缓冲区大小无效。 |
The size of the buffer is invalid for the specified operation. |
| 0xC0000207 | 传输拒绝指定的无效网络地址。 |
The transport rejected the network address specified as invalid. |
| 0xC0000208 | 传输因无效通配符使用而拒绝所指定的网络地址。 |
The transport rejected the network address specified due to an invalid use of a wildcard. |
| 0xC0000209 | 因所有的可用地址已在使用中而无法打开传输地址。 |
The transport address could not be opened because all the available addresses are in use. |
| 0xC000020A | 无法打开已存在的传输地址。 |
The transport address could not be opened because it already exists. |
| 0xC000020B | 已关闭传输地址。 |
The transport address is now closed. |
| 0xC000020C | 已断开传输连接。 |
The transport connection is now disconnected. |
| 0xC000020D | 已重置传输连接。 |
The transport connection has been reset. |
| 0xC000020E | 传输无法动态取得更多的节点。 |
The transport cannot dynamically acquire any more nodes. |
| 0xC000020F | 传输终止了一个没有完成的事务。 |
The transport aborted a pending transaction. |
| 0xC0000210 | 传输已使等待响应的请求超时。 |
The transport timed out a request waiting for a response. |
| 0xC0000211 | 传输未接收到挂起响应的释放。 |
The transport did not receive a release for a pending response. |
| 0xC0000212 | 传输未找到与特定令牌匹配的事务。 |
The transport did not find a transaction matching the specific token. |
| 0xC0000213 | 传输先前已响应一事务处理请求。 |
The transport had previously responded to a transaction request. |
| 0xC0000214 | 传输无法识别指定的事务处理请求标识符。 |
The transport does not recognized the transaction request identifier specified. |
| 0xC0000215 | 传输无法识别指定的事务处理请求类型。 |
The transport does not recognize the transaction request type specified. |
| 0xC0000216 | 传输仅能处理会话的服务器端所指定的请求。 |
The transport can only process the specified request on the server side of a session. |
| 0xC0000217 | 传输仅能处理会话的客户端所指定的请求。 |
The transport can only process the specified request on the client side of a session. |
| 0xC0000218 | {注册表文件失败}注册表无法加载配置单元(文件):%hs或它的日志或替代数据。可能已经损坏、不存在或是无法写入。 |
{Registry File Failure}The registry cannot load the hive (file):%hsor its log or alternate.It is corrupt, absent, or not writable. |
| 0xC0000219 | {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. |
| 0xC000021A | {致命系统错误}%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. |
| 0xC000021B | {无法接受数据}TDI 客户端无法在指示的时间内处理接收的数据。 |
{Data Not Accepted}The TDI client could not handle the data received during an indication. |
| 0xC000021C | {无法检索浏览服务器列表}工作组的服务器列表目前不可用。 |
{Unable to Retrieve Browser Server List}The list of servers for this workgroup is not currently available. |
| 0xC000021D | NTVDM 遇到一个硬错误。 |
NTVDM encountered a hard error. |
| 0xC000021E | {取消超时值}驱动程序 %hs 无法在指定的时间内完成一个已取消的 I/O 请求。 |
{Cancel Timeout}The driver %hs failed to complete a cancelled I/O request in the allotted time. |
| 0xC000021F | {应答消息不匹配}试图应答 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. |
| 0xC0000220 | {映射查看定位不正确}试图映射一文件的查看，但所指定的基址或文件的偏移地址无法在适当的分配间距上对齐。 |
{Mapped View Alignment Incorrect}An attempt was made to map a view of a file, but either the specified base address or the offset into the file were not aligned on the proper allocation granularity. |
| 0xC0000221 | {映像校验和不正确}映像 %hs 可能已损坏。标头的校验和与所计算的校验和不符。 |
{Bad Image Checksum}The image %hs is possibly corrupt. The header checksum does not match the computed checksum. |
| 0xC0000222 | {延缓写入失败}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. |
| 0xC0000223 | 发送给在客户端/服务器共享内存窗口中的服务器参数无效。共享内存窗口中放入过多的数据。 |
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. |
| 0xC0000224 | 在登录之前，必须更改用户的密码。 |
The user's password must be changed before signing in. |
| 0xC0000225 | 无法找到对象。 |
The object was not found. |
| 0xC0000226 | 此流不是小流。 |
The stream is not a tiny stream. |
| 0xC0000227 | 事务处理恢复失败。 |
A transaction recover failed. |
| 0xC0000228 | 本请求必须由堆栈溢出代码处理。 |
The request must be handled by the stack overflow code. |
| 0xC0000229 | 一致性检测失败。 |
A consistency check failed. |
| 0xC000022A | 因为该 ID 已在索引中，未能将其插入索引。 |
The attempt to insert the ID in the index failed because the ID is already in the index. |
| 0xC000022B | 因为已有 ID，未能设置对象 ID。 |
The attempt to set the object's ID failed because the object already has an ID. |
| 0xC000022C | 内部 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. |
| 0xC000022D | 必须重试本请求。 |
The request needs to be retried. |
| 0xC000022E | 在卷上找到一个 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. |
| 0xC000022F | 必须增加 bucket 数组。请运行后再重试事务处理。 |
The bucket array must be grown. Retry transaction after doing so. |
| 0xC0000230 | 在对象上不存在指定的属性集。 |
The property set specified does not exist on the object. |
| 0xC0000231 | 用户/内核排列缓冲区溢出。 |
The user/kernel marshalling buffer has overflowed. |
| 0xC0000232 | 提供的变量结构包含无效数据。 |
The supplied variant structure contains invalid data. |
| 0xC0000233 | 无法找到该域的域控制器。 |
Could not find a domain controller for this domain. |
| 0xC0000234 | 由于无效登录或要求更改密码的尝试次数过多，已自动锁定用户帐户。 |
The user account has been automatically locked because too many invalid logon attempts or password change attempts have been requested. |
| 0xC0000235 | 由句柄所调用的 NtClose 已使用 NtSetInformationObject 以防止关闭。 |
NtClose was called on a handle that was protected from close via NtSetInformationObject. |
| 0xC0000236 | 远程系统拒绝传输连接。 |
The transport connection attempt was refused by the remote system. |
| 0xC0000237 | 传输连接已正常关闭。 |
The transport connection was gracefully closed. |
| 0xC0000238 | 传输终结点已有与其相关的地址。 |
The transport endpoint already has an address associated with it. |
| 0xC0000239 | 尚未与传输终结点产生关联地址。 |
An address has not yet been associated with the transport endpoint. |
| 0xC000023A | 已尝试在不存在的传输连接上进行操作。 |
An operation was attempted on a nonexistent transport connection. |
| 0xC000023B | 试图在活动传输连接上运行无效的操作。 |
An invalid operation was attempted on an active transport connection. |
| 0xC000023C | 无法通过传输连接远程网络。 |
The remote network is not reachable by the transport. |
| 0xC000023D | 无法通过传输访问远程系统。 |
The remote system is not reachable by the transport. |
| 0xC000023E | 远程系统不支持传输协议。 |
The remote system does not support the transport protocol. |
| 0xC000023F | 在远程系统的传输目标端口上未运行任何的服务。 |
No service is operating at the destination port of the transport on the remote system. |
| 0xC0000240 | 请求被中止。 |
The request was aborted. |
| 0xC0000241 | 本地系统已终止传输连接。 |
The transport connection was aborted by the local system. |
| 0xC0000242 | 指定的缓冲区中包含类型错误的数据。 |
The specified buffer contains ill-formed data. |
| 0xC0000243 | 请求的操作不能在用户映射区打开的文件上执行。 |
The requested operation cannot be performed on a file with a user mapped section open. |
| 0xC0000244 | {审核失败}未能生成安全审核。 |
{Audit Failed}An attempt to generate a security audit failed. |
| 0xC0000245 | 当前的过程未设置计时器分辨率。 |
The timer resolution was not previously set by the current process. |
| 0xC0000246 | 因为已达到此帐户的最大同时连接数限制，所以无法连接服务器。 |
A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached. |
| 0xC0000247 | 试图在本帐户的未授权时间内登录。 |
Attempting to login during an unauthorized time of day for this account. |
| 0xC0000248 | 该帐户不能从这个站点登录。 |
The account is not authorized to login from this station. |
| 0xC0000249 | {UP/MP 映像不匹配 }映像 %hs 已被修改为在单处理器系统上使用，但你正在多处理器系统上运行它。请重新安装映像文件。 |
{UP/MP Image Mismatch}The image %hs has been modified for use on a uniprocessor system, but you are running it on a multiprocessor machine.Please reinstall the image file. |
| 0xC0000250 | 帐户信息不足，无法登录。 |
There is insufficient account information to log you on. |
| 0xC0000251 | {无效的 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. |
| 0xC0000252 | {无效的服务回调入口点}%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. |
| 0xC0000253 | 服务器已收到消息，但是无法发送应答。 |
The server received the messages but did not send a reply. |
| 0xC0000254 | IP 地址与网络上的其他系统有冲突。 |
There is an IP address conflict with another system on the network |
| 0xC0000256 | {注册表空间不足}系统已达到注册表系统部分所允许的最大大小。将忽略附加存储请求。 |
{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. |
| 0xC0000257 | 联系到的服务器不支持指定的部分 DFS 命名空间。 |
The contacted server does not support the indicated part of the DFS namespace. |
| 0xC0000258 | 没有启动回调功能时，回调系统服务不能运行。 |
A callback return system service cannot be executed when no callback is active. |
| 0xC0000259 | 正在访问的服务受特定连接数目授权限制。此时无法对该服务进行更多数目的连接，原因是已达到该服务可接受的连接数目上限。 |
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. |
| 0xC000025A | 提供的密码太短，不符合用户帐户的策略。请选择一个较长的密码。 |
The password provided is too short to meet the policy of your user account. Please choose a longer password. |
| 0xC000025B | 你的用户帐户策略不允许你过于频繁更改密码。这样做可避免用户将密码更改回熟悉的、但可能被别人猜到的密码。如果你觉得密码已被别人知道，请立即与管理员联系以获得一个指定的新密码。 |
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. |
| 0xC000025C | 已尝试将密码更改为过去曾用过的密码。用户帐户的策略不允许这样做。请选择以前没有用过的密码。 |
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. |
| 0xC000025E | 你想加载旧型的设备驱动程序，但是设备范例已经被禁用了。 |
You have attempted to load a legacy device driver while its device instance had been disabled. |
| 0xC000025F | 不支持指定的压缩格式。 |
The specified compression format is unsupported. |
| 0xC0000260 | 指定的硬件配置文件配置无效。 |
The specified hardware profile configuration is invalid. |
| 0xC0000261 | 指定的即插即用注册表设备的路径无效。 |
The specified Plug and Play registry device path is invalid. |
| 0xC0000262 | {找不到驱动程序输入点}%hs 设备驱动程序找不到有序的 %ld (驱动程序 %hs 中)。 |
{Driver Entry Point Not Found}The %hs device driver could not locate the ordinal %ld in driver %hs. |
| 0xC0000263 | {驱动程序输入点找不到}%hs 设备驱动程序找不到输入点 %hs (驱动程序 %hs 中)。 |
{Driver Entry Point Not Found}The %hs device driver could not locate the entry point %hs in driver %hs. |
| 0xC0000264 | {应用程序错误}应用程序试图释放不属于自已的资源。请单击“确定”，终止应用程序。 |
{Application Error}The application attempted to release a resource it did not own. Click OK to terminate the application. |
| 0xC0000265 | 试图在文件上创建超过文件系统支持的链接数。 |
An attempt was made to create more links on a file than the file system supports. |
| 0xC0000266 | 指定的限额列表与其描述符不一致。 |
The specified quota list is internally inconsistent with its descriptor. |
| 0xC0000267 | 指定的文件已被重定位到脱机存储。 |
The specified file has been relocated to offline storage. |
| 0xC0000268 | {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. |
| 0xC0000269 | {无效的系统 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. |
| 0xC000026A | {许可证冲突}系统检测到你的注册的产品类型有篡改现象。这是对软件许可证的侵犯。篡改产品类型是不允许的。 |
{License Violation}The system has detected tampering with your registered product type. This is a violation of your software license. Tampering with product type is not permitted. |
| 0xC000026B | {DLL 初始化失败}因为窗口站已关闭，应用程序初始化失败。 |
{DLL Initialization Failed}The application failed to initialize because the window station is shutting down. |
| 0xC000026C | {无法加载设备驱动程序}%hs 设备驱动程序无法加载。错误状态是 0x%x |
{Unable to Load Device Driver}%hs device driver could not be loaded.Error Status was 0x%x |
| 0xC000026D | DFS 在联系的服务器上不可用。 |
DFS is unavailable on the contacted server. |
| 0xC000026E | 试图在卷被卸载后对其进行操作。 |
An operation was attempted to a volume after it was dismounted. |
| 0xC000026F | Win32 x86 仿真子系统中出现内部错误。 |
An internal error occurred in the Win32 x86 emulation subsystem. |
| 0xC0000270 | Win32 x86 仿真系统浮点栈检查。 |
Win32 x86 emulation subsystem Floating-point stack check. |
| 0xC0000271 | 验证过程需要进行到下一步。 |
The validation process needs to continue on to the next step. |
| 0xC0000272 | 索引中没有同指定项相匹配的项。 |
There was no match for the specified key in the index. |
| 0xC0000273 | 不再有与当前索引列举相匹配的项。 |
There are no more matches for the current index enumeration. |
| 0xC0000275 | NTFS 文件或目录不是重新分析点。 |
The NTFS file or directory is not a reparse point. |
| 0xC0000276 | 为 NTFS 重新分析点传递的 Windows I/O 重新分析标记无效。 |
The Windows I/O reparse tag passed for the NTFS reparse point is invalid. |
| 0xC0000277 | Windows I/O 重新分析标记与目前在 NTFS 中的重新分析点不匹配。 |
The Windows I/O reparse tag does not match the one present in the NTFS reparse point. |
| 0xC0000278 | 为 NTFS 重新分析点传递的用户数据无效。 |
The user data passed for the NTFS reparse point is invalid. |
| 0xC0000279 | 在需要处理 IO 标记时，这个 IO 标记的分层文件系统驱动程序并未处理它。 |
The layered file system driver for this IO tag did not handle it when needed. |
| 0xC000027A | 提供的密码太长，不符合用户帐户的策略。请选择一个较短的密码。 |
The password provided is too long to meet the policy of your user account. Please choose a shorter password. |
| 0xC000027B | 发生应用程序内部异常。 |
An application-internal exception has occurred. |
| 0xC0000280 | 虽然初始文件名正确，但无法辨认 NTFS 符号链接。 |
The NTFS symbolic link could not be resolved even though the initial file name is valid. |
| 0xC0000281 | NTFS 目录是一个重新分析点。 |
The NTFS directory is a reparse point. |
| 0xC0000282 | 由于冲突，无法将区域添加到区域列表。 |
The range could not be added to the range list because of a conflict. |
| 0xC0000283 | 指定的媒体更改源元素中不包含媒体。 |
The specified medium changer source element contains no media. |
| 0xC0000284 | 指定的媒体更改目标元素已经包含媒体。 |
The specified medium changer destination element already contains media. |
| 0xC0000285 | 指定的媒体更改元素不存在。 |
The specified medium changer element does not exist. |
| 0xC0000286 | 指定的元素在一个已不存在的库中。 |
The specified element is contained within a magazine that is no longer present. |
| 0xC0000287 | 由于硬件错误，设备需要重新初始化。 |
The device requires reinitialization due to hardware errors. |
| 0xC000028A | 文件加密失败。 |
The file encryption attempt failed. |
| 0xC000028B | 文件解密失败。 |
The file decryption attempt failed. |
| 0xC000028C | 在范围列表中找不到指定的范围。 |
The specified range could not be found in the range list. |
| 0xC000028D | 没有为这个系统配置的加密恢复策略。 |
There is no encryption recovery policy configured for this system. |
| 0xC000028E | 所需的加密驱动程序并未加载到系统中。 |
The required encryption driver is not loaded for this system. |
| 0xC000028F | 文件加密所使用的加密驱动程序与目前加载的加密驱动程序不同。 |
The file was encrypted with a different encryption driver than is currently loaded. |
| 0xC0000290 | 没有为用户定义 EFS 关键字。 |
There are no EFS keys defined for the user. |
| 0xC0000291 | 指定的文件并未加密。 |
The specified file is not encrypted. |
| 0xC0000292 | 指定的文件不是定义的 EFS 导出格式。 |
The specified file is not in the defined EFS export format. |
| 0xC0000293 | 指定的文件已加密，而且用户没有能力解密。 |
The specified file is encrypted and the user does not have the ability to decrypt it. |
| 0xC0000295 | 无法识别传来的 GUID 是否为有效的 WMI 数据提供程序。 |
The guid passed was not recognized as valid by a WMI data provider. |
| 0xC0000296 | 无法识别传来的实例名是否为有效的 WMI 数据提供程序。 |
The instance name passed was not recognized as valid by a WMI data provider. |
| 0xC0000297 | WMI 数据提供程序不认为传递的数据项 id 是有效的。 |
The data item id passed was not recognized as valid by a WMI data provider. |
| 0xC0000298 | 无法完成 WMI 请求，应该重试一次。 |
The WMI request could not be completed and should be retried. |
| 0xC0000299 | 策略对象已共享，而且只能在根目录修改 |
The policy object is shared and can only be modified at the root |
| 0xC000029A | 策略对象不存在，它应该存在才对 |
The policy object does not exist when it should |
| 0xC000029B | 要求的策略信息只在 DS 中 |
The requested policy information only lives in the Ds |
| 0xC000029C | 卷必须通过升级，才可启用这个功能 |
The volume must be upgraded to enable this feature |
| 0xC000029D | 远程存储服务此时不可操作。 |
The remote storage service is not operational at this time. |
| 0xC000029E | 远程存储服务遇到一个媒体错误。 |
The remote storage service encountered a media error. |
| 0xC000029F | 跟踪(工作站)服务没有运行。 |
The tracking (workstation) service is not running. |
| 0xC00002A0 | 服务器进程运行的 SID 跟客户端要求的不同。 |
The server process is running under a SID different than that required by client. |
| 0xC00002A1 | 指定的目录服务属性或值不存在。 |
The specified directory service attribute or value does not exist. |
| 0xC00002A2 | 指定给目录服务的属性语法无效。 |
The attribute syntax specified to the directory service is invalid. |
| 0xC00002A3 | 指定给目录服务的属性类型未定义。 |
The attribute type specified to the directory service is not defined. |
| 0xC00002A4 | 指定的目录服务属性或值已经存在。 |
The specified directory service attribute or value already exists. |
| 0xC00002A5 | 目录服务忙。 |
The directory service is busy. |
| 0xC00002A6 | 目录服务不可用。 |
The directory service is not available. |
| 0xC00002A7 | 目录服务无法分配相对标识符。 |
The directory service was unable to allocate a relative identifier. |
| 0xC00002A8 | 目录服务已经用完了相对标识符池。 |
The directory service has exhausted the pool of relative identifiers. |
| 0xC00002A9 | 由于目录服务不是该类操作的主控，未能执行操作。 |
The requested operation could not be performed because the directory service is not the master for that type of operation. |
| 0xC00002AA | 目录服务无法初始化分配相对标识符的子系统。 |
The directory service was unable to initialize the subsystem that allocates relative identifiers. |
| 0xC00002AB | 该请求的操作没有满足一个或多个与该对象的类别相关的约束。 |
The requested operation did not satisfy one or more constraints associated with the class of the object. |
| 0xC00002AC | 目录服务只可以在一个页状对象上运行要求的操作。 |
The directory service can perform the requested operation only on a leaf object. |
| 0xC00002AD | 目录服务无法在对象的相对定义的名称(RDN)属性上运行要求的操作。 |
The directory service cannot perform the requested operation on the Relatively Defined Name (RDN) attribute of an object. |
| 0xC00002AE | 目录服务检测出修改对象类别的尝试。 |
The directory service detected an attempt to modify the object class of an object. |
| 0xC00002AF | 执行跨域移动操作时，发生了一个错误。 |
An error occurred while performing a cross domain move operation. |
| 0xC00002B0 | 无法与全局编录服务器联系。 |
Unable to Contact the Global Catalog Server. |
| 0xC00002B1 | 要求的操作需要一个目录服务，但没有可用的。 |
The requested operation requires a directory service, and none was available. |
| 0xC00002B2 | 因与一个现存属性不相容，重新分列属性无法设置。 |
The reparse attribute cannot be set as it is incompatible with an existing attribute. |
| 0xC00002B3 | 不能启用标为“只用于否定”的组。 |
A group marked use for deny only cannot be enabled. |
| 0xC00002B4 | {异常}多浮点错。 |
{EXCEPTION}Multiple floating point faults. |
| 0xC00002B5 | {异常}多浮点陷阱。 |
{EXCEPTION}Multiple floating point traps. |
| 0xC00002B6 | 设备已被删除。 |
The device has been removed. |
| 0xC00002B7 | 正在删除卷更改日志。 |
The volume change journal is being deleted. |
| 0xC00002B8 | 卷更改日志处于非活动状态。 |
The volume change journal is not active. |
| 0xC00002B9 | 不支持所请求的接口。 |
The requested interface is not supported. |
| 0xC00002BA | 目录服务检测到用于分配相对标识符的子系统被禁用。这是系统在确定相对标识符(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. |
| 0xC00002C1 | 超过了目录服务资源限制。 |
A directory service resource limit has been exceeded. |
| 0xC00002C2 | {系统待机失败}驱动程序 %hs 不支持待机模式。更新这个驱动程序会允许系统进入待机模式。 |
{System Standby Failed}The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode. |
| 0xC00002C3 | 相互身份验证失败。该服务器在域控制器的密码过期。 |
Mutual Authentication failed. The server's password is out of date at the domain controller. |
| 0xC00002C4 | 系统文件 %1 已损坏而且已经被替换。 |
The system file %1 has become corrupt and has been replaced. |
| 0xC00002C5 | {异常}定位错误在加载或存储指令中检测到一个数据类型定位错误。 |
{EXCEPTION}Alignment ErrorA datatype misalignment error was detected in a load or store instruction. |
| 0xC00002C6 | WMI 数据项目或数据块为只读。 |
The WMI data item or data block is read only. |
| 0xC00002C7 | 不能更改 WMI 数据项目或数据块。 |
The WMI data item or data block could not be changed. |
| 0xC00002C8 | {虚拟内存最小值太低}系统虚拟内存太低。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. |
| 0xC00002C9 | {异常}寄存器 NaT 消耗错误。NaT 数值在一个非推理指令中消耗。 |
{EXCEPTION}Register NaT consumption faults.A NaT value is consumed on a non speculative instruction. |
| 0xC00002CA | 媒体更换器的传输元素中包含使操作失败的媒体。 |
The medium changer's transport element contains media, which is causing the operation to fail. |
| 0xC00002CB | 安全帐户管理器初始化失败，原因是发生了以下错误:%hs错误状态: 0x%x。请关闭此系统，并重新启动到目录服务还原模式。有关详细信息，请查看事件日志。 |
Security Accounts Manager initialization failed because of the following error:%hsError Status: 0x%x.Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. |
| 0xC00002CC | 只有连接到服务器上时，该操作才受支持。 |
This operation is supported only when you are connected to the server. |
| 0xC00002CD | 只有管理员才能修改管理组的成员列表。 |
Only an administrator can modify the membership list of an administrative group. |
| 0xC00002CE | 删除了一个设备，因此必须重新启动枚举。 |
A device was removed so enumeration must be restarted. |
| 0xC00002CF | 日志项已从日志中被删除。 |
The journal entry has been deleted from the journal. |
| 0xC00002D0 | 不能更改域控制器帐户的主要组 ID。 |
Cannot change the primary group ID of a domain controller account. |
| 0xC00002D1 | {严重系统错误}系统映像 %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. |
| 0xC00002D2 | 不重新启动计算机，设备不会开始运行。 |
Device will not start without a reboot. |
| 0xC00002D3 | 当前设备电源状态不能支持这个请求。 |
Current device power state cannot support this request. |
| 0xC00002D4 | 指定的组类型无效。 |
The specified group type is invalid. |
| 0xC00002D5 | 在混合型域中，如果是启用安全的组，则没有全局组的嵌套。 |
In mixed domain no nesting of global group if group is security enabled. |
| 0xC00002D6 | 在混合型域中，如果是启用安全的组，则无法用其它本地组来嵌套本地组。 |
In mixed domain, cannot nest local groups with other local groups, if the group is security enabled. |
| 0xC00002D7 | 全局组不能将本地组作为成员。 |
A global group cannot have a local group as a member. |
| 0xC00002D8 | 全局组不能将通用组作为成员。 |
A global group cannot have a universal group as a member. |
| 0xC00002D9 | 通用组不能将本地组作为成员。 |
A universal group cannot have a local group as a member. |
| 0xC00002DA | 全局组不能有跨域成员。 |
A global group cannot have a cross domain member. |
| 0xC00002DB | 本地组不能将另一个跨域本地组作为成员。 |
A local group cannot have another cross domain local group as a member. |
| 0xC00002DC | 因为这个组中有主要成员，所以不能更改为禁用安全的组。 |
Cannot change to security disabled group because of having primary members in this group. |
| 0xC00002DD | 数据区块或方法不支持 WMI 操作。 |
The WMI operation is not supported by the data block or method. |
| 0xC00002DE | 电源不足，无法完成要求的操作。 |
There is not enough power to complete the requested operation. |
| 0xC00002DF | 安全帐户管理员需要获得启动密码。 |
Security Account Manager needs to get the boot password. |
| 0xC00002E0 | 安全帐户管理员需要从软盘获得启动密钥。 |
Security Account Manager needs to get the boot key from floppy disk. |
| 0xC00002E1 | 目录服务无法启动。 |
Directory Service cannot start. |
| 0xC00002E2 | 目录服务无法启动，原因是发生了以下错误:%hs错误状态: 0x%x。请关闭此系统，并重新启动到目录服务还原模式。有关详细信息，请查看事件日志。 |
Directory Services could not start because of the following error:%hsError Status: 0x%x.Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. |
| 0xC00002E3 | 安全帐户管理器初始化失败，原因是以下错误:%hs错误状态: 0x%x。请单击“确定”，关闭这个系统并重新启动到安全模式中。有关详细信息，请查阅事件日志。 |
Security Accounts Manager initialization failed because of the following error:%hsError Status: 0x%x.Please click OK to shutdown this system and reboot into Safe Mode, check the event log for more detailed information. |
| 0xC00002E4 | 只能在全局编录服务器上执行请求的操作。 |
The requested operation can be performed only on a global catalog server. |
| 0xC00002E5 | 本地组只能是同一个域中其他本地组的成员。 |
A local group can only be a member of other local groups in the same domain. |
| 0xC00002E6 | 外部安全主体不能是通用组的成员。 |
Foreign security principals cannot be members of universal groups. |
| 0xC00002E7 | 你的计算机无法加入域。已超出此域所允许创建的计算机帐户的最大值。请跟系统管理员联系，以便重置或增加此限制。 |
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. |
| 0xC00002E8 | STATUS_MULTIPLE_FAULT_VIOLATION |
STATUS_MULTIPLE_FAULT_VIOLATION |
| 0xC00002E9 | 无法在当前域上执行此操作。 |
This operation cannot be performed on the current domain. |
| 0xC00002EA | 无法创建目录或文件。 |
The directory or file cannot be created. |
| 0xC00002EB | 系统正在关机。 |
The system is in the process of shutting down. |
| 0xC00002EC | 由于下列原因，目录服务无法启动:%hs错误状态: 0x%x.请单击“确定”关闭系统。你可使用恢复控制台对系统进行进一步的诊断。 |
Directory Services could not start because of the following error:%hsError Status: 0x%x.Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0xC00002ED | 由于下列原因，安全帐户管理器初始化失败:%hs错误状态: 0x%x.请单击“确定”关闭系统。你可使用恢复控制台对系统进行进一步的诊断。 |
Security Accounts Manager initialization failed because of the following error:%hsError Status: 0x%x.Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0xC00002EE | 在上下文完成之前，已删除安全性上下文。这被认为是登录失败。 |
A security context was deleted before the context was completed. This is considered a logon failure. |
| 0xC00002EF | 客户端正在协商上下文。服务器要求用户对用户，但没有发送 TGT 应答。 |
The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply. |
| 0xC00002F0 | 文件中没有找到对象 ID。 |
An object ID was not found in the file. |
| 0xC00002F1 | 由于本地计算机没有任何 IP 地址，无法完成请求的任务。 |
Unable to accomplish the requested task because the local machine does not have any IP addresses. |
| 0xC00002F2 | 提供的凭据句柄同与安全上下文相关联的凭据不匹配。 |
The supplied credential handle does not match the credential associated with the security context. |
| 0xC00002F3 | 由于要求的程序不可用，加密系统或校验和函数无效。 |
The crypto system or checksum function is invalid because a required function is unavailable. |
| 0xC00002F4 | 超出了最大票证参照数。 |
The number of maximum ticket referrals has been exceeded. |
| 0xC00002F5 | 本地计算机必须是 Kerberos KDC (域控制器)；而它不是。 |
The local machine must be a Kerberos KDC (domain controller) and it is not. |
| 0xC00002F6 | 安全协商的另一端要求较强的加密，但本地计算机不支持。 |
The other end of the security negotiation is requires strong crypto but it is not supported on the local machine. |
| 0xC00002F7 | KDC 应答包含不止一个主要名称。 |
The KDC reply contained more than one principal name. |
| 0xC00002F8 | 应能在 PA 数据中找到使用的 etype 类型的信息，但找不到。 |
Expected to find PA data for a hint of what etype to use, but it was not found. |
| 0xC00002F9 | 客户端证书不包含有效的 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. |
| 0xC00002FA | 要求智能卡登录，但没有使用。 |
Smartcard logon is required and was not used. |
| 0xC00002FB | 向 KDC 发送了无效的请求。 |
An invalid request was sent to the KDC. |
| 0xC00002FC | KDC 无法为要求的服务生成参照。 |
The KDC was unable to generate a referral for the service requested. |
| 0xC00002FD | KDC 不支持请求的加密类型。 |
The encryption type requested is not supported by the KDC. |
| 0xC00002FF | 服务器正在关机。 |
The server machine is shutting down. |
| 0xC0000300 | 运行 Windows Server 2003 for Small Business Server 的计算机不支持此操作。 |
This operation is not supported on a computer running Windows Server 2003 for Small Business Server |
| 0xC0000301 | WMI GUID 不可用 |
The WMI GUID is no longer available |
| 0xC0000302 | WMI GUID 的集合或事件已禁用。 |
Collection or events for the WMI GUID is already disabled. |
| 0xC0000303 | WMI GUID 的集合或事件已启用。 |
Collection or events for the WMI GUID is already enabled. |
| 0xC0000304 | 卷上的主文件表太零碎，无法完成操作。 |
The Master File Table on the volume is too fragmented to complete this operation. |
| 0xC0000305 | 复制保护失败。 |
Copy protection failure. |
| 0xC0000306 | 复制保护错误 - DVD CSS 身份验证失败。 |
Copy protection error - DVD CSS Authentication failed. |
| 0xC0000307 | 复制保护错误 - 给定的扇区没有有效的密钥。 |
Copy protection error - The given sector does not contain a valid key. |
| 0xC0000308 | 复制保护错误 - 没有建立 DVD 会话密钥。 |
Copy protection error - DVD session key not established. |
| 0xC0000309 | 复制保护错误 - 由于扇区加密，读取失败。 |
Copy protection error - The read failed because the sector is encrypted. |
| 0xC000030A | 复制保护错误 - 给定的 DVD 的区域同驱动器的区域设置不对应。 |
Copy protection error - The given DVD's region does not correspond to theregion setting of the drive. |
| 0xC000030B | 复制保护错误 - 驱动器的区域设置是永久的。 |
Copy protection error - The drive's region setting may be permanent. |
| 0xC000030C | EAS 策略需要用户先更改密码才能执行此操作。 |
EAS policy requires that the user change their password before this operation can be performed. |
| 0xC000030D | 管理员已限制登录。若要登录，请确保设备已连接到 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. |
| 0xC0000320 | 在登录过程中，验证 KDC 证书时，Kerberos 协议遇到错误。系统事件日志中包含详细信息。 |
The Kerberos protocol encountered an error while validating the KDC certificate during logon. There is more information in the system event log. |
| 0xC0000321 | 尝试使用智能卡子系统时，Kerberos 协议遇到错误。 |
The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem. |
| 0xC0000322 | 目标服务器没有可接受的 Kerberos 凭据。 |
The target server does not have acceptable Kerberos credentials. |
| 0xC0000350 | 传输确定远端系统已关机。 |
The transport determined that the remote system is down. |
| 0xC0000351 | Kerberos 包中存在不受支持的预身份验证机制。 |
An unsupported preauthentication mechanism was presented to the Kerberos package. |
| 0xC0000352 | 源文件所使用的加密算法所使用的密钥缓冲区需要大于目标文件的密钥缓冲区。 |
The encryption algorithm used on the source file needs a bigger key buffer than the one used on the destination file. |
| 0xC0000353 | 试图删除进程的 DebugPort，但端口没有同此进程相关联。 |
An attempt to remove a process's DebugPort was made, but a port was not already associated with the process. |
| 0xC0000354 | 调试程序处于非活动状态: Windows 可能在没有启用内核调试的情况下启动。 |
Debugger Inactive: Windows may have been started without kernel debugging enabled. |
| 0xC0000355 | 这一版本的 Windows 与目录林、域或域控制器的版本不兼容。 |
This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller. |
| 0xC0000356 | 当前没有审核指定的事件。 |
The specified event is currently not being audited. |
| 0xC0000357 | 计算机帐户是由 NT4 之前的版本创建的。需要重新创建该帐户。 |
The machine account was created pre-NT4. The account needs to be recreated. |
| 0xC0000358 | 帐户组无法将通用组作为成员。 |
A account group cannot have a universal group as a member. |
| 0xC0000359 | 指定的映像文件没有正确的格式，似乎是 32 位的 Windows 映像。 |
The specified image file did not have the correct format, it appears to be a 32-bit Windows image. |
| 0xC000035A | 指定的映像文件没有正确的格式，似乎是 64 位的 Windows 映像。 |
The specified image file did not have the correct format, it appears to be a 64-bit Windows image. |
| 0xC000035B | 客户端提供的 SSPI 通道绑定不正确。 |
Client's supplied SSPI channel bindings were incorrect. |
| 0xC000035C | 客户端的会话已过期。客户端必须重新进行身份验证以继续访问远端资源。 |
The client's session has expired, so the client must reauthenticate to continue accessing the remote resources. |
| 0xC000035D | 取消了 AppHelp 对话，导致应用程序无法启动。 |
AppHelp dialog canceled thus preventing the application from starting. |
| 0xC000035E | SID 筛选操作删除了所有 SID。 |
The SID filtering operation removed all SIDs. |
| 0xC000035F | 系统正在以安全模式启动，因此没有加载驱动程序。 |
The driver was not loaded because the system is booting into safe mode. |
| 0xC0000361 | 管理员用默认的软件限制策略级别限制了对 %1 的访问。 |
Access to %1 has been restricted by your Administrator by the default software restriction policy level. |
| 0xC0000362 | 对 %1 的访问被你的管理员根据位置用路径 %3 上的策略规则 %2 限制了 |
Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3 |
| 0xC0000363 | 管理员用软件发布者策略限制了对 %1 的访问。 |
Access to %1 has been restricted by your Administrator by software publisher policy. |
| 0xC0000364 | 管理员用策略规则 %2 限制了对 %1 的访问。 |
Access to %1 has been restricted by your Administrator by policy rule %2. |
| 0xC0000365 | 由于初始化调用失败，驱动程序无法加载。 |
The driver was not loaded because it failed its initialization call. |
| 0xC0000366 | “%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. |
| 0xC0000368 | 创建操作失败，因为名称含有至少一个装入点，它引起生成的卷没有同指定的设备对象连接上。 |
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. |
| 0xC0000369 | 设备对象参数不是有效的设备对象，或者没有附到文件名指定的卷。 |
The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. |
| 0xC000036A | 发生计算机检查错误。有关额外信息，请查阅系统事件日志。 |
A Machine Check Error has occurred. Please check the system eventlog for additional information. |
| 0xC000036B | 阻止加载驱动程序 %2。 |
Driver %2 has been blocked from loading. |
| 0xC000036D | 处理驱动程序数据库时发生错误 [%2]。 |
There was error [%2] processing the driver database. |
| 0xC000036E | 系统配置单元大小已超出限制。 |
System hive size has exceeded its limit. |
| 0xC000036F | 动态链接库(DLL)引用的模块不是 DLL 也不是过程可执行映像。 |
A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image. |
| 0xC0000371 | 本地帐户存储不包含指定帐户的秘密材料。 |
The local account store does not contain secret material for the specified account. |
| 0xC0000373 | 系统无法分配足够内存来执行堆栈切换。 |
The system was not able to allocate enough memory to perform a stack switch. |
| 0xC0000374 | 堆已损坏。 |
A heap has been corrupted. |
| 0xC0000380 | 向智能卡提交了一个错误的 PIN |
An incorrect PIN was presented to the smart card |
| 0xC0000381 | 智能卡被阻止 |
The smart card is blocked |
| 0xC0000382 | 没有向智能卡提交 PIN |
No PIN was presented to the smart card |
| 0xC0000383 | 无智能卡 |
No smart card available |
| 0xC0000384 | 智能卡上不存在请求的密钥容器 |
The requested key container does not exist on the smart card |
| 0xC0000385 | 智能卡上不存在请求的证书 |
The requested certificate does not exist on the smart card |
| 0xC0000386 | 请求的密钥集不存在 |
The requested keyset does not exist |
| 0xC0000387 | 检测到与智能卡通讯发生错误。 |
A communication error with the smart card has been detected. |
| 0xC0000388 | 系统无法联系域控制器来为身份验证请求提供服务。请稍后再试。 |
The system cannot contact a domain controller to service the authentication request. Please try again later. |
| 0xC0000389 | 用于身份验证的智能卡证书已经吊销。请与你的系统管理员联系。事件日志中可能有额外的信息。 |
The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log. |
| 0xC000038A | 在处理用于身份验证的证书时，检测到不受信任的证书颁发机构。 |
An untrusted certificate authority was detected while processing the certificate used for authentication. |
| 0xC000038B | 无法确定用于身份验证的证书的吊销状态。 |
The revocation status of the certificate used for authentication could not be determined. |
| 0xC000038C | 用于身份验证的客户端证书不受信任。 |
The client certificate used for authentication was not trusted. |
| 0xC000038D | 用于身份验证的智能卡证书已过期。请与系统管理员联系。 |
The smartcard certificate used for authentication has expired. Pleasecontact your system administrator. |
| 0xC000038E | 上一版本的驱动程序还在内存中，因此无法加载驱动程序。 |
The driver could not be loaded because a previous version of the driver is still in memory. |
| 0xC000038F | 因为获取的上下文是无声的，智能卡提供程序不能执行操作。 |
The smartcard provider could not perform the action since the context was acquired as silent. |
| 0xC0000401 | 已经超过当前用户的委派信任创建限额。 |
The current user's delegated trust creation quota has been exceeded. |
| 0xC0000402 | 已经超过委派信任创建限额的总数。 |
The total delegated trust creation quota has been exceeded. |
| 0xC0000403 | 已经超过当前用户的委派信任删除限额。 |
The current user's delegated trust deletion quota has been exceeded. |
| 0xC0000404 | 请求的名称是已经存在的唯一标识符。 |
The requested name already exists as a unique identifier. |
| 0xC0000405 | 请求的对象包含非唯一标识符而且无法检索。 |
The requested object has a non-unique identifier and cannot be retrieved. |
| 0xC0000406 | 由于请求的组类型上属性的限制，组不能被转换。 |
The group cannot be converted due to attribute restrictions on the requested group type. |
| 0xC0000407 | {卷影复制服务}卷影复制服务准备用于休眠的卷 %hs 时请稍候。 |
{Volume Shadow Copy Service}Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation. |
| 0xC0000408 | 要求 Kerberos 子协议 User2User。 |
Kerberos sub-protocol User2User is required. |
| 0xC0000409 | 系统在此应用程序中检测到基于堆栈的缓冲区溢出。溢出可能允许恶意用户获得此应用程序的控制。 |
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. |
| 0xC000040A | 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. |
| 0xC000040B | 此服务器已经尝试为服务器领域之外的目标进行 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. |
| 0xC000040C | 无法确定用于身份验证的域控制器证书的吊销状态。系统事件日志中有其他信息。 |
The revocation status of the domain controller certificate used for authentication could not be determined. There is additional information in the system event log. |
| 0xC000040D | 处理用于身份验证的域控制器证书时检测到不受信任的证书颁发机构。系统事件日志中有其他信息。请与系统管理员联系。 |
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. |
| 0xC000040E | 用于登录的域控制器证书已过期。系统事件日志中有其他信息。 |
The domain controller certificate used for logon has expired. There is additional information in the system event log. |
| 0xC000040F | 用于登录的域控制器证书已被吊销。系统事件日志中有其他信息。 |
The domain controller certificate used for logon has been revoked. There is additional information in the system event log. |
| 0xC0000410 | 函数不能操作参数之一中的数据。 |
Data present in one of the parameters is more than the function can operate on. |
| 0xC0000411 | 系统未能休眠(错误代码是 %hs)。系统重新启动之前，休眠将被禁用。 |
The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted. |
| 0xC0000412 | 未能延迟加载 .dll 或从延迟加载的 .dll 获得函数地址。 |
An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed. |
| 0xC0000413 | 登录失败: 你正在登录的计算机受身份验证防火墙保护。不允许指定的帐户通过到此计算机的身份验证。 |
Logon Failure: The machine you are logging onto is protected by an authentication firewall. The specified account is not allowed to authenticate to the machine. |
| 0xC0000414 | %hs 是一个 16 位应用程序。你没有权限执行 16 位应用程序。请与系统管理员检查你的权限。 |
%hs is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator. |
| 0xC0000415 | {显示器驱动程序已停止响应}%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. |
| 0xC0000416 | 桌面堆在分配会话内存时遇到错误。系统事件日志中包含详细信息。 |
The Desktop heap encountered an error while allocating session memory. There is more information in the system event log. |
| 0xC0000417 | 向 C 运行时函数传入了无效的参数。 |
An invalid parameter was passed to a C runtime function. |
| 0xC0000418 | 身份验证失败，因为 NTLM 被阻止。 |
The authentication failed since NTLM was blocked. |
| 0xC0000419 | 来源对象的 SID 已经在目标林中。 |
The source object's SID already exists in destination forest. |
| 0xC000041A | 在林中已存在受信任域的域名。 |
The domain name of the trusted domain already exists in the forest. |
| 0xC000041B | 在林中已存在受信任域的平面名称。 |
The flat name of the trusted domain already exists in the forest. |
| 0xC000041C | 用户主体名称(UPN)无效。 |
The User Principal Name (UPN) is invalid. |
| 0xC000041D | 用户回调期间遇到未经处理的异常。 |
An unhandled exception was encountered during a user callback. |
| 0xC0000420 | 出现声明故障。 |
An assertion failure has occurred. |
| 0xC0000421 | 应用程序验证程序在当前进程中发现错误。 |
Application verifier has found an error in the current process. |
| 0xC0000423 | 用户模式回调中发生异常，应删除内核回调框架。 |
An exception has occurred in a user mode callback and the kernel callback frame should be removed. |
| 0xC0000424 | 由于与此系统不兼容，已阻止加载 %2。请与软件供应商联系，以获得驱动程序的兼容版本。 |
%2 has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver. |
| 0xC0000425 | 在已经卸载的注册表项上尝试了非法操作。 |
Illegal operation attempted on a registry key which has already been unloaded. |
| 0xC0000426 | 禁止压缩该卷。 |
Compression is disabled for this volume. |
| 0xC0000427 | 由于文件系统限制，因此请求的操作无法完成 |
The requested operation could not be completed due to a file system limitation |
| 0xC0000428 | 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. |
| 0xC0000429 | 实现无法执行此请求。 |
The implementation is not capable of performing the request. |
| 0xC000042A | 请求的操作相对于其他操作次序有误。 |
The requested operation is out of order with respect to other operations. |
| 0xC000042B | 尝试的操作超出实现定义的限制。 |
An operation attempted to exceed an implementation-defined limit. |
| 0xC000042C | 请求的操作需要提升。 |
The requested operation requires elevation. |
| 0xC000042D | 要求的安全上下文不存在。 |
The required security context does not exist. |
| 0xC000042F | 尝试使用关联证书时，PKU2U 协议出现错误。 |
The PKU2U protocol encountered an error while attempting to utilize the associated certificates. |
| 0xC0000432 | 尝试的操作超出文件的有效数据长度。 |
The operation was attempted beyond the valid data length of the file. |
| 0xC0000433 | 尝试的写入操作遇到一个已经为范围的某部分进行的写入。 |
The attempted write operation encountered a write already in progress for some portion of the range. |
| 0xC0000434 | 页面故障映射在处理故障的过程中被更改，因此必须重试该操作。 |
The page fault mappings changed in the middle of processing a fault so the operation must be retried. |
| 0xC0000435 | 从内存中清除此文件的尝试无法从内存中清除某些或所有数据。 |
The attempt to purge this file from memory failed to purge some or all the data from memory. |
| 0xC0000440 | 请求的凭据要求确认。 |
The requested credential requires confirmation. |
| 0xC0000441 | 远程服务器为使用客户端加密打开的文件发送了无效的响应。 |
The remote server sent an invalid response for a file being opened with Client Side Encryption. |
| 0xC0000442 | 远程服务器不支持客户端加密，即使其声明支持。 |
Client Side Encryption is not supported by the remote server even though it claims to support it. |
| 0xC0000443 | 文件已加密，应以客户端加密模式打开。 |
File is encrypted and should be opened in Client Side Encryption mode. |
| 0xC0000444 | 正在新建加密文件，需要提供 $EFS。 |
A new encrypted file is being created and a $EFS needs to be provided. |
| 0xC0000445 | SMB 客户端在非 CSE 文件上请求 CSE FSCTL。 |
The SMB client requested a CSE FSCTL on a non-CSE file. |
| 0xC0000446 | 指明特定的安全 ID 可能不能作为对象的标签分配。 |
Indicates a particular Security ID may not be assigned as the label of an object. |
| 0xC0000450 | 承载此设备驱动程序的进程已终止。 |
The process hosting the driver for this device has terminated. |
| 0xC0000451 | 由于可能有多个不可辨别的设备与识别条件相匹配，无法识别所请求的系统设备。 |
The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. |
| 0xC0000452 | 找不到请求的系统设备。 |
The requested system device cannot be found. |
| 0xC0000453 | 必须重新启动此启动应用程序。 |
This boot application must be restarted. |
| 0xC0000454 | 存在的 NVRAM 资源不足，无法完成 API。可能需要重新启动。 |
Insufficient NVRAM resources exist to complete the API. A reboot might be required. |
| 0xC0000455 | 指定的会话无效。 |
The specified session is invalid. |
| 0xC0000456 | 指定的线程已经位于会话中。 |
The specified thread is already in a session. |
| 0xC0000457 | 指定的线程不位于会话中。 |
The specified thread is not in a session. |
| 0xC0000458 | 指定的权重无效。 |
The specified weight is invalid. |
| 0xC0000459 | 操作已经暂停。 |
The operation was paused. |
| 0xC0000460 | 无法处理指定操作的范围。 |
No ranges for the specified operation were able to be processed. |
| 0xC0000461 | 此磁盘的物理资源已用尽。 |
The physical resources of this disk have been exhausted. |
| 0xC0000462 | 无法启动此应用程序。请尝试重新安装应用程序以解决该问题。 |
The application cannot be started. Try reinstalling the application to fix the problem. |
| 0xC0000463 | {设备功能不受支持}该设备不支持命令功能。 |
{Device Feature Not Supported}The device does not support the command feature. |
| 0xC0000464 | {源/目标设备无法访问}无法访问该设备。 |
{Source/Destination device unreachable}The device is unreachable. |
| 0xC0000465 | {无效的代理数据令牌}代表数据的令牌无效。 |
{Invalid Proxy Data Token}The token representing the data is invalid. |
| 0xC0000466 | 暂时无法使用该文件服务器。 |
The file server is temporarily unavailable. |
| 0xC0000467 | 暂时无法使用该文件。 |
The file is temporarily unavailable. |
| 0xC0000468 | {设备资源不足}目标设备没有足够的资源来完成操作。 |
{Device Insufficient Resources}The target device has insufficient resources to complete the operation. |
| 0xC0000469 | 无法启动应用程序，因为该程序当前正在更新。 |
The application cannot be started because it is currently updating. |
| 0xC000046A | 无法读取请求数据的指定副本。 |
The specified copy of the requested data could not be read. |
| 0xC000046B | 无法将指定的数据写入到任何副本中。 |
The specified data could not be written to any of the copies. |
| 0xC000046C | 此设备上的一个或多个数据副本可能不同步。在完成数据完整性扫描后，才能执行写入操作。 |
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. |
| 0xC000046D | 任何提供程序都没有从外部支持此对象。 |
This object is not externally backed by any provider. |
| 0xC000046E | 无法识别该外部支持提供程序。 |
The external backing provider is not recognized. |
| 0xC000046F | 压缩此对象不会节省空间。 |
Compressing this object would not save space. |
| 0xC0000470 | 发生了数据完整性校验和错误。文件流中的数据已损坏。 |
A data integrity checksum error occurred. Data in the file stream is corrupt. |
| 0xC0000471 | 已尝试在同一操作中修改 KERNEL 和正常扩展属性 (EA)。 |
An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation. |
| 0xC0000472 | {不支持 LogicalBlockProvisioningReadZero}目标设备不支持从已剪裁或未映射的块中的读取值返回零。 |
{LogicalBlockProvisioningReadZero Not Supported}The target device does not support read returning zeros from trimmed/unmapped blocks. |
| 0xC0000473 | {超过最大段描述符数量}该命令指定的描述符数量超过了设备支持的最大数量。 |
{Maximum Segment Descriptors Exceeded}The command specified a number of descriptors that exceeded the maximum supported by the device. |
| 0xC0000474 | {对齐冲突}该命令指定的数据偏移未对齐设备的粒度/队列。 |
{Alignment Violation}The command specified a data offset that does not align to the device's granularity/alignment. |
| 0xC0000475 | {参数列表中的字段无效}该命令在其参数列表中指定了无效字段。 |
{Invalid Field In Parameter List}The command specified an invalid field in its parameter list. |
| 0xC0000476 | {正在进行操作}设备当前正在进行某项操作。 |
{Operation In Progress}An operation is currently in progress with the device. |
| 0xC0000477 | {I_T Nexus 无效}试图通过无效路径将该命令向下发送到目标设备。 |
{Invalid I_T Nexus}An attempt was made to send down the command via an invalid path to the target device. |
| 0xC0000478 | 指定文件上已禁用推移操作。 |
Scrub is disabled on the specified file. |
| 0xC0000479 | 存储设备未提供冗余。 |
The storage device does not provide redundancy. |
| 0xC000047A | 不支持对常驻文件执行操作。 |
An operation is not supported on a resident file. |
| 0xC000047B | 不支持对压缩的文件执行操作。 |
An operation is not supported on a compressed file. |
| 0xC000047C | 不支持对目录执行操作。 |
An operation is not supported on a directory. |
| 0xC000047D | {IO 操作超时}指定的 I/O 操作无法在期望的时间段内完成。 |
{IO Operation Timeout}The specified I/O operation failed to complete within the expected time period. |
| 0xC000047E | 在系统二进制文件中检测到错误。请尝试恢复电脑以解决该问题。 |
An error in a system binary was detected. Try refreshing the PC to fix the problem. |
| 0xC000047F | 在系统上检测到损坏的 CLR NGEN 二进制文件。 |
A corrupted CLR NGEN binary was detected on the system. |
| 0xC0000480 | 共享暂时不可用。 |
The share is temporarily unavailable. |
| 0xC0000481 | 找不到目标 dll，因为未承载 apiset %hs。 |
The target dll was not found because the apiset %hs is not hosted. |
| 0xC0000482 | API 集扩展包含不存在的 API 集的主机。 |
The API set extension contains a host for a non-existent API set. |
| 0xC0000483 | 设备硬件出现致命错误，导致请求失败。 |
The request failed due to a fatal device hardware error. |
| 0xC0000484 | 指定的固件插槽无效。 |
The specified firmware slot is invalid. |
| 0xC0000485 | 指定的固件映像无效。 |
The specified firmware image is invalid. |
| 0xC0000486 | 由于存储拓扑 ID 不匹配，请求失败。 |
The request failed due to a storage topology ID mismatch. |
| 0xC0000487 | 指定的 Windows 映像(WIM)未标记为可引导。 |
The specified Windows Image (WIM) is not marked as bootable. |
| 0xC0000488 | 操作被家长控制阻止。 |
The operation was blocked by parental controls. |
| 0xC0000489 | 由于指定的应用程序需要先注册，部署操作失败。 |
The deployment operation failed because the specified application needs to be registered first. |
| 0xC000048A | 由于配额操作仍在进行中，请求的操作失败。 |
The requested operation failed due to quota operation is still in progress. |
| 0xC000048B | 回调函数必须通过内联方式调用。 |
The callback function must be invoked inline. |
| 0xC000048C | 正在引用的文件系统块已达到最大引用计数，无法进一步引用。 |
A file system block being referenced has already reached the maximum reference count and can't be referenced any further. |
| 0xC000048D | 请求的操作失败，因为文件流已标记为不允许写入。 |
The requested operation failed because the file stream is marked to disallow writes. |
| 0xC000048E | Windows 信息保护策略不允许访问此网络资源。 |
Windows Information Protection policy does not allow access to this network resource. |
| 0xC000048F | 请求的操作失败，返回体系结构特定的故障代码。 |
The requested operation failed with an architecture-specific failure code. |
| 0xC0000490 | 没有可用于此设备的兼容驱动程序。 |
There are no compatible drivers available for this device. |
| 0xC0000491 | 在系统上找不到指定的驱动程序包。 |
The specified driver package cannot be found on the system. |
| 0xC0000492 | 驱动程序包找不到所需的驱动程序配置。 |
The driver package cannot find a required driver configuration. |
| 0xC0000493 | 驱动程序配置不完整，不可用于此设备。 |
The driver configuration is incomplete for use with this device. |
| 0xC0000494 | 设备需要包含功能驱动程序的驱动程序配置。 |
The device requires a driver configuration with a function driver. |
| 0xC0000495 | 设备有待进一步配置。 |
The device is pending further configuration. |
| 0xC0000496 | 设备提示名称缓冲区太小，无法接收剩余名称。 |
The device hint name buffer is too small to receive the remaining name. |
| 0xC0000497 | 程序包当前不可用。 |
The package is currently not available. |
| 0xC0000499 | 该设备处于维护模式。 |
The device is in maintenance mode. |
| 0xC000049A | DAX 卷不支持此操作。 |
This operation is not supported on a DAX volume. |
| 0xC000049B | 卷上的可用空间太零碎，无法完成此操作。 |
The free space on the volume is too fragmented to complete this operation. |
| 0xC000049C | 此卷具有活动 DAX 映射。 |
The volume has active DAX mappings. |
| 0xC000049D | 已阻止创建进程。 |
The process creation has been blocked. |
| 0xC000049E | 此存储设备已丢失数据或持久性。 |
The storage device has lost data or persistence. |
| 0xC000049F | CFG 启用时，无法设置驱动程序验证程序易失性设置。 |
Driver Verifier Volatile settings cannot be set when CFG is enabled. |
| 0xC0000500 | 指定的任务名称无效。 |
The specified task name is invalid. |
| 0xC0000501 | 指定的任务索引无效。 |
The specified task index is invalid. |
| 0xC0000502 | 指定的线程已加入任务。 |
The specified thread is already joining a task. |
| 0xC0000503 | 已请求回调绕过本机代码。 |
A callback has requested to bypass native code. |
| 0xC0000504 | 目标计算机上未定义指定的中心访问策略。 |
The Central Access Policy specified is not defined on the target machine. |
| 0xC0000505 | 从 Active Directory 获取的中心访问策略无效。 |
The Central Access Policy obtained from Active Directory is invalid. |
| 0xC0000506 | 无法完成请求的操作，因为指定的进程不是 GUI 进程。 |
Unable to finish the requested operation because the specified process is not a GUI process. |
| 0xC0000507 | 该设备没有响应，无法安全删除。 |
The device is not responding and cannot be safely removed. |
| 0xC0000508 | 指定的作业已有为其分配的容器。 |
The specified Job already has a container assigned to it. |
| 0xC0000509 | 指定的作业没有为其分配的容器。 |
The specified Job does not have a container assigned to it. |
| 0xC000050A | 设备没有响应。 |
The device is unresponsive. |
| 0xC000050B | 对象管理器在检索对象时遇到重分析点。 |
The object manager encountered a reparse point while retrieving an object. |
| 0xC000050C | 所请求的属性不存在于指定的文件或目录中。 |
The requested attribute is not present on the specified file or directory. |
| 0xC000050D | 此卷不是分层卷。 |
This volume is not a tiered volume. |
| 0xC000050E | 此文件当前与一个不同的流 ID 关联。 |
This file is currently associated with a different stream id. |
| 0xC000050F | 由于指定的作业具有子项，请求的操作无法完成。 |
The requested operation could not be completed because the specified job has children. |
| 0xC0000510 | 指定的对象已经初始化。 |
The specified object has already been initialized. |
| 0xC0000602 | {快速异常检测失败}发生了快速异常检测失败。将不会调用异常处理程序，并且进程将立即终止。 |
{Fail Fast Exception}A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. |
| 0xC0000603 | Windows 无法验证此文件的数字签名。此文件的签名证书已经吊销。 |
Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked. |
| 0xC0000604 | 操作被阻止，因为进程禁止动态生成代码。 |
The operation was blocked as the process prohibits dynamic code generation. |
| 0xC0000605 | Windows 无法验证此文件的数字签名。此文件的签名证书已过期。 |
Windows cannot verify the digital signature for this file. The signing certificate for this file has expired. |
| 0xC0000606 | 指定的映像文件被阻止加载，因为未启用进程所需的功能: 控制流防护。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard. |
| 0xC0000607 | 指定的映像文件被阻止加载，因为未启用进程所需的功能: 返回流防护。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Return Flow Guard. |
| 0xC0000608 | 发生了针对返回流防护受限区域的无效内存访问。 |
An invalid memory access occurred to a Return Flow Guard restricted region. |
| 0xC0000609 | 发生了针对来自附加进程的返回流防护受限区域的无效内存访问。 |
An invalid memory access occurred to a Return Flow Guard restricted region from an attached process. |
| 0xC000060A | 无法更新线程会话，因为已限制对该进程执行此操作。 |
The thread context could not be updated because this has been restricted for the process. |
| 0xC000060B | 尝试访问另一分区的专用文件/节时被拒绝。 |
An attempt to access another partition's private file/section was rejected. |
| 0xC000060C | 此进程在附加到另一进程时，对返回流防护受限区域触发了无效内存访问。 |
This process triggered an invalid memory access to a Return Flow Guard restricted region while attached to another process. |
| 0xC0000700 | ALPC 端口已关闭。 |
The ALPC port is closed. |
| 0xC0000701 | 请求的 ALPC 消息不再可用。 |
The ALPC message requested is no longer available. |
| 0xC0000702 | 提供的 ALPC 消息无效。 |
The ALPC message supplied is invalid. |
| 0xC0000703 | ALPC 消息已取消。 |
The ALPC message has been canceled. |
| 0xC0000704 | 递归调度尝试无效。 |
Invalid recursive dispatch attempt. |
| 0xC0000705 | 同步请求中尚未提供接收缓冲区。 |
No receive buffer has been supplied in a synchrounus request. |
| 0xC0000706 | 连接端口在无效的上下文中使用。 |
The connection port is used in an invalid context. |
| 0xC0000707 | ALPC 端口不接受新的请求消息。 |
The ALPC port does not accept new request messages. |
| 0xC0000708 | 请求的资源已在使用。 |
The resource requested is already in use. |
| 0xC0000709 | 硬件已报告不可纠正的内存错误。 |
The hardware has reported an uncorrectable memory error. |
| 0xC000070A | 返回状态 0x%08x，在句柄 0x%x 上等待 0x%p (位于等待者 0x%p)。 |
Status 0x%08x was returned, waiting on handle 0x%x for wait 0x%p, in waiter 0x%p. |
| 0xC000070B | 回调 0x%p(0x%p)后，完成调用 SetEvent(0x%p)失败，状态为 0x%08x。 |
After a callback to 0x%p(0x%p), a completion call to SetEvent(0x%p) failed with status 0x%08x. |
| 0xC000070C | 回调 0x%p(0x%p)后，完成调用 ReleaseSemaphore(0x%p, %d)失败，状态为 0x%08x。 |
After a callback to 0x%p(0x%p), a completion call to ReleaseSemaphore(0x%p, %d) failed with status 0x%08x. |
| 0xC000070D | 回调 0x%p(0x%p)后，完成调用 ReleaseMutex(%p)失败，状态为 0x%08x。 |
After a callback to 0x%p(0x%p), a completion call to ReleaseMutex(%p) failed with status 0x%08x. |
| 0xC000070E | 回调 0x%p(0x%p)后，完成调用 FreeLibrary(%p)失败，状态为 0x%08x。 |
After a callback to 0x%p(0x%p), an completion call to FreeLibrary(%p) failed with status 0x%08x. |
| 0xC000070F | 线程池 0x%p 已释放，同时线程正在向其投放回调 0x%p(0x%p)。 |
The threadpool 0x%p was released while a thread was posting a callback to 0x%p(0x%p) to it. |
| 0xC0000710 | 在回调 0x%p(0x%p)后，线程池工作线程正在模拟客户端。这是意外，指示回调缺少对还原模拟的调用。 |
A threadpool worker thread is impersonating a client, after a callback to 0x%p(0x%p).This is unexpected, indicating that the callback is missing a call to revert the impersonation. |
| 0xC0000711 | 在执行 APC 后，线程池工作线程正在模拟客户端。这是意外，指示 APC 缺少对还原模拟的调用。 |
A threadpool worker thread is impersonating a client, after executing an APC.This is unexpected, indicating that the APC is missing a call to revert the impersonation. |
| 0xC0000712 | 目标进程或目标线程的包含进程是受保护的进程。 |
Either the target process, or the target thread's containing process, is a protected process. |
| 0xC0000713 | 由于 MCA，正在使用 MCA EXCEPTION 调度线程。 |
A Thread is getting dispatched with MCA EXCEPTION because of MCA. |
| 0xC0000714 | 客户端证书帐户映射不唯一。 |
The client certificate account mapping is not unique. |
| 0xC0000715 | 无法遵循符号链接，因为其类型已禁用。 |
The symbolic link cannot be followed because its type is disabled. |
| 0xC0000716 | 指示指定的字符串对 IDN 标准化无效。 |
Indicates that the specified string is not valid for IDN normalization. |
| 0xC0000718 | 提供的回调已被注册。 |
The provided callback is already registered. |
| 0xC0000719 | 提供的上下文与目标不匹配。 |
The provided context did not match the target. |
| 0xC000071A | 指定的端口已有完成列表。 |
The specified port already has a completion list. |
| 0xC000071B | 线程池工作线程在线程基本优先级 0x%x 进入回调并在优先级 0x%x 退出。这是意外情况，表明回调未还原优先级。 |
A threadpool worker thread enter a callback at thread base priority 0x%x and exited at priority 0x%x.This is unexpected, indicating that the callback missed restoring the priority. |
| 0xC000071C | 为此操作指定的线程(句柄 %p)无效。可能已指定线程池工作线程。 |
An invalid thread, handle %p, is specified for this operation. Possibly, a threadpool worker thread was specified. |
| 0xC000071D | 线程池工作线程进入回调，离开了事务状态。此这是意外情况，表明回调未清除事务。 |
A threadpool worker thread enter a callback, which left transaction state.This is unexpected, indicating that the callback missed clearing the transaction. |
| 0xC000071E | 线程池工作线程进入回调，使加载器仍处于锁定状态。这是意外情况，表明回调未释放锁定。 |
A threadpool worker thread enter a callback, which left the loader lock held.This is unexpected, indicating that the callback missed releasing the lock. |
| 0xC000071F | 线程池工作线程进入回调，但仍保留着首选语言设置。这是意外情况，表明回调未清除它们。 |
A threadpool worker thread enter a callback, which left with preferred languages set.This is unexpected, indicating that the callback missed clearing them. |
| 0xC0000720 | 线程池工作线程进入回调，但仍保留着后台优先级设置。这是意外情况，表明回调未还原初始优先级。 |
A threadpool worker thread enter a callback, which left with background priorities set.This is unexpected, indicating that the callback missed restoring the original priorities. |
| 0xC0000721 | 线程池工作线程在线程关联 %p 进入回调，在关联 %p 退出。这是意外情况，表明回调未还原优先级。 |
A threadpool worker thread enter a callback at thread affinity %p and exited at affinity %p.This is unexpected, indicating that the callback missed restoring the priority. |
| 0xC0000722 | 调用方超过了可在单个本地过程调用中传输的最大句柄数。 |
The caller has exceeded the maximum number of handles that may be transmitted ina single local procedure call. |
| 0xC0000800 | 尝试的操作要求启用自疗功能。 |
The attempted operation required self healing to be enabled. |
| 0xC0000801 | 目录服务不能执行请求的操作因为正在进行域重命名操作。 |
The Directory Service cannot perform the requested operation because a domain rename operation is in progress. |
| 0xC0000802 | 请求的文件操作失败，因为超出存储配额。若要释放磁盘空间，请将文件移至其他位置或删除不必要的文件。有关详细信息，请与系统管理员联系。 |
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. |
| 0xC0000804 | 请求的文件操作失败，因为存储策略阻止此类型文件。有关详细信息，请与系统管理员联系。 |
The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator. |
| 0xC0000805 | 由于磁盘上的群集损坏，因此操作无法完成。 |
The operation could not be completed due to bad clusters on disk. |
| 0xC0000806 | 无法完成操作，因为卷有问题。请运行 chkdsk 并重试。 |
The operation could not be completed because the volume is dirty. Please run chkdsk and try again. |
| 0xC0000808 | 卷修复不成功。 |
The volume repair was not successful. |
| 0xC0000809 | 其中一个卷损坏日志已满。无法记录检测到的更多损坏。 |
One of the volume corruption logs is full. Further corruptions that may be detected won't be logged. |
| 0xC000080A | 其中一个卷损坏日志内部已损坏，需要重新创建。该卷可能包含未检测到的损坏，并且必须进行扫描。 |
One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned. |
| 0xC000080B | 无法对其中一个卷损坏日志进行操作。 |
One of the volume corruption logs is unavailable for being operated on. |
| 0xC000080C | 已经删除其中一个卷损坏日志，但是该日志中仍然包含损坏记录。该卷包含检测到的损坏，并且必须进行扫描。 |
One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned. |
| 0xC000080D | chkdsk 已经清除了其中一个卷损坏日志，并且不再包含真实损坏。 |
One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions. |
| 0xC000080E | 卷中存在孤立文件，但是无法恢复，因为无法在恢复目录中创建更多新名称。文件必须从恢复目录中移出。 |
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. |
| 0xC000080F | 操作无法完成，原因是主动扫描仪的实例当前正在运行。 |
The operation could not be completed because an instance of Proactive Scanner is currently running. |
| 0xC0000810 | 无法完成对加密文件执行的读取或写入操作，因为尚未打开该文件以进行数据访问。 |
The read or write operation to an encrypted file could not be completed because the file has not been opened for data access. |
| 0xC0000811 | 其中一个卷损坏日志来自较新版本的 Windows，并且包含损坏记录。该日志将被清空并重置为当前版本，而且卷健康状态也将相应更新。 |
One of the volume corruption logs comes from a newer version of Windows and contains corruption records. The log will be emptied and reset to the current version, and the volume health state will be updated accordingly. |
| 0xC0000901 | 签出或锁定此文件，以便另一用户编辑。 |
This file is checked out or locked for editing by another user. |
| 0xC0000902 | 保存更改之前必须签出文件。 |
The file must be checked out before saving changes. |
| 0xC0000903 | 正在保存或检索的文件类型已阻止。 |
The file type being saved or retrieved has been blocked. |
| 0xC0000904 | 文件大小超出允许的限制，无法保存。 |
The file size exceeds the limit allowed and cannot be saved. |
| 0xC0000905 | 访问被拒绝。在此位置打开文件之前，必须先浏览到网站并选择自动登录选项。 |
Access Denied. Before opening files in this location, you must first browse to the web site and select the option to login automatically. |
| 0xC0000906 | 无法成功完成操作，因为文件包含病毒或潜在的垃圾软件。 |
Operation did not complete successfully because the file contains a virus or potentially unwanted software. |
| 0xC0000907 | 此文件包含病毒或潜在的垃圾软件，无法打开。由于病毒或潜在的垃圾软件的本质，此文件已从该位置删除。 |
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. |
| 0xC0000908 | 此设备所需的资源与 MCFG 表冲突。 |
The resources required for this device conflict with the MCFG table. |
| 0xC0000909 | 操作未能成功完成，因为这将导致操作锁定中断。调用方已要求现有操作锁定不被中断。 |
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. |
| 0xC000090A | 不正确的项。 |
Bad key. |
| 0xC000090B | 不正确的数据。 |
Bad data. |
| 0xC000090C | 该项不存在。 |
Key does not exist. |
| 0xC0000910 | 已吊销对指定文件句柄的访问权限。 |
Access to the specified file handle has been revoked. |
| 0xC0009898 | WOW 断言错误。 |
WOW Assertion Error. |
| 0xC000A000 | 加密签名无效。 |
The cryptographic signature is invalid. |
| 0xC000A001 | 加密提供程序不支持 HMAC。 |
The cryptographic provider does not support HMAC. |
| 0xC000A002 | 已计算的身份验证标记与输入的身份验证标记不匹配。 |
The computed authentication tag did not match the input authentication tag. |
| 0xC000A003 | 请求的状态转换无效且无法执行。 |
The requested state transition is invalid and cannot be performed. |
| 0xC000A004 | 提供的内核信息版本无效。 |
The supplied kernel information version is invalid. |
| 0xC000A005 | 提供的 PEP 信息版本无效。 |
The supplied PEP information version is invalid. |
| 0xC000A006 | 已吊销对指定句柄的访问权限。 |
Access to the specified handle has been revoked. |
| 0xC000A007 | 文件操作将导致文件的末尾在幻像范围内。 |
The file operation will result in the end of file being on a ghosted range. |
| 0xC000A010 | IPSEC 队列溢出。 |
The IPSEC queue overflowed. |
| 0xC000A011 | 邻居发现队列溢出。 |
The neighbor discovery queue overflowed. |
| 0xC000A012 | 接收到 ICMP 跃点限制超出错误。 |
An ICMP hop limit exceeded error was received. |
| 0xC000A013 | 本地计算机上未安装该协议。 |
The protocol is not installed on the local machine. |
| 0xC000A014 | 当操作或数据处于网络快速路径上时遭到拒绝。 |
An operation or data has been rejected while on the network fast path. |
| 0xC000A080 | {延迟写入失败}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. |
| 0xC000A081 | {延迟写入失败}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. |
| 0xC000A082 | {延迟写入失败}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. |
| 0xC000A083 | Windows 无法分析请求的 XML 数据。 |
Windows was unable to parse the requested XML data. |
| 0xC000A084 | 处理 XML 数字签名时出现错误。 |
An error was encountered while processing an XML digital signature. |
| 0xC000A085 | 表明发出连接请求的调用方位于错误的路由分段中。 |
Indicates that the caller made the connection request in the wrong routing compartment. |
| 0xC000A086 | 表明尝试连接到远程主机时存在 AuthIP 故障。 |
Indicates that there was an AuthIP failure when attempting to connect to the remote host. |
| 0xC000A087 | OID 映射组不能具有成员。 |
OID mapped groups cannot have members. |
| 0xC000A088 | 无法找到指定的 OID。 |
The specified OID cannot be found. |
| 0xC000A089 | 该系统对指定的帐户没有授权，因此无法完成此操作。请使用与此帐户相关联的提供程序重新尝试操作。如果这是联机提供程序，请使用提供程序的联机站点。 |
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. |
| 0xC000A100 | 在服务器上未对指定的版本和哈希类型启用哈希生成。 |
Hash generation for the specified version and hash type is not enabled on server. |
| 0xC000A101 | 哈希请求不存在或不是最新的当前文件内容。 |
The hash requests is not present or not up to date with the current file contents. |
| 0xC000A121 | 未注册用于管理指定中断的辅助中断控制器实例。 |
The secondary interrupt controller instance that manages the specified interrupt is not registered. |
| 0xC000A122 | GPIO 客户端驱动程序提供的信息无效。 |
The information supplied by the GPIO client driver is invalid. |
| 0xC000A123 | GPIO 客户端驱动程序指定的版本不受支持。 |
The version specified by the GPIO client driver is not supported. |
| 0xC000A124 | GPIO 客户端驱动程序提供的注册数据包无效。 |
The registration packet supplied by the GPIO client driver is not valid. |
| 0xC000A125 | 指定的句柄不支持请求的操作。 |
The requested operation is not suppported for the specified handle. |
| 0xC000A126 | 请求的连接模式与一个或多个指定的 PIN 上的现有模式冲突。 |
The requested connect mode conflicts with an existing mode on one or more of the specified pins. |
| 0xC000A141 | 请求的运行级别切换无法成功完成，因为一个或多个服务拒绝停止或重新启动。 |
The requested run level switch cannot be completed successfully sinceone or more services refused to stop or restart. |
| 0xC000A142 | 服务含有无效的运行级别设置。服务的运行级别不得高于从属服务的运行级别。 |
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. |
| 0xC000A143 | 无法成功完成请求的运行级别切换，因为在指定的超时时间内一个或多个服务将不会停止或重新启动。 |
The requested run level switch cannot be completed successfully sinceone or more services will not stop or restart within the specified timeout. |
| 0xC000A145 | 在指定的超时时间内，运行级别切换代理未响应。 |
A run level switch agent did not respond within the specified timeout. |
| 0xC000A146 | 运行级别切换当前正在进行。 |
A run level switch is currently in progress. |
| 0xC000A200 | 此操作仅在应用容器上下文中有效。 |
This operation is only valid in the context of an app container. |
| 0xC000A201 | 在应用容器上下文中不支持此功能。 |
This functionality is not supported in the context of an app container. |
| 0xC000A202 | 提供的 SID 长度对应用容器 SID 无效。 |
The length of the SID supplied is not a valid length for app container SIDs. |
| 0xC000A203 | 已拒绝低特权应用容器对指定资源的访问。 |
Access to the specified resource has been denied for a less privileged app container. |
| 0xC000A281 | 找不到快速缓存数据。 |
Fast Cache data not found. |
| 0xC000A282 | 快速缓存数据已过期。 |
Fast Cache data expired. |
| 0xC000A283 | 快速缓存数据损坏。 |
Fast Cache data corrupt. |
| 0xC000A284 | 快速缓存数据已经超出其最大大小，无法更新。 |
Fast Cache data has exceeded its max size and cannot be updated. |
| 0xC000A285 | 快速缓存已重置，需要重新启动，然后才能更新。 |
Fast Cache has been ReArmed and requires a reboot until it can be updated. |
| 0xC000A2A1 | 副本卸载读取操作不受筛选器支持。 |
The copy offload read operation is not supported by a filter. |
| 0xC000A2A2 | 副本卸载写入操作不受筛选器支持。 |
The copy offload write operation is not supported by a filter. |
| 0xC000A2A3 | 不支持对该文件进行副本卸载读取操作。 |
The copy offload read operation is not supported for the file. |
| 0xC000A2A4 | 不支持对该文件进行副本卸载写入操作。 |
The copy offload write operation is not supported for the file. |
| 0xC000CE01 | 支持文件系统虚拟化的提供程序暂时不可用。 |
The provider that supports file system virtualization is temporarily unavailable. |
| 0xC000CE02 | 文件系统虚拟化的元数据已损坏且无法读取。 |
The metadata for file system virtualization is corrupt and unreadable. |
| 0xC000CE03 | 支持文件系统虚拟化的提供程序太忙，无法完成此操作。 |
The provider that supports file system virtualization is too busy to complete this operation. |
| 0xC000CE04 | 支持文件系统虚拟化的提供程序未知。 |
The provider that supports file system virtualization is unknown. |
| 0xC000CF00 | 云文件提供程序未知。 |
The Cloud File provider is unknown. |
| 0xC000CF01 | 云文件提供程序未运行。 |
The Cloud File provider is not running. |
| 0xC000CF02 | 云文件元数据已损坏且不可读取。 |
The Cloud File metadata is corrupt and unreadable. |
| 0xC000CF03 | 由于云文件元数据太大，无法完成该操作。 |
The operation could not be completed because the Cloud File metadata is too large. |
| 0xC000CF06 | 因为不支持云文件元数据版本，无法完成该操作。 |
The operation could not be completed because the Cloud File metadata version is not supported. |
| 0xC000CF07 | 因为该文件不是云文件，此操作无法完成。 |
The operation could not be completed because the file is not a Cloud File. |
| 0xC000CF08 | 因为云文件未同步，此操作不能完成。 |
The operation could not be completed because the Cloud File is not in sync. |
| 0xC0010001 | 调试程序没有进行状态更改。 |
Debugger did not perform a state change. |
| 0xC0010002 | 调试程序发现应用程序正在使用中。 |
Debugger has found the application is not idle. |
| 0xC0020001 | 字符串绑定无效。 |
The string binding is invalid. |
| 0xC0020002 | 绑定句柄的类型不正确。 |
The binding handle is not the correct type. |
| 0xC0020003 | 绑定句柄无效。 |
The binding handle is invalid. |
| 0xC0020004 | 不支持 RPC 协议序列。 |
The RPC protocol sequence is not supported. |
| 0xC0020005 | RPC 协议序列无效。 |
The RPC protocol sequence is invalid. |
| 0xC0020006 | 字符串 UUID 无效。 |
The string UUID is invalid. |
| 0xC0020007 | 终结点格式无效。 |
The endpoint format is invalid. |
| 0xC0020008 | 网络地址无效。 |
The network address is invalid. |
| 0xC0020009 | 找不到终结点。 |
No endpoint was found. |
| 0xC002000A | 超时值无效。 |
The timeout value is invalid. |
| 0xC002000B | 找不到对象 UUID。 |
The object UUID was not found. |
| 0xC002000C | 对象 UUID 已注册。 |
The object UUID has already been registered. |
| 0xC002000D | 类型 UUID 已注册。 |
The type UUID has already been registered. |
| 0xC002000E | RPC 服务器已在侦听。 |
The RPC server is already listening. |
| 0xC002000F | 未登记任何协议序列。 |
No protocol sequences have been registered. |
| 0xC0020010 | RPC 服务器未在侦听。 |
The RPC server is not listening. |
| 0xC0020011 | 管理程序类型未知。 |
The manager type is unknown. |
| 0xC0020012 | 接口未知。 |
The interface is unknown. |
| 0xC0020013 | 没有绑定。 |
There are no bindings. |
| 0xC0020014 | 没有协议序列。 |
There are no protocol sequences. |
| 0xC0020015 | 无法创建终结点。 |
The endpoint cannot be created. |
| 0xC0020016 | 资源不足，无法完成该操作。 |
Not enough resources are available to complete this operation. |
| 0xC0020017 | RPC 服务器不可用。 |
The RPC server is unavailable. |
| 0xC0020018 | RPC 服务器太忙，不能完成该操作。 |
The RPC server is too busy to complete this operation. |
| 0xC0020019 | 网络选项无效。 |
The network options are invalid. |
| 0xC002001A | 该线程中没有远程过程调用活动。 |
There are no remote procedure calls active on this thread. |
| 0xC002001B | 远程过程调用失败。 |
The remote procedure call failed. |
| 0xC002001C | 远程过程调用失败且未执行。 |
The remote procedure call failed and did not execute. |
| 0xC002001D | 发生 RPC 协议错误。 |
An RPC protocol error occurred. |
| 0xC002001F | RPC 服务器不支持传送语法。 |
The transfer syntax is not supported by the RPC server. |
| 0xC0020021 | 不支持类型 UUID。 |
The type UUID is not supported. |
| 0xC0020022 | 标记无效。 |
The tag is invalid. |
| 0xC0020023 | 数组绑定无效。 |
The array bounds are invalid. |
| 0xC0020024 | 绑定不包含登录项名字。 |
The binding does not contain an entry name. |
| 0xC0020025 | 名称语法无效。 |
The name syntax is invalid. |
| 0xC0020026 | 不支持该名称语法。 |
The name syntax is not supported. |
| 0xC0020028 | 没有用来构造 UUID 的网络地址。 |
No network address is available to use to construct a UUID. |
| 0xC0020029 | 终结点重复。 |
The endpoint is a duplicate. |
| 0xC002002A | 未知的身份验证类型。 |
The authentication type is unknown. |
| 0xC002002B | 调用的最大个数太小。 |
The maximum number of calls is too small. |
| 0xC002002C | 字符串太长。 |
The string is too long. |
| 0xC002002D | 找不到 RPC 协议顺序。 |
The RPC protocol sequence was not found. |
| 0xC002002E | 过程号超出范围。 |
The procedure number is out of range. |
| 0xC002002F | 绑定不包含任何身份验证信息。 |
The binding does not contain any authentication information. |
| 0xC0020030 | 未知的身份验证服务。 |
The authentication service is unknown. |
| 0xC0020031 | 未知的身份验证级别。 |
The authentication level is unknown. |
| 0xC0020032 | 安全上下文无效。 |
The security context is invalid. |
| 0xC0020033 | 未知的授权服务。 |
The authorization service is unknown. |
| 0xC0020034 | 项目无效。 |
The entry is invalid. |
| 0xC0020035 | 无法执行该操作。 |
The operation cannot be performed. |
| 0xC0020036 | 终结点映射器中没有更多的终结点可用。 |
There are no more endpoints available from the endpoint mapper. |
| 0xC0020037 | 未导出任何接口。 |
No interfaces have been exported. |
| 0xC0020038 | 项目名不完整。 |
The entry name is incomplete. |
| 0xC0020039 | 版本选项无效。 |
The version option is invalid. |
| 0xC002003A | 没有其他成员。 |
There are no more members. |
| 0xC002003B | 没有内容未导出。 |
There is nothing to unexport. |
| 0xC002003C | 找不到接口。 |
The interface was not found. |
| 0xC002003D | 项目已存在。 |
The entry already exists. |
| 0xC002003E | 找不到项目。 |
The entry is not found. |
| 0xC002003F | 名称服务不可用。 |
The name service is unavailable. |
| 0xC0020040 | 网络地址族无效。 |
The network address family is invalid. |
| 0xC0020041 | 不支持请求的操作。 |
The requested operation is not supported. |
| 0xC0020042 | 没有安全上下文可用来允许模仿。 |
No security context is available to allow impersonation. |
| 0xC0020043 | RPC 中出现内部错误。 |
An internal error occurred in RPC. |
| 0xC0020044 | RPC 服务器尝试将一个整数除零。 |
The RPC server attempted an integer divide by zero. |
| 0xC0020045 | RPC 服务器出现寻址错误。 |
An addressing error occurred in the RPC server. |
| 0xC0020046 | RPC 服务器上的一次浮点操作引起除数为零。 |
A floating point operation at the RPC server caused a divide by zero. |
| 0xC0020047 | RPC 服务器上发生浮点下溢。 |
A floating point underflow occurred at the RPC server. |
| 0xC0020048 | RPC 服务器上发生浮点溢出。 |
A floating point overflow occurred at the RPC server. |
| 0xC0020049 | 此线程的远程过程调用已在进行中。 |
A remote procedure call is already in progress for this thread. |
| 0xC002004A | 没有更多的绑定。 |
There are no more bindings. |
| 0xC002004B | 找不到该组成员。 |
The group member was not found. |
| 0xC002004C | 无法创建终结点映射表数据库项。 |
The endpoint mapper database entry could not be created. |
| 0xC002004D | 对象 UUID 是空的 UUID。 |
The object UUID is the nil UUID. |
| 0xC002004F | 未登记任何接口。 |
No interfaces have been registered. |
| 0xC0020050 | 远程过程调用被取消。 |
The remote procedure call was cancelled. |
| 0xC0020051 | 绑定句柄不包含所有需要的信息。 |
The binding handle does not contain all required information. |
| 0xC0020052 | 在远程过程调用过程中通信失败。 |
A communications failure occurred during a remote procedure call. |
| 0xC0020053 | 请求的身份验证级别不被支持。 |
The requested authentication level is not supported. |
| 0xC0020054 | 未登记任何主名称。 |
No principal name registered. |
| 0xC0020055 | 指定的错误不是有效的 Windows RPC 错误代码。 |
The error specified is not a valid Windows RPC error code. |
| 0xC0020057 | 出现了特定的安全程序包错误。 |
A security package specific error occurred. |
| 0xC0020058 | 线程未取消。 |
Thread is not cancelled. |
| 0xC0020062 | 无效的异步远程过程调用句柄。 |
Invalid asynchronous remote procedure call handle. |
| 0xC0020063 | 这个操作的异步 RPC 调用句柄无效。 |
Invalid asynchronous RPC call handle for this operation. |
| 0xC0020064 | 拒绝访问 HTTP 代理。 |
Access to the HTTP proxy is denied. |
| 0xC0020065 | HTTP 代理服务器拒绝连接，因为 cookie 身份验证失败。 |
HTTP proxy server rejected the connection because the cookie authentication failed. |
| 0xC0030001 | 已没有可用于自动处理绑定的 RPC 服务器。 |
The list of RPC servers available for auto-handle binding has been exhausted. |
| 0xC0030002 | 无法打开由 DCERPCCHARTRANS 指定的文件。 |
The file designated by DCERPCCHARTRANS cannot be opened. |
| 0xC0030003 | 包含字符转换表的文件小于 512 字节。 |
The file containing the character translation table has fewer than 512 bytes. |
| 0xC0030004 | 将空上下文句柄作为 [in] 参数传递。 |
A null context handle is passed as an [in] parameter. |
| 0xC0030005 | 该上下文句柄无法符合已知的范围句柄。 |
The context handle does not match any known context handles. |
| 0xC0030006 | 上下文句柄已在调用期间更改。 |
The context handle changed during a call. |
| 0xC0030007 | 传送给远程过程调用的绑定句柄不匹配。 |
The binding handles passed to a remote procedure call do not match. |
| 0xC0030008 | 占位程序无法取得调用句柄。 |
The stub is unable to get the call handle. |
| 0xC0030009 | 向占位程序传送了空的索引指针。 |
A null reference pointer was passed to the stub. |
| 0xC003000A | 枚举值越界。 |
The enumeration value is out of range. |
| 0xC003000B | 字节计数太小。 |
The byte count is too small. |
| 0xC003000C | 占位程序接收到错误数据。 |
The stub received bad data. |
| 0xC0030059 | 无效的编码/解码句柄操作。 |
Invalid operation on the encoding/decoding handle. |
| 0xC003005A | 系列软件包的不兼容版本。 |
Incompatible version of the serializing package. |
| 0xC003005B | RPC 占位程序的不兼容版本。 |
Incompatible version of the RPC stub. |
| 0xC003005C | RPC 管道对象无效或已损坏。 |
The RPC pipe object is invalid or corrupted. |
| 0xC003005D | 试图在 RPC 管道对象上进行无效操作。 |
An invalid operation was attempted on an RPC pipe object. |
| 0xC003005E | 不支持该版本的 RPC 管道。 |
Unsupported RPC pipe version. |
| 0xC003005F | RPC 管道对象已经关闭。 |
The RPC pipe object has already been closed. |
| 0xC0030060 | 在 RPC 调用完成之前全部的管道都已处理完成。 |
The RPC call completed before all pipes were processed. |
| 0xC0030061 | 没有其他可用的数据来自 RPC 管道。 |
No more data is available from the RPC pipe. |
| 0xC0040035 | 系统 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. |
| 0xC0040036 | 转换程序未能转换资源。 |
A translator failed to translate resources. |
| 0xC0040037 | IRQ 转换程序未能转换资源。 |
A IRQ translator failed to translate resources. |
| 0xC0040038 | 驱动程序 %2 返回了子设备 (%3) 的无效 ID。 |
Driver %2 returned invalid ID for a child device (%3). |
| 0xC0040039 | 将给定操作作为缓存 IO 操作重新发出 |
Reissue the given operation as a cached IO operation |
| 0xC00A0001 | 会话名 %1 无效。 |
Session name %1 is invalid. |
| 0xC00A0002 | 协议驱动程序 %1 无效。 |
The protocol driver %1 is invalid. |
| 0xC00A0003 | 系统路径中找不到协议驱动程序 %1。 |
The protocol driver %1 was not found in the system path. |
| 0xC00A0006 | 一个封闭式操作在等待终端连接。 |
A close operation is pending on the Terminal Connection. |
| 0xC00A0007 | 没有可用的输出缓冲区。 |
There are no free output buffers available. |
| 0xC00A0008 | 找不到 MODEM.INF 文件。 |
The MODEM.INF file was not found. |
| 0xC00A0009 | 在 MODEM.INF 中没有找到(%1)调制解调器。 |
The modem (%1) was not found in MODEM.INF. |
| 0xC00A000A | 调制解调器没有接受发送给它的命令。请验证配置的调制解调器名与连到的调制解调器相匹配。 |
The modem did not accept the command sent to it.Verify the configured modem name matches the attached modem. |
| 0xC00A000B | 调制解调器没有接受发送给它的命令。请验证调制解调器连接正确并且已通电。 |
The modem did not respond to the command sent to it.Verify the modem is properly cabled and powered on. |
| 0xC00A000C | 由于连接被中断，载波检测没有成功，或者载波已被放弃。 |
Carrier detect has failed or carrier has been dropped due to disconnect. |
| 0xC00A000D | 在要求的时间内未检测到拨号音。确定电话线连接正确并且工作正常。 |
Dial tone not detected within required time.Verify phone cable is properly attached and functional. |
| 0xC00A000E | 在远程站点回拨时检测到了占线信号。 |
Busy signal detected at remote site on callback. |
| 0xC00A000F | 回拨时在远程站点上检测到了声音。 |
Voice detected at remote site on callback. |
| 0xC00A0010 | 传输驱动程序错误 |
Transport driver error |
| 0xC00A0012 | 你使用的客户端没有使用这个系统的权利。你的登录请求遭到拒绝。 |
The client you are using is not licensed to use this system. Your logon request is denied. |
| 0xC00A0013 | 系统已达到其授权的登录限制。请以后再试一次。 |
The system has reached its licensed logon limit.Please try again later. |
| 0xC00A0014 | 系统许可证已过期。登录请求被拒绝。 |
The system license has expired. Your logon request is denied. |
| 0xC00A0015 | 无法找到指定的会话。 |
The specified session cannot be found. |
| 0xC00A0016 | 指定的会话名称已在使用中。 |
The specified session name is already in use. |
| 0xC00A0017 | 由于远程桌面服务当前正忙，因此无法完成你尝试执行的任务。请在几分钟之后重试。其他用户应该仍然能够登录。 |
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. |
| 0xC00A0018 | 试图连接到其视频模式不受当前客户端支持的会话。 |
An attempt has been made to connect to a session whose video mode is not supported by the current client. |
| 0xC00A0022 | 应用程序试图启动 DOS 图形模式。不支持 DOS 图形模式。 |
The application attempted to enable DOS graphics mode.DOS graphics mode is not supported. |
| 0xC00A0024 | 请求的操作无法只在系统控制台上运行。这通常是驱动程序或系统 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. |
| 0xC00A0026 | 客户端未能对服务器连接消息作出响应。 |
The client failed to respond to the server connect message. |
| 0xC00A0027 | 不支持断开控制台会话的连接。 |
Disconnecting the console session is not supported. |
| 0xC00A0028 | 不支持重新将一个断开的会话连接到控制台。 |
Reconnecting a disconnected session to the console is not supported. |
| 0xC00A002A | 远程控制另一个会话的请求被拒绝。 |
The request to control another session remotely was denied. |
| 0xC00A002B | 过程已请求访问一个会话，但是尚未授权这些访问权利。 |
A process has requested access to a session, but has not been granted those access rights. |
| 0xC00A002E | 终端连接驱动程序 %1 无效。 |
The Terminal Connection driver %1 is invalid. |
| 0xC00A002F | 在系统路径上没有找到终端连接驱动程序 %1。 |
The Terminal Connection driver %1 was not found in the system path. |
| 0xC00A0030 | 无法远端控制请求的会话。你无法控制自己的会话、控制其它会话的会话或无用户登录的会话，也无法从控制台控制其他会话。 |
The requested session cannot be controlled remotely.You cannot control your own session, a session that is trying to control your session,a session that has no user logged on, nor control other sessions from the console. |
| 0xC00A0031 | 该请求的会话没有配置成允许远程控制。 |
The requested session is not configured to allow remote control. |
| 0xC00A0032 | RDP 协议组件 %2 在协议流中发现一个错误并且中断了客户端连接。 |
The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client. |
| 0xC00A0033 | 连接到该终端服务器的请求被拒绝。还没有为这份终端客户端输入终端服务器客户端许可证号码。请与系统管理员联系，为这个终端服务器客户端输入一个有效的、唯一的许可证号码。要继续，请单击“确定”。 |
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 Client.Please call your system administrator for help in entering a valid, unique license number for this Terminal Server Client.Click OK to continue. |
| 0xC00A0034 | 连接到该终端服务器的请求被拒绝。另一个用户正在使用你的终端服务器客户端许可证号码。请与系统管理员联系，为这个终端服务器客户端输入一个有效的、唯一的许可证号码。要继续，请单击“确定”。 |
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 new copy of the Terminal Server Client with a valid, unique license number.Click OK to continue. |
| 0xC00A0035 | 由于更改了显示模式，控制台的远程控制已终止。不支持在远程控制会话中更改显示模式。 |
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. |
| 0xC00A0036 | 由于当前没有远程控制指定的会话，无法终止远程控制。 |
Remote control could not be terminated because the specified session is not currently being remotely controlled. |
| 0xC00A0037 | 交互式登录权限已禁用。请与你的系统管理员联系。 |
Your interactive logon privilege has been disabled.Please contact your system administrator. |
| 0xC00A0038 | 终端服务器安全层在协议流中检测到错误，并已取消客户端连接。客户端 IP: %2。 |
The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.Client IP: %2. |
| 0xC00A0039 | 目标会话与当前会话不兼容。 |
The target session is incompatible with the current session. |
| 0xC00A003A | 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. |
| 0xC00B0001 | 资源加载器找不到 MUI 文件。 |
The resource loader failed to find MUI file. |
| 0xC00B0002 | 资源加载器未能加载 MUI 文件，因为文件未能通过验证。 |
The resource loader failed to load MUI file because the file fail to pass validation. |
| 0xC00B0003 | RC 清单已被垃圾数据或不支持的版本损坏，或缺少必需的项目。 |
The RC Manifest is corrupted with garbage data or unsupported version or missing required item. |
| 0xC00B0004 | RC 清单的区域性名称无效。 |
The RC Manifest has invalid culture name. |
| 0xC00B0005 | RC 清单的 ultimatefallback 名称无效。 |
The RC Manifest has invalid ultimatefallback name. |
| 0xC00B0006 | 资源加载器缓存没有已加载的 MUI 项。 |
The resource loader cache doesn't have loaded MUI entry. |
| 0xC00B0007 | 用户已停止资源枚举。 |
User stopped resource enumeration. |
| 0xC0130001 | 该群集节点无效。 |
The cluster node is not valid. |
| 0xC0130002 | 该群集节点已经存在。 |
The cluster node already exists. |
| 0xC0130003 | 一个节点正在加入该群集。 |
A node is in the process of joining the cluster. |
| 0xC0130004 | 找不到群集节点。 |
The cluster node was not found. |
| 0xC0130005 | 找不到群集本地节点信息。 |
The cluster local node information was not found. |
| 0xC0130006 | 群集网络已经存在。 |
The cluster network already exists. |
| 0xC0130007 | 找不到群集网络。 |
The cluster network was not found. |
| 0xC0130008 | 群集网络接口已经存在。 |
The cluster network interface already exists. |
| 0xC0130009 | 找不到群集网络接口。 |
The cluster network interface was not found. |
| 0xC013000A | 群集请求在这个对象中无效。 |
The cluster request is not valid for this object. |
| 0xC013000B | 群集网络提供程序无效。 |
The cluster network provider is not valid. |
| 0xC013000C | 群集节点坏了。 |
The cluster node is down. |
| 0xC013000D | 无法连接到群集节点。 |
The cluster node is not reachable. |
| 0xC013000E | 该群集节点不是群集的一个成员。 |
The cluster node is not a member of the cluster. |
| 0xC013000F | 目前没有执行群集加入操作。 |
A cluster join operation is not in progress. |
| 0xC0130010 | 该群集网络无效。 |
The cluster network is not valid. |
| 0xC0130011 | 没有可用的网络适配器。 |
No network adapters are available. |
| 0xC0130012 | 该群集节点可以使用。 |
The cluster node is up. |
| 0xC0130013 | 该群集节点暂停。 |
The cluster node is paused. |
| 0xC0130014 | 该群集节点没有中止。 |
The cluster node is not paused. |
| 0xC0130015 | 没有有效的群集安全上下文。 |
No cluster security context is available. |
| 0xC0130016 | 该群集网络不是为内部群集通信配置的。 |
The cluster network is not configured for internal cluster communication. |
| 0xC0130017 | 群集节点已中毒。 |
The cluster node has been poisoned. |
| 0xC0130018 | 该路径不属于群集共享卷。 |
The path does not belong to a cluster shared volume. |
| 0xC0130019 | 未本地装入该群集共享卷。 |
The cluster shared volume is not locally mounted. |
| 0xC0130020 | 操作失败，因为读取 oplock 中断正在进行。 |
The operation has failed because read oplock break is in progress. |
| 0xC0130021 | 操作失败。CSVFS 必须暂停并刷新信息。 |
The operation has failed. CSVFS has to pause and refresh information. |
| 0xC0130022 | 操作失败。CSVFS 不允许在重定向模式下阻止 I/O。 |
The operation has failed. CSVFS does not allow block i/o in redirected mode. |
| 0xC0130023 | 操作失败。CSVFS 未处于重定向模式。 |
The operation has failed. CSVFS is not in redirected mode. |
| 0xC0130024 | CSVFS 操作失败，因为它处于耗尽状态。 |
CSVFS is failing operation because it is in draining state. |
| 0xC0130025 | 操作失败，因为正在创建快照。 |
The operation has failed because snapshot creation is in progress. |
| 0xC0130026 | 已成功在下层文件系统上执行操作，但是 CSV 失败，因为它处于耗尽状态。 |
The operation has succeeded on the down level file system, but CSV is failing it because it is in draining state. |
| 0xC0130027 | 协调节点上的 Volsnap 返回错误，指示在此卷上没有快照。 |
Volsnap on the coordinating node returned an error indicating that there is no snapshots on this volume. |
| 0xC0130028 | 由于 CSV 卷无法在此文件对象中指定的时间恢复，操作已失败。 |
The operation has failed because CSV volume was not able to recover in time specified on this file object. |
| 0xC0130029 | 操作失败，因为 CSV 没有通过此文件对象的验证。 |
The operation has failed because CSV has invalidated this file object. |
| 0xC0130030 | 只有 CSV 协调器节点才支持此操作。 |
This operation is supported only on the CSV coordinator node. |
| 0xC0130031 | 群集 CAM 检测到有人正在试图回复票证。 |
Cluster CAM has detected that somone is trying to reply ticket. |
| 0xC0140001 | 试图运行一个无效的 AML 操作码 |
An attempt was made to run an invalid AML opcode |
| 0xC0140002 | AML 解释器堆栈溢出 |
The AML Interpreter Stack has overflowed |
| 0xC0140003 | 出现了一个不一致状态 |
An inconsistent state has occurred |
| 0xC0140004 | 试图访问界限外的一个数组 |
An attempt was made to access an array outside of its bounds |
| 0xC0140005 | 一个必需的参数未被指定 |
A required argument was not specified |
| 0xC0140006 | 发生了一个严重错误 |
A fatal error has occurred |
| 0xC0140007 | 指定了一个无效的 SuperName |
An invalid SuperName was specified |
| 0xC0140008 | 指定了一个类型不正确的参数 |
An argument with an incorrect type was specified |
| 0xC0140009 | 指定了一个类型不正确的对象 |
An object with an incorrect type was specified |
| 0xC014000A | 指定了一个类型不正确的目标 |
A target with an incorrect type was specified |
| 0xC014000B | 指定了一个不正确参数个数 |
An incorrect number of arguments were specified |
| 0xC014000C | 未能转换一个地址 |
An address failed to translate |
| 0xC014000D | 指定一个不正确的事件类型 |
An incorrect event type was specified |
| 0xC014000E | 一个目标处理程序已经存在 |
A handler for the target already exists |
| 0xC014000F | 指定了无效的目标数据 |
Invalid data for the target was specified |
| 0xC0140010 | 指定了一个无效的目标区域 |
An invalid region for the target was specified |
| 0xC0140011 | 试图访问定义范围外的字符域 |
An attempt was made to access a field outside of the defined range |
| 0xC0140012 | 无法获取全局系统锁定 |
The Global system lock could not be acquired |
| 0xC0140013 | 试图重新初始化 ACPI 子系统 |
An attempt was made to reinitialize the ACPI subsystem |
| 0xC0140014 | ACPI 子系统尚未初始化 |
The ACPI subsystem has not been initialized |
| 0xC0140015 | 指定了一个不正确的互斥机构 |
An incorrect mutex was specified |
| 0xC0140016 | 目前没有互斥机构 |
The mutex is not currently owned |
| 0xC0140017 | 试图通过不是拥有者的过程访问互斥机构 |
An attempt was made to access the mutex by a process that was not the owner |
| 0xC0140018 | 访问区域空间时，出现了一个错误 |
An error occurred during an access to Region Space |
| 0xC0140019 | 试图使用一个不正确的数据表 |
An attempt was made to use an incorrect table |
| 0xC0140020 | ACPI 事件的注册未能成功 |
The registration of an ACPI event failed |
| 0xC0140021 | ACPI 能源对象未能变换状态 |
An ACPI Power Object failed to transition state |
| 0xC0150001 | 要求的段不在激活上下文中。 |
The requested section is not present in the activation context. |
| 0xC0150002 | Windows 无法处理应用程序绑定信息。有关详细信息，请参阅系统事件日志。 |
Windows was not able to process the application binding information.Please refer to your System Event Log for further information. |
| 0xC0150003 | 应用程序绑定数据格式无效。 |
The application binding data format is invalid. |
| 0xC0150004 | 参照的程序集没有安装在系统上。 |
The referenced assembly is not installed on your system. |
| 0xC0150005 | 清单文件没有以要求的标记和格式信息开始。 |
The manifest file does not begin with the required tag and format information. |
| 0xC0150006 | 清单文件包含多个语法错误。 |
The manifest file contains one or more syntax errors. |
| 0xC0150007 | 应用程序试图激活禁用的激活上下文。 |
The application attempted to activate a disabled activation context. |
| 0xC0150008 | 在活动的激活上下文中找不到任何查找密钥。 |
The requested lookup key was not found in any active activation context. |
| 0xC0150009 | 应用程序要求的组件版本同另一个活动的组件有冲突。 |
A component version required by the application conflicts with another component version already active. |
| 0xC015000A | 要求激活上下文部分的类型与使用的查询 API 不匹配。 |
The type requested activation context section does not match the query API used. |
| 0xC015000B | 由于系统资源缺乏，要求为当前执行的线程禁用独立的激活。 |
Lack of system resources has required isolated activation to be disabled for the current thread of execution. |
| 0xC015000C | 找不到引用的汇编。 |
The referenced assembly could not be found. |
| 0xC015000E | 已设置进程默认激活上下文，因此设置失败。 |
An attempt to set the process default activation context failed because the process default activation context was already set. |
| 0xC015000F | 正被停用的激活上下文不是最近激活的。 |
The activation context being deactivated is not the most recently activated one. |
| 0xC0150010 | 正被停用的激活上下文对于当前执行线程来说不是活动的。 |
The activation context being deactivated is not active for the current thread of execution. |
| 0xC0150011 | 正被停用的激活上下文已被停用了。 |
The activation context being deactivated has already been deactivated. |
| 0xC0150012 | 无法生成系统默认汇编的激活上下文。 |
The activation context of system default assembly could not be generated. |
| 0xC0150013 | 孤立设施使用的组件已经请求结束此进程。 |
A component used by the isolation facility has requested to terminate the process. |
| 0xC0150014 | 激活上下文激活堆栈损坏，该堆栈用于执行运行的线程。 |
The activation context activation stack for the running thread of execution is corrupt. |
| 0xC0150015 | 此进程或线程的应用程序隔离无程序已经损坏。 |
The application isolation metadata for this process or thread has become corrupt. |
| 0xC0150016 | 标识中属性的值不在合法范围内。 |
The value of an attribute in an identity is not within the legal range. |
| 0xC0150017 | 标识中属性的名称不在合法范围内。 |
The name of an attribute in an identity is not within the legal range. |
| 0xC0150018 | 标识包含同一属性的两个定义。 |
An identity contains two definitions for the same attribute. |
| 0xC0150019 | 标识字符串格式错误。这可能是因为尾部的逗号、两个以上未命名的属性、缺少属性名称或缺少属性值。 |
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. |
| 0xC015001A | 组件存储已损坏。 |
The component store has been corrupted. |
| 0xC015001B | 组件的文件跟组件清单中的验证信息不匹配。 |
A component's file does not match the verification information present in the component manifest. |
| 0xC015001C | 清单的标识相同，但其内容不同。 |
The identities of the manifests are identical but their contents are different. |
| 0xC015001D | 组件标识不同。 |
The component identities are different. |
| 0xC015001E | 程序集并非部署。 |
The assembly is not a deployment. |
| 0xC015001F | 该文件不是程序集的一部分。 |
The file is not a part of the assembly. |
| 0xC0150020 | 高级安装程序在安装或提供服务时失败。 |
An advanced installer failed during setup or servicing. |
| 0xC0150021 | XML 声明中的字符编码与文档中使用的编码不匹配。 |
The character encoding in the XML declaration did not match the encoding used in the document. |
| 0xC0150022 | 清单大小超出允许的最大值。 |
The size of the manifest exceeds the maximum allowed. |
| 0xC0150023 | 设置未注册。 |
The setting is not registered. |
| 0xC0150024 | 一个或多个要求的事务成员不存在。 |
One or more required members of the transaction are not present. |
| 0xC0150025 | SMI 基元安装程序在安装或服务过程中失败。 |
The SMI primitive installer failed during setup or servicing. |
| 0xC0150026 | 可执行的通用命令返回一个指示失败的结果。 |
A generic command executable returned a result that indicates failure. |
| 0xC0150027 | 某组件的清单中缺少文件验证信息。 |
A component is missing file verification information in its manifest. |
| 0xC0190001 | 该函数尝试使用为让另一事务使用而保留的名称。 |
The function attempted to use a name that is reserved for use by another transaction. |
| 0xC0190002 | 与该操作关联的事务句柄无效。 |
The transaction handle associated with this operation is not valid. |
| 0xC0190003 | 请求的操作是在不再活动的事务的上下文中进行的。 |
The requested operation was made in the context of a transaction that is no longer active. |
| 0xC0190004 | 无法成功启动事务管理器。不支持事务处理操作。 |
The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported. |
| 0xC0190005 | 由于发生错误，指定资源管理器中的事务支持未启动或已关闭。 |
Transaction support within the specified resource manager is not started or was shut down due to an error. |
| 0xC0190006 | RM 的元数据已损坏。RM 将不起作用。 |
The metadata of the RM has been corrupted. The RM will not function. |
| 0xC0190007 | 资源管理器已尝试准备其未成功加入的事务。 |
The resource manager has attempted to prepare a transaction that it has not successfully joined. |
| 0xC0190008 | 指定的目录未包含文件系统资源管理器。 |
The specified directory does not contain a file system resource manager. |
| 0xC019000A | 远程服务器或共享不支持事务处理文件操作。 |
The remote server or share does not support transacted file operations. |
| 0xC019000B | 文件系统资源管理器请求的日志大小无效。 |
The requested log size for the file system resource manager is invalid. |
| 0xC019000C | 远程服务器发送了使用事务打开的文件的不匹配的版本号或 Fid。 |
The remote server sent mismatching version number or Fid for a file opened with transactions. |
| 0xC019000F | RM 尝试注册已经存在的协议。 |
The RM tried to register a protocol that already exists. |
| 0xC0190010 | 尝试传播事务失败。 |
The attempt to propagate the Transaction failed. |
| 0xC0190011 | 请求的传播协议未注册为 CRM。 |
The requested propagation protocol was not registered as a CRM. |
| 0xC0190012 | 事务对象已具有上级登记，而调用方已尝试一个会新建上级的操作。仅允许单个上级登记。 |
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 allowed. |
| 0xC0190013 | 请求的操作在当前状态的事务对象上无效。 |
The requested operation is not valid on the Transaction object in its current state. |
| 0xC0190014 | 调用方调用了响应 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. |
| 0xC0190015 | 执行请求的操作太迟，因为事务已中止。 |
It is too late to perform the requested operation, since the Transaction has already been aborted. |
| 0xC0190016 | 执行请求的操作太迟，因为事务已提交。 |
It is too late to perform the requested operation, since the Transaction has already been committed. |
| 0xC0190017 | 传递到 NtPushTransaction 或 NtPullTransaction 的缓冲区的格式无效。 |
The buffer passed in to NtPushTransaction or NtPullTransaction is not in a valid format. |
| 0xC0190018 | 与线程关联的当前事务上下文对于事务对象不是有效的句柄。 |
The current transaction context associated with the thread is not a valid handle to a transaction object. |
| 0xC0190019 | 尝试在事务性资源管理器日志中创建空间失败。已在事件日志中记录失败状态。 |
An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log. |
| 0xC0190021 | 与句柄相对应的对象(文件、流、链接)已被事务保存点回退删除。 |
The object (file, stream, link) corresponding to the handle has been deleted by a transaction savepoint rollback. |
| 0xC0190022 | 找不到用于此事务处理文件打开的指定文件的迷你版本。 |
The specified file miniversion was not found for this transacted file open. |
| 0xC0190023 | 指定的文件迷你版本已找到，但已经无效。最可能是因为事务保存点回退。 |
The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback. |
| 0xC0190024 | 迷你版本只能在创建该迷你版本的事务的上下文中打开。 |
A miniversion may only be opened in the context of the transaction that created it. |
| 0xC0190025 | 无法使用修改访问来打开迷你版本。 |
It is not possible to open a miniversion with modify access. |
| 0xC0190026 | 无法再创建此流的迷你版本。 |
It is not possible to create any more miniversions for this stream. |
| 0xC0190028 | 该句柄已由事务验证无效。最可能的原因是在事务结束或回退到保存点时，文件或打开的句柄上出现内存映射。 |
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. |
| 0xC0190030 | 日志数据损坏。 |
The log data is corrupt. |
| 0xC0190032 | 事务结果不可用，因为对其负责的资源管理器已经断开连接。 |
The transaction outcome is unavailable because the resource manager responsible for it has disconnected. |
| 0xC0190033 | 请求遭到拒绝，因为问题中的登记不是上级登记。 |
The request was rejected because the enlistment in question is not a superior enlistment. |
| 0xC0190036 | 无法以事务方式打开该文件，因为文件标识取决于一个未解决的事务的结果。 |
The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction. |
| 0xC0190037 | 无法执行该操作，因为另一事务取决于此属性将不会更改的事实。 |
The operation cannot be performed because another transaction is depending on the fact that this property will not change. |
| 0xC0190038 | 该操作将涉及一个文件和两个事务性资源管理器，因此不被允许。 |
The operation would involve a single file with two transactional resource managers and is therefore not allowed. |
| 0xC0190039 | $Txf 目录必须为空，此操作才能成功。 |
The $Txf directory must be empty for this operation to succeed. |
| 0xC019003A | 该操作将事务性资源管理器置于不一致状态，因此不被允许。 |
The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed. |
| 0xC019003B | 由于事务管理器没有日志，因此操作无法完成。 |
The operation could not be completed because the transaction manager does not have a log. |
| 0xC019003C | 无法计划回退，因为以前计划的回退已经执行或已排队等候执行。 |
A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. |
| 0xC019003D | 文件或目录 %hs 的事务性元数据属性已损坏且无法读取。 |
The transactional metadata attribute on the file or directory %hs is corrupt and unreadable. |
| 0xC019003E | 无法完成加密操作，因为事务是活动的。 |
The encryption operation could not be completed because a transaction is active. |
| 0xC019003F | 不允许在事务中打开该对象。 |
This object is not allowed to be opened in a transaction. |
| 0xC0190040 | 不支持对事务下的远程文件进行内存映射(创建映射区域)。 |
Memory mapping (creating a mapped section) a remote file under a transaction is not supported. |
| 0xC0190043 | 需要升级才能允许资源管理器登记，但已将事务设置为不允许升级。 |
Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it. |
| 0xC0190044 | 该文件已在未解决的事务中打开进行修改，可能仅有事务处理阅读器才能将其打开用于执行。 |
This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader. |
| 0xC0190045 | 使冻结事务解冻的请求遭到忽略，因为以前并未冻结事务。 |
The request to thaw frozen transactions was ignored because transactions had not previously been frozen. |
| 0xC0190046 | 无法冻结事务，因为正在进行某个冻结过程。 |
Transactions cannot be frozen because a freeze is already in progress. |
| 0xC0190047 | 目标卷并非快照卷。此操作仅在装载为快照的卷上有效。 |
The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot. |
| 0xC0190048 | 保存点操作失败，因为在事务上打开文件。上述情况是不允许的。 |
The savepoint operation failed because files are open on the transaction. This is not permitted. |
| 0xC0190049 | 无法完成稀疏操作，因为文件上的事务是活动的。 |
The sparse operation could not be completed because a transaction is active on the file. |
| 0xC019004A | 对创建 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. |
| 0xC019004B | 在由于事务结束而引起浮动的区域对象上尝试 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. |
| 0xC019004C | 由于暂时情况(如资源不足)事务性资源管理器当前无法接受事务处理工作。 |
The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources. |
| 0xC019004D | 事务性资源管理器具有太多无法中止的未决事务处理。事务性资源管理器已经关闭。 |
The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down. |
| 0xC019004E | 由于找不到指定的 Transaction，无法打开。 |
The specified Transaction was unable to be opened, because it was not found. |
| 0xC019004F | 由于找不到指定的 ResourceManager，无法打开。 |
The specified ResourceManager was unable to be opened, because it was not found. |
| 0xC0190050 | 由于找不到指定的 Enlistment，无法打开。 |
The specified Enlistment was unable to be opened, because it was not found. |
| 0xC0190051 | 由于找不到指定的 TransactionManager，无法打开。 |
The specified TransactionManager was unable to be opened, because it was not found. |
| 0xC0190052 | 无法创建或打开指定的对象，原因是其关联的 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. |
| 0xC0190053 | 指定的 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. |
| 0xC0190054 | 用于在此事务对象上创建上级登记的调用无法完成，原因是指定用于登记的事务对象是该事务的下级分支。只有事务的根才能登记为上级。 |
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. |
| 0xC0190055 | 由于关联的事物管理器或资源管理器已关闭，因此句柄不再有效。 |
Because the associated transaction manager or resource manager has been closed, the handle is no longer valid. |
| 0xC0190056 | 由于该文件上的一个事务处于活动状态，压缩操作无法完成。 |
The compression operation could not be completed because a transaction is active on the file. |
| 0xC0190057 | 无法在该上级登记上执行指定的操作，因为未使用 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. |
| 0xC0190058 | 无法执行指定的操作，原因是要记入日志的记录太长。在下列两种情况下可能发生此情形: 在此事务上的登记数量太多，或代表这些登记记录的组合 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. |
| 0xC0190059 | 无法完成链接跟踪操作，因为事务处于活动状态。 |
The link tracking operation could not be completed because a transaction is active. |
| 0xC019005A | 无法在事务中执行此操作。 |
This operation cannot be performed in a transaction. |
| 0xC019005B | 核心事务管理器必须中止或忽略该事务，因为它阻止继续进行操作。 |
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. |
| 0xC019005C | 已提供的 TransactionManager 标识与 TransactionManager 的日志文件中记录的标识不匹配。 |
The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file. |
| 0xC019005D | 此快照操作无法继续，因为无法在事务性资源管理器处于当前状态时将其冻结。请再试一次。 |
This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again. |
| 0xC019005E | 无法使用指定的 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. |
| 0xC019005F | 该事务没有上级登记。 |
The transaction does not have a superior enlistment. |
| 0xC0190060 | 句柄不再正确地与其事务相关联。此句柄可能已在事务资源管理器中打开，而随后该事务资源管理器被强制重新启动。请关闭此句柄并打开新的句柄。 |
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. |
| 0xC0190061 | 无法执行指定操作，因为在事务中未登记资源管理器。 |
The specified operation could not be performed because the resource manager is not enlisted in the transaction. |
| 0xC01A0001 | 日志服务已发现无效的日志扇区。 |
Log service found an invalid log sector. |
| 0xC01A0002 | 日志服务遇到块奇偶校验无效的日志扇区。 |
Log service encountered a log sector with invalid block parity. |
| 0xC01A0003 | 日志服务遇到重映射的日志扇区。 |
Log service encountered a remapped log sector. |
| 0xC01A0004 | 日志服务遇到部分或未完成的日志块。 |
Log service encountered a partial or incomplete log block. |
| 0xC01A0005 | 日志服务遇到错误，原因: 试图访问活动日志范围外的数据。 |
Log service encountered an attempt access data outside the active log range. |
| 0xC01A0006 | 日志服务用户日志排列缓冲区已耗尽。 |
Log service user log marshalling buffers are exhausted. |
| 0xC01A0007 | 日志服务遇到错误，原因: 试图从读取上下文无效的排列区读取。 |
Log service encountered an attempt read from a marshalling area with an invalid read context. |
| 0xC01A0008 | 日志服务遇到无效日志重新启动区域。 |
Log service encountered an invalid log restart area. |
| 0xC01A0009 | 日志服务遇到无效日志块版本。 |
Log service encountered an invalid log block version. |
| 0xC01A000A | 日志服务遇到无效日志块。 |
Log service encountered an invalid log block. |
| 0xC01A000B | 日志服务遇到错误，原因: 试图以无效读取模式读取。 |
Log service encountered an attempt to read the log with an invalid read mode. |
| 0xC01A000D | 日志服务遇到损坏的元数据文件。 |
Log service encountered a corrupted metadata file. |
| 0xC01A000E | 日志服务遇到无法由日志文件系统创建的元数据文件。 |
Log service encountered a metadata file that could not be created by the log file system. |
| 0xC01A000F | 日志服务遇到数据不一致的元数据文件。 |
Log service encountered a metadata file with inconsistent data. |
| 0xC01A0010 | 日志服务遇到对错误地分配或处置保留空间的尝试。 |
Log service encountered an attempt to erroneously allocate or dispose reservation space. |
| 0xC01A0011 | 日志服务无法删除日志文件或文件系统容器。 |
Log service cannot delete log file or file system container. |
| 0xC01A0012 | 日志服务已经达到允许分配给日志文件的容器的上限。 |
Log service has reached the maximum allowable containers allocated to a log file. |
| 0xC01A0013 | 日志服务已尝试后向读取或写入，一直到达日志的开始。 |
Log service has attempted to read or write backwards past the start of the log. |
| 0xC01A0014 | 由于相同类型的策略已经存在，无法安装日志策略。 |
Log policy could not be installed because a policy of the same type is already present. |
| 0xC01A0015 | 该疑问日志策略在请求时尚未安装。 |
Log policy in question was not installed at the time of the request. |
| 0xC01A0016 | 日志上的策略的已安装集无效。 |
The installed set of policies on the log is invalid. |
| 0xC01A0017 | 该疑问日志上的策略阻止完成操作。 |
A policy on the log in question prevented the operation from completing. |
| 0xC01A0018 | 由于日志被存档结尾固定，无法回收日志空间。 |
Log space cannot be reclaimed because the log is pinned by the archive tail. |
| 0xC01A0019 | 日志记录不是日志文件中的记录。 |
Log record is not a record in the log file. |
| 0xC01A001A | 保留的日志记录数或保留的日志记录数的调整无效。 |
Number of reserved log records or the adjustment of the number of reserved log records is invalid. |
| 0xC01A001B | 保留的日志空间或日志空间的调整无效。 |
Reserved log space or the adjustment of the log space is invalid. |
| 0xC01A001C | 活动日志新存档或现有存档的尾部或底部无效。 |
A new or existing archive tail or base of the active log is invalid. |
| 0xC01A001D | 日志空间已用尽。 |
Log space is exhausted. |
| 0xC01A001E | 日志被复用，不允许直接写入物理日志。 |
Log is multiplexed, no direct writes to the physical log is allowed. |
| 0xC01A001F | 由于日志是专用日志，操作失败。 |
The operation failed because the log is a dedicated log. |
| 0xC01A0020 | 操作需要存档上下文。 |
The operation requires an archive context. |
| 0xC01A0021 | 日志存档进行中。 |
Log archival is in progress. |
| 0xC01A0022 | 操作需要长日志，但该日志是极短日志。 |
The operation requires a non-ephemeral log, but the log is ephemeral. |
| 0xC01A0023 | 日志必须至少拥有两个容器，才能读取或写入。 |
The log must have at least two containers before it can be read from or written to. |
| 0xC01A0024 | 日志客户端已经在该流上注册。 |
A log client has already registered on the stream. |
| 0xC01A0025 | 日志客户端尚未在该流上注册。 |
A log client has not been registered on the stream. |
| 0xC01A0026 | 已经请求处理日志满状况。 |
A request has already been made to handle the log full condition. |
| 0xC01A0027 | 日志服务试图读取日志容器时遇到错误。 |
Log service encountered an error when attempting to read from a log container. |
| 0xC01A0028 | 日志服务试图写入日志容器时遇到错误。 |
Log service encountered an error when attempting to write to a log container. |
| 0xC01A0029 | 日志服务试图打开日志容器时遇到错误。 |
Log service encountered an error when attempting open a log container. |
| 0xC01A002A | 日志服务试图执行请求的操作时遇到无效容器状态。 |
Log service encountered an invalid container state when attempting a requested action. |
| 0xC01A002B | 日志服务状态错误，不能执行请求的操作。 |
Log service is not in the correct state to perform a requested action. |
| 0xC01A002C | 由于日志被固定，无法回收日志空间。 |
Log space cannot be reclaimed because the log is pinned. |
| 0xC01A002D | 未能刷新日志元数据。 |
Log metadata flush failed. |
| 0xC01A002E | 日志及其容器上的安全不一致。 |
Security on the log and its containers is inconsistent. |
| 0xC01A002F | 已将记录附加到日志或已进行保留更改，但无法刷新日志。 |
Records were appended to the log or reservation changes were made, but the log could not be flushed. |
| 0xC01A0030 | 由于保留会消耗大部分日志空间，因此已固定该日志。请释放某些保留的记录以增加可用空间。 |
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. |
| 0xC01B00EA | {显示驱动程序停止响应}%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 upload data about this failure to Microsoft. |
| 0xC01C0001 | 筛选器未定义此操作的处理程序。 |
A handler was not defined by the filter for this operation. |
| 0xC01C0002 | 已定义此对象的上下文。 |
A context is already defined for this object. |
| 0xC01C0003 | 异步请求对此操作无效。 |
Asynchronous requests are not valid for this operation. |
| 0xC01C0004 | 筛选器管理器使用内部错误代码来确定是否应将 fastio 操作强制用于 IRP 路径。微筛选器应从不返回此值。 |
Internal error code used by the filter manager to determine if a fastio operation should be forced down the IRP path. Mini-filters should never return this value. |
| 0xC01C0005 | 执行的名称请求无效。此时无法检索请求的名称。 |
An invalid name request was made. The name requested cannot be retrieved at this time. |
| 0xC01C0006 | 此时将此操作发送到工作线程进行进一步处理是不安全的，因为这样会导致系统死锁。 |
Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. |
| 0xC01C0007 | 尝试注册筛选器时，筛选器管理器未初始化。请确保将筛选器管理器加载为驱动程序。 |
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. |
| 0xC01C0008 | 筛选器尚未准备好附加到卷，因为筛选器还未完成初始化(尚未调用 FltStartFiltering)。 |
The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). |
| 0xC01C0009 | 此时筛选器必须清理所有操作特定的上下文，因为从系统中删除其上下文之后，低级驱动程序才能完成此操作。 |
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. |
| 0xC01C000A | 筛选器管理器发生无法恢复的内部错误，因此该操作失败。这通常是因为筛选器从预操作回调中返回了无效的值。 |
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. |
| 0xC01C000B | 正在删除为此操作指定的对象，因此此时无法完成请求的操作。 |
The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. |
| 0xC01C000C | 必须对此类型的上下文使用非分页缓冲池。 |
Non-paged pool must be used for this type of context. |
| 0xC01C000D | 为操作提供了重复的处理程序定义。 |
A duplicate handler definition has been provided for an operation. |
| 0xC01C000E | 回调数据队列已禁用。 |
The callback data queue has been disabled. |
| 0xC01C000F | 此时不要将筛选器附加到卷。 |
Do not attach the filter to the volume at this time. |
| 0xC01C0010 | 此时不要从卷分离筛选器。 |
Do not detach the filter from the volume at this time. |
| 0xC01C0011 | 在指定卷的此高度上已存在实例。 |
An instance already exists at this altitude on the volume specified. |
| 0xC01C0012 | 在指定卷上已存在此名称的实例。 |
An instance already exists with this name on the volume specified. |
| 0xC01C0013 | 系统无法找到指定的筛选器。 |
The system could not find the filter specified. |
| 0xC01C0014 | 系统无法找到指定的卷。 |
The system could not find the volume specified. |
| 0xC01C0015 | 系统无法找到指定的实例。 |
The system could not find the instance specified. |
| 0xC01C0016 | 找不到为给定请求注册的上下文分配定义。 |
No registered context allocation definition was found for the given request. |
| 0xC01C0017 | 注册上下文期间指定了无效的参数。 |
An invalid parameter was specified during context registration. |
| 0xC01C0018 | 在筛选器管理器的名称缓存中找不到请求的名称，无法从文件系统中检索。 |
The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
| 0xC01C0019 | 给定的卷中不存在请求的设备对象。 |
The requested device object does not exist for the given volume. |
| 0xC01C001A | 已装载指定的卷。 |
The specified volume is already mounted. |
| 0xC01C001B | 指定的事务上下文已在事务中登记 |
The specified Transaction Context is already enlisted in a transaction |
| 0xC01C001C | 特定上下文已附加到另一对象 |
The specifiec context is already attached to another object |
| 0xC01C0020 | 不存在等候筛选器回复此消息的程序。 |
No waiter is present for the filter's reply to this message. |
| 0xC01C0023 | 文件系统数据库资源正在使用中。目前无法完成注册。 |
The filesystem database resource is in use. Registration cannot complete at this time. |
| 0xC01D0001 | 无法获取监视器描述符。 |
Monitor descriptor could not be obtained. |
| 0xC01D0002 | 此版本不支持已获取的监视器描述符的格式。 |
Format of the obtained monitor descriptor is not supported by this release. |
| 0xC01D0003 | 获取的监视器描述符的校验和无效。 |
Checksum of the obtained monitor descriptor is invalid. |
| 0xC01D0004 | 监视器描述符包含无效的标准计时块。 |
Monitor descriptor contains an invalid standard timing block. |
| 0xC01D0005 | 为 MSMonitorClass WMI 子类之一进行的 WMI 数据块注册失败。 |
WMI data block registration failed for one of the MSMonitorClass WMI subclasses. |
| 0xC01D0006 | 提供的监视器描述符块已损坏或不包含监视器的详细序列号。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number. |
| 0xC01D0007 | 提供的监视器描述符块已损坏，或者不包含监视器的用户好记的名称。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name. |
| 0xC01D0008 | 在指定的(偏移，大小)区域没有监视器描述符数据。 |
There is no monitor descriptor data at the specified (offset, size) region. |
| 0xC01D0009 | 监视器描述符包含无效的详细计时块。 |
Monitor descriptor contains an invalid detailed timing block. |
| 0xC01D000A | 监视器描述符包含的制造日期无效。 |
Monitor descriptor contains invalid manufacture date. |
| 0xC01E0000 | 创建非托管主分配需要独占模式所有权。 |
Exclusive mode ownership is needed to create unmanaged primary allocation. |
| 0xC01E0001 | 驱动程序需要更多 DMA 缓冲区空间以完成请求的操作。 |
The driver needs more DMA buffer space in order to complete the requested operation. |
| 0xC01E0002 | 指定的显示适配器句柄无效。 |
Specified display adapter handle is invalid. |
| 0xC01E0003 | 指定的显示适配器及其所有状态已重置。 |
Specified display adapter and all of its state has been reset. |
| 0xC01E0004 | 驱动程序堆栈与预期的驱动程序模型不匹配。 |
The driver stack doesn't match the expected driver model. |
| 0xC01E0005 | 已经显示，但导致桌面模式更改 |
Present happened but ended up into the changed desktop mode |
| 0xC01E0006 | 由于桌面封闭，因此无法显示任何内容 |
Nothing to present due to desktop occlusion |
| 0xC01E0007 | 由于拒绝桌面访问，因此无法显示 |
Not able to present due to denial of desktop access |
| 0xC01E0008 | 无法显示颜色转换 |
Not able to present with color convertion |
| 0xC01E0009 | 内核驱动程序检测到它和用户模式驱动程序之间的版本不匹配。 |
The kernel driver detected a version mismatch between it and the user mode driver. |
| 0xC01E000B | 当前重定向被禁用(桌面窗口管理子系统关闭)。 |
Present redirection is disabled (desktop windowing management subsystem is off). |
| 0xC01E000C | 以前的独占 VidPn 源所有者已释放其所有权 |
Previous exclusive VidPn source owner has released its ownership |
| 0xC01E000D | 无法使用 Window DC 进行演示 |
Window DC is not available for presentation |
| 0xC01E000E | 已禁用无窗口显示(桌面窗口管理子系统已关闭)。 |
Windowless present is disabled (desktop windowing management subsystem is off). |
| 0xC01E0100 | 可用视频内存不足，无法完成操作。 |
Not enough video memory available to complete the operation. |
| 0xC01E0101 | 无法探测和锁定分配的基础内存。 |
Couldn't probe and lock the underlying memory of an allocation. |
| 0xC01E0102 | 分配当前正忙。 |
The allocation is currently busy. |
| 0xC01E0103 | 引用的对象已达到最大引用计数，无法进一步引用。 |
An object being referenced has already reached the maximum reference count and can't be referenced any further. |
| 0xC01E0104 | 由于当前的某个现有条件，问题无法解决。应稍后重试解决此问题。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again later. |
| 0xC01E0105 | 由于当前的某个现有条件，问题无法解决。应立即重试解决此问题。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately. |
| 0xC01E0106 | 分配无效。 |
The allocation is invalid. |
| 0xC01E0107 | 当前没有更多取消调配的孔径可用。 |
No more unswizzling aperture are currently available. |
| 0xC01E0108 | 当前分配无法由孔径取消调配。 |
The current allocation can't be unswizzled by an aperture. |
| 0xC01E0109 | 请求失败，因为无法收回已固定的分配。 |
The request failed because a pinned allocation can't be evicted. |
| 0xC01E0110 | 无法从分配的当前段位置使用该分配进行指定的操作。 |
The allocation can't be used from its current segment location for the specified operation. |
| 0xC01E0111 | 锁定的分配无法用于当前的命令缓冲区。 |
A locked allocation can't be used in the current command buffer. |
| 0xC01E0112 | 正在引用的分配已永久关闭。 |
The allocation being referenced has been closed permanently. |
| 0xC01E0113 | 正在引用的分配实例无效。 |
An invalid allocation instance is being referenced. |
| 0xC01E0114 | 正在引用的分配句柄无效。 |
An invalid allocation handle is being referenced. |
| 0xC01E0115 | 正在引用的分配不属于当前设备。 |
The allocation being referenced doesn't belong to the current device. |
| 0xC01E0116 | 指定的分配已丢失其内容。 |
The specified allocation lost its content. |
| 0xC01E0200 | 在给定的设备上检测到 GPU 异常。无法计划该设备。 |
GPU exception is detected on the given device. The device is not able to be scheduled. |
| 0xC01E0300 | 指定的 VidPN 拓扑无效。 |
Specified VidPN topology is invalid. |
| 0xC01E0301 | 指定的 VidPN 拓扑有效，但此型号的显示适配器不支持。 |
Specified VidPN topology is valid but is not supported by this model of the display adapter. |
| 0xC01E0302 | 指定的 VidPN 拓扑有效，但由于其资源的当前分配，此时不受显示适配器支持。 |
Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources. |
| 0xC01E0303 | 指定的 VidPN 句柄无效。 |
Specified VidPN handle is invalid. |
| 0xC01E0304 | 指定的视频显示源无效。 |
Specified video present source is invalid. |
| 0xC01E0305 | 指定的视频显示目标无效。 |
Specified video present target is invalid. |
| 0xC01E0306 | 不支持指定的 VidPN 模态(例如，其中至少两个固定模式的功能无效)。 |
Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional). |
| 0xC01E0308 | 指定的 VidPN 源模式集无效。 |
Specified VidPN source mode set is invalid. |
| 0xC01E0309 | 指定的 VidPN 目标模式集无效。 |
Specified VidPN target mode set is invalid. |
| 0xC01E030A | 指定的视频信号频率无效。 |
Specified video signal frequency is invalid. |
| 0xC01E030B | 指定的视频信号活动区域无效。 |
Specified video signal active region is invalid. |
| 0xC01E030C | 指定的视频信号总区域无效。 |
Specified video signal total region is invalid. |
| 0xC01E0310 | 指定的视频显示源模式无效。 |
Specified video present source mode is invalid. |
| 0xC01E0311 | 指定的视频显示目标模式无效。 |
Specified video present target mode is invalid. |
| 0xC01E0312 | 固定的模式必须保持在 VidPN 的功能模态枚举上的集中。 |
Pinned mode must remain in the set on VidPN's cofunctional modality enumeration. |
| 0xC01E0313 | 指定的视频显示路径已经存在于 VidPN 的拓扑中。 |
Specified video present path is already in VidPN's topology. |
| 0xC01E0314 | 指定的模式已经存在于模式集中。 |
Specified mode is already in the mode set. |
| 0xC01E0315 | 指定的视频显示源集无效。 |
Specified video present source set is invalid. |
| 0xC01E0316 | 指定的视频显示目标集无效。 |
Specified video present target set is invalid. |
| 0xC01E0317 | 指定的视频显示源已经存在于视频显示源集中。 |
Specified video present source is already in the video present source set. |
| 0xC01E0318 | 指定的视频显示目标已经存在于视频显示目标集中。 |
Specified video present target is already in the video present target set. |
| 0xC01E0319 | 指定的 VidPN 显示路径无效。 |
Specified VidPN present path is invalid. |
| 0xC01E031A | 微型端口没有对指定 VidPN 的拓扑的增量的建议。 |
Miniport has no recommendation for augmentation of the specified VidPN's topology. |
| 0xC01E031B | 指定的监视器频率范围集无效。 |
Specified monitor frequency range set is invalid. |
| 0xC01E031C | 指定的监视器频率范围无效。 |
Specified monitor frequency range is invalid. |
| 0xC01E031D | 指定的频率范围不在指定的监视器频率范围集中。 |
Specified frequency range is not in the specified monitor frequency range set. |
| 0xC01E031F | 指定的频率范围已经存在于指定的监视器频率范围集中。 |
Specified frequency range is already in the specified monitor frequency range set. |
| 0xC01E0320 | 指定的模式集已经过时。请重新获取新的模式集。 |
Specified mode set is stale. Please reacquire the new mode set. |
| 0xC01E0321 | 指定的监视器源模式集无效。 |
Specified monitor source mode set is invalid. |
| 0xC01E0322 | 指定的监视器源模式无效。 |
Specified monitor source mode is invalid. |
| 0xC01E0323 | 关于在当前显示适配器配置下提供有效 VidPN 的请求，微型端口无任何建议。 |
Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration. |
| 0xC01E0324 | 集中的另一模式已经在使用指定模式的 ID。 |
ID of the specified mode is already used by another mode in the set. |
| 0xC01E0325 | 系统无法确定显示适配器和与其连接的监视器都支持的模式。 |
System failed to determine a mode that is supported by both the display adapter and the monitor connected to it. |
| 0xC01E0326 | 视频显示目标的数目必须大于或等于视频显示源的数目。 |
Number of video present targets must be greater than or equal to the number of video present sources. |
| 0xC01E0327 | 指定的显示路径不在 VidPN 的拓扑中。 |
Specified present path is not in VidPN's topology. |
| 0xC01E0328 | 显示适配器必须至少有一个视频显示源。 |
Display adapter must have at least one video present source. |
| 0xC01E0329 | 显示适配器必须至少有一个视频显示目标。 |
Display adapter must have at least one video present target. |
| 0xC01E032A | 指定的监视器描述符集无效。 |
Specified monitor descriptor set is invalid. |
| 0xC01E032B | 指定的监视器描述符无效。 |
Specified monitor descriptor is invalid. |
| 0xC01E032C | 指定的描述符不在指定的监视器描述符集中。 |
Specified descriptor is not in the specified monitor descriptor set. |
| 0xC01E032D | 指定的描述符已经存在于指定的监视器描述符集中。 |
Specified descriptor is already in the specified monitor descriptor set. |
| 0xC01E032E | 集中的另一描述符已经在使用指定监视器描述符的 ID。 |
ID of the specified monitor descriptor is already used by another descriptor in the set. |
| 0xC01E032F | 指定的视频显示目标子集类型无效。 |
Specified video present target subset type is invalid. |
| 0xC01E0330 | 如界面语义所定义，两个或多个指定的资源彼此不相关。 |
Two or more of the specified resources are not related to each other, as defined by the interface semantics. |
| 0xC01E0331 | 集中的另一源已经在使用指定视频显示源的 ID。 |
ID of the specified video present source is already used by another source in the set. |
| 0xC01E0332 | 集中的另一目标已经在使用指定视频现有目标的 ID。 |
ID of the specified video present target is already used by another target in the set. |
| 0xC01E0333 | 指定的 VidPN 源无法使用，因为没有可用的 VidPN 目标与其连接。 |
Specified VidPN source cannot be used because there is no available VidPN target to connect it to. |
| 0xC01E0334 | 新到的监视器无法关联显示适配器。 |
Newly arrived monitor could not be associated with a display adapter. |
| 0xC01E0335 | 问题中的显示适配器没有关联的 VidPN 管理器。 |
Display adapter in question does not have an associated VidPN manager. |
| 0xC01E0336 | 问题中的显示适配器的 VidPN 管理器没有活动的 VidPN。 |
VidPN manager of the display adapter in question does not have an active VidPN. |
| 0xC01E0337 | 指定的 VidPN 拓扑已过时。请重新获取新的拓扑。 |
Specified VidPN topology is stale. Please reacquire the new topology. |
| 0xC01E0338 | 指定的视频显示目标上未连接监视器。 |
There is no monitor connected on the specified video present target. |
| 0xC01E0339 | 指定的源不是指定的 VidPN 拓扑的一部分。 |
Specified source is not part of the specified VidPN's topology. |
| 0xC01E033A | 指定的主表面大小无效。 |
Specified primary surface size is invalid. |
| 0xC01E033B | 指定的可见区域大小无效。 |
Specified visible region size is invalid. |
| 0xC01E033C | 指定的步幅无效。 |
Specified stride is invalid. |
| 0xC01E033D | 指定的像素格式无效。 |
Specified pixel format is invalid. |
| 0xC01E033E | 指定的颜色基础无效。 |
Specified color basis is invalid. |
| 0xC01E033F | 指定的像素值访问模式无效。 |
Specified pixel value access mode is invalid. |
| 0xC01E0340 | 所指定目标不是所指定 VidPN 的拓扑的一部分。 |
Specified target is not part of the specified VidPN's topology. |
| 0xC01E0341 | 无法获取显示模式管理界面。 |
Failed to acquire display mode management interface. |
| 0xC01E0342 | 指定的 VidPN 源已经由 DMM 客户端拥有，在该客户端将其释放之前，无法使用。 |
Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it. |
| 0xC01E0343 | 指定的 VidPN 处于活动中，无法访问。 |
Specified VidPN is active and cannot be accessed. |
| 0xC01E0344 | 指定的 VidPN 显示路径重要性顺序无效。 |
Specified VidPN present path importance ordinal is invalid. |
| 0xC01E0345 | 指定的 VidPN 显示路径内容规格转换无效。 |
Specified VidPN present path content geometry transformation is invalid. |
| 0xC01E0346 | 指定的内容规格转换在相应的 VidPN 显示路径中不受支持。 |
Specified content geometry transformation is not supported on the respective VidPN present path. |
| 0xC01E0347 | 指定的伽马校正无效。 |
Specified gamma ramp is invalid. |
| 0xC01E0348 | 在各自的 VidPN 显示路径上不支持指定的伽马校正。 |
Specified gamma ramp is not supported on the respective VidPN present path. |
| 0xC01E0349 | 多示例在相应的 VidPN 显示路径中不受支持。 |
Multi-sampling is not supported on the respective VidPN present path. |
| 0xC01E034A | 指定的模式不在指定的模式集中。 |
Specified mode is not in the specified mode set. |
| 0xC01E034D | 指定的 VidPN 拓扑建议原因无效。 |
Specified VidPN topology recommendation reason is invalid. |
| 0xC01E034E | 指定的 VidPN 显示路径内容类型无效。 |
Specified VidPN present path content type is invalid. |
| 0xC01E034F | 指定的 VidPN 显示路径副本保护类型无效。 |
Specified VidPN present path copy protection type is invalid. |
| 0xC01E0350 | 给定的 VidPN 源/目标在任何给定的时间最多可以存在一个未分配的模式集。 |
No more than one unassigned mode set can exist at any given time for a given VidPN source/target. |
| 0xC01E0352 | 指定的扫描行排序类型无效。 |
Specified scanline ordering type is invalid. |
| 0xC01E0353 | 指定的 VidPN 不允许拓扑更改。 |
Topology changes are not allowed for the specified VidPN. |
| 0xC01E0354 | 所有可用的重要性序号已用于指定的拓扑。 |
All available importance ordinals are already used in specified topology. |
| 0xC01E0355 | 指定的主表面具有与当前主表面不同的专用格式属性 |
Specified primary surface has a different private format attribute than the current primary surface |
| 0xC01E0356 | 指定的模式修剪算法无效 |
Specified mode pruning algorithm is invalid |
| 0xC01E0357 | 指定的监视器原始功能无效。 |
Specified monitor capability origin is invalid. |
| 0xC01E0358 | 指定的监视器频率范围限制无效。 |
Specified monitor frequency range constraint is invalid. |
| 0xC01E0359 | 现有路径的数量已达到支持的最大数量。 |
Maximum supported number of present paths has been reached. |
| 0xC01E035A | 对于指定的 VidPN 拓扑的指定源，微型端口请求取消其增量。 |
Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology. |
| 0xC01E035B | 未识别指定的客户端类型。 |
Specified client type was not recognized. |
| 0xC01E035C | 此适配器上未设置客户端 VidPN (例如，此适配器上没有发生任何在用户模式下启动的模式更改)。 |
Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet). |
| 0xC01E0400 | 指定的显示适配器子设备已经具有与其连接的外部设备。 |
Specified display adapter child device already has an external device connected to it. |
| 0xC01E0401 | 指定的显示适配器子设备不支持描述符暴露。 |
Specified display adapter child device does not support descriptor exposure. |
| 0xC01E0430 | 显示适配器未链接到任何其他适配器。 |
The display adapter is not linked to any other adapters. |
| 0xC01E0431 | 尚未枚举链接配置中的主导适配器。 |
Lead adapter in a linked configuration was not enumerated yet. |
| 0xC01E0432 | 尚未枚举链接的配置中的某些链适配器。 |
Some chain adapters in a linked configuration were not enumerated yet. |
| 0xC01E0433 | 由于未知故障，链接的适配器的链启动未准备就绪。 |
The chain of linked adapters is not ready to start because of an unknown failure. |
| 0xC01E0434 | 当链链接尚未启动时，尝试启动前导链接显示适配器。 |
An attempt was made to start a lead link display adapter when the chain links were not started yet. |
| 0xC01E0435 | 当链链接断电时，尝试给前导链接显示适配器通电。 |
An attempt was made to power up a lead link display adapter when the chain links were powered down. |
| 0xC01E0436 | 发现适配器链接处于不一致状态。不是所有适配器都处于预期的 PNP/电源状态。 |
The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state. |
| 0xC01E0438 | 尝试启动的驱动程序与 POSTed 显示适配器的驱动程序不同。 |
The driver trying to start is not the same as the driver for the POSTed display adapter. |
| 0xC01E043B | 正在尝试的操作要求显示适配器处于静止状态。 |
An operation is being attempted that requires the display adapter to be in a quiescent state. |
| 0xC01E0500 | 驱动程序不支持 OPM。 |
The driver does not support OPM. |
| 0xC01E0501 | 驱动程序不支持 COPP。 |
The driver does not support COPP. |
| 0xC01E0502 | 驱动程序不支持 UAB。 |
The driver does not support UAB. |
| 0xC01E0503 | 指定的加密参数无效。 |
The specified encrypted parameters are invalid. |
| 0xC01E0505 | 传递到此函数的 GDI 显示设备没有任何活动的受保护的输出。 |
The GDI display device passed to this function does not have any active protected outputs. |
| 0xC01E050B | 内部错误导致此操作失败。 |
An internal error caused an operation to fail. |
| 0xC01E050C | 函数失败，因为调用方传递进无效的 OPM 用户模式句柄。 |
The function failed because the caller passed in an invalid OPM user mode handle. |
| 0xC01E050E | 无法返回证书，因为传递到函数的证书缓冲区过小。 |
A certificate could not be returned because the certificate buffer passed to the function was too small. |
| 0xC01E050F | DxgkDdiOpmCreateProtectedOutput 函数无法创建受保护的输出，因为视频显示目标处于跨区模式。 |
The DxgkDdiOpmCreateProtectedOutput function could not create a protected output because the Video Present Target is in spanning mode. |
| 0xC01E0510 | DxgkDdiOpmCreateProtectedOutput 函数无法创建受保护的输出，因为视频显示目标处于影院模式。 |
The DxgkDdiOpmCreateProtectedOutput function could not create a protected output because the Video Present Target is in theater mode. |
| 0xC01E0511 | 函数出现错误，原因是显示适配器的硬件功能性扫描验证图形硬件失败。 |
The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware. |
| 0xC01E0512 | 传递给此函数的“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. |
| 0xC01E0513 | 受保护的输出无法启用高带宽数字内容保护系统(HDCP)，因为它不支持该系统。 |
The protected output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP. |
| 0xC01E0514 | 受保护的输出无法启用模拟复制保护(ACP)，因为它不支持该保护方式。 |
The protected output cannot enable Analogue Copy Protection (ACP) because it does not support ACP. |
| 0xC01E0515 | 受保护的输出无法启用内容生成管理系统模拟保护技术(CGMS-A)，因为它不支持该技术。 |
The protected output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A. |
| 0xC01E0516 | DxgkDdiOPMGetInformation 函数无法返回所使用 SRM 的版本，原因是应用程序始终没有成功将 SRM 传递到受保护的输出。 |
The DxgkDdiOPMGetInformation function cannot return the version of the SRM being used because the application never successfully passed an SRM to the protected output. |
| 0xC01E0517 | DxgkDdiOPMConfigureProtectedOutput 函数无法启用指定的输出保护技术，原因是输出的屏幕分辨率太高。 |
The DxgkDdiOPMConfigureProtectedOutput function cannot enable the specified output protection technology because the output's screen resolution is too high. |
| 0xC01E0518 | DxgkDdiOPMConfigureProtectedOutput 函数无法启用 HDCP，因为显示适配器的 HDCP 硬件已被其他物理输出使用。 |
The DxgkDdiOPMConfigureProtectedOutput function cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs. |
| 0xC01E051A | 操作系统异步毁坏了此 OPM 保护的输出，原因是操作系统的状态已更改。发生此错误的原因通常为: 与此受保护的输出相关联的监视器 PDO 已移除；与此受保护的输出相关联的监视器 PDO 已停用；或受保护的输出的会话已成为非控制台会话。 |
The operating system asynchronously destroyed this OPM protected output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this protected output was removed, the monitor PDO associated with this protected output was stopped, or the protected output's session became a non-console session. |
| 0xC01E051C | DxgkDdiOPMGetCOPPCompatibleInformation、DxgkDdiOPMGetInformation 或 DxgkDdiOPMConfigureProtectedOutput 函数失败。当调用程序尝试使用 COPP 特定命令，而受保护的输出仅具有 OPM 语义时返回该错误。 |
Either the DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned when the caller tries to use a COPP specific command while the protected output has OPM semantics only. |
| 0xC01E051D | 如果传入的序列号不是期望的序列号或者传入的 OMAC 值无效，则 DxgkDdiOPMGetInformation 和 DxgkDdiOPMGetCOPPCompatibleInformation 函数返回此错误代码。 |
The DxgkDdiOPMGetInformation and DxgkDdiOPMGetCOPPCompatibleInformation functions return this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid. |
| 0xC01E051E | 函数因显示驱动程序内部发生意外错误而失败。 |
The function failed because an unexpected error occurred inside of a display driver. |
| 0xC01E051F | DxgkDdiOPMGetCOPPCompatibleInformation、DxgkDdiOPMGetInformation 或 DxgkDdiOPMConfigureProtectedOutput 函数失败。当调用程序尝试使用 OPM 特定的命令，而受保护的输出仅具有 COPP 语义时返回该错误。 |
Either the DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned when the caller tries to use an OPM specific command while the protected output has COPP semantics only. |
| 0xC01E0520 | 如果显示驱动程序不支持 DXGKMDT_OPM_GET_ACP_AND_CGMSA_SIGNALING 和 DXGKMDT_OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs，则 DxgkDdiOPMGetCOPPCompatibleInformation 和 DxgkDdiOPMConfigureProtectedOutput 函数返回此错误。 |
The DxgkDdiOPMGetCOPPCompatibleInformation and DxgkDdiOPMConfigureProtectedOutput functions return this error if the display driver does not support the DXGKMDT_OPM_GET_ACP_AND_CGMSA_SIGNALING and DXGKMDT_OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs. |
| 0xC01E0521 | 如果传入的序列号不是期望的序列号或者传入的 OMAC 值无效，则 DxgkDdiOPMConfigureProtectedOutput 函数返回此错误代码。 |
The DxgkDdiOPMConfigureProtectedOutput 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. |
| 0xC01E0580 | 连接到指定视频输出的监视器没有 I2C 总线。 |
The monitor connected to the specified video output does not have an I2C bus. |
| 0xC01E0581 | I2C 总线上的设备没有指定的地址。 |
No device on the I2C bus has the specified address. |
| 0xC01E0582 | 将数据传输到 I2C 总线上的设备时出错。 |
An error occurred while transmitting data to the device on the I2C bus. |
| 0xC01E0583 | 从 I2C 总线上的设备接收数据时出错。 |
An error occurred while receiving data from the device on the I2C bus. |
| 0xC01E0584 | 该监视器不支持指定的 VCP 代码。 |
The monitor does not support the specified VCP code. |
| 0xC01E0585 | 从监视器接收到的数据无效。 |
The data received from the monitor is invalid. |
| 0xC01E0586 | 函数失败，原因是操作系统使用 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. |
| 0xC01E0587 | 监视器返回 DDC/CI 功能字符串，该字符串不符合 ACCESS.bus 3.0、DDC/CI 1.1 或 MCCS 2 修订版 1 规范。 |
A monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification. |
| 0xC01E0589 | 操作失败，原因是 DDC/CI 消息的命令字段中的值无效。 |
An operation failed because a DDC/CI message had an invalid value in its command field. |
| 0xC01E058A | 由于 DDC/CI 消息的字段长度包含无效的值，因此出现错误。 |
An error occurred because the field length of a DDC/CI message contained an invalid value. |
| 0xC01E058B | 出现错误，原因是 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. |
| 0xC01E058C | 由于向函数传递了无效的监视器句柄，因此该函数失败。 |
This function failed because an invalid monitor handle was passed to it. |
| 0xC01E058D | 操作系统异步毁坏了与此句柄相对应的监视器，原因是操作系统的状态已更改。发生此错误的原因通常为: 与此句柄相关联的监视器 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. |
| 0xC01E05E0 | 仅当程序在本地控制台会话中运行时，才能使用此函数。如果程序在远程桌面会话或终端服务器会话中运行，则无法使用此函数。 |
This function can only be used if a program is running in the local console session. It cannot be used if a program is running on a remote desktop session or on a terminal server session. |
| 0xC01E05E1 | 该函数无法找到与指定的 GDI 显示设备名称相对应的实际 GDI 显示设备。 |
This function cannot find an actual GDI display device which corresponds to the specified GDI display device name. |
| 0xC01E05E2 | 函数失败，原因是未将指定的 GDI 显示设备连接到 Windows 桌面。 |
The function failed because the specified GDI display device was not attached to the Windows desktop. |
| 0xC01E05E3 | 该函数不支持 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. |
| 0xC01E05E4 | 函数失败，原因是向其传递了无效的指针参数。如果指针参数为 NULL、指向无效地址、指向内核模式地址或没有正确对齐，指针参数将无效。 |
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, it points to an invalid address, it points to a kernel mode address or it is not correctly aligned. |
| 0xC01E05E5 | 此函数失败，因为传递到该函数的 GDI 设备没有任何与其关联的监视器。 |
This function failed because the GDI device passed to it did not have any monitors associated with it. |
| 0xC01E05E6 | 传递到函数的数组无法包含该函数必须将其复制到数组的所有数据。 |
An array passed to the function cannot hold all of the data that the function must copy into the array. |
| 0xC01E05E8 | 函数失败，因为当前会话正在更改其类型。当前会话正在更改其类型时，无法调用该函数。当前存在三种类型的会话: 控制台、断开连接和远程。 |
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. |
| 0xC0210000 | 此卷已被 BitLocker 驱动器加密锁定。 |
This volume is locked by BitLocker Drive Encryption. |
| 0xC0210001 | 该卷未加密，没有可用的密钥。 |
The volume is not encrypted, no key is available. |
| 0xC0210002 | 加密卷的控制块无效。 |
The control block for the encrypted volume is not valid. |
| 0xC0210003 | 卷上没有足够的可用空间，无法对其进行加密。 |
The volume cannot be encrypted because it does not have enough free space. |
| 0xC0210004 | 无法加密卷，因为不支持该文件系统。 |
The volume cannot be encrypted because the file system is not supported. |
| 0xC0210005 | 文件系统大小大于分区表中的分区大小。 |
The file system size is larger than the partition size in the partition table. |
| 0xC0210006 | 文件系统未扩展到卷的未尾。 |
The file system does not extend to the end of the volume. |
| 0xC0210007 | 在卷上装入文件系统时，无法执行此操作。 |
This operation cannot be performed while a file system is mounted on the volume. |
| 0xC0210008 | 此版本的 Windows 不包含 BitLocker 驱动器加密。 |
BitLocker Drive Encryption is not included with this version of Windows. |
| 0xC0210009 | 在当前卷的状态中不允许请求的操作。 |
Requested action not allowed in the current volume state. |
| 0xC021000A | 提供的数据格式错误。 |
Data supplied is malformed. |
| 0xC021000B | 此卷未绑定到该系统。 |
The volume is not bound to the system. |
| 0xC021000C | 此卷不是数据卷。 |
That volume is not a data volume. |
| 0xC021000D | 转换卷时读取操作失败。 |
A read operation failed while converting the volume. |
| 0xC021000E | 转换卷时写入操作失败。 |
A write operation failed while converting the volume. |
| 0xC021000F | 另一线程已更新加密卷的控制块。请重试。 |
The control block for the encrypted volume was updated by another thread. Try again. |
| 0xC0210010 | 加密算法不支持该卷的扇区大小。 |
The encryption algorithm does not support the sector size of that volume. |
| 0xC0210011 | BitLocker 恢复身份验证失败。 |
BitLocker recovery authentication failed. |
| 0xC0210012 | 此卷不是操作系统卷。 |
That volume is not the OS volume. |
| 0xC0210013 | 无法从外部介质读取 BitLocker 启动密钥或恢复密码。 |
The BitLocker startup key or recovery password could not be read from external media. |
| 0xC0210014 | BitLocker 启动密钥或恢复密码文件损坏或无效。 |
The BitLocker startup key or recovery password file is corrupt or invalid. |
| 0xC0210015 | 无法从启动密钥或恢复密码获取 BitLocker 加密密钥。 |
The BitLocker encryption key could not be obtained from the startup key or recovery password. |
| 0xC0210016 | 受信任的平台模块(TPM)已禁用。 |
The Trusted Platform Module (TPM) is disabled. |
| 0xC0210017 | 受信任的平台模块(TPM)的存储根密钥(SRK)的授权数据不为零。 |
The authorization data for the Storage Root Key (SRK) of the Trusted Platform Module (TPM) is not zero. |
| 0xC0210018 | 系统启动信息已更改，或者受信任的平台模块(TPM)已锁定在计算机重新启动之前对 BitLocker 加密密钥的访问权限。 |
The system boot information changed or the Trusted Platform Module (TPM) locked out access to BitLocker encryption keys until the computer is restarted. |
| 0xC0210019 | 无法从受信任的平台模块(TPM)获取 BitLocker 加密密钥。 |
The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM). |
| 0xC021001A | 无法从受信任的平台模块(TPM)和 PIN 获取 BitLocker 加密密钥。 |
The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and PIN. |
| 0xC021001B | 启动应用程序哈希与启用 BitLocker 时计算得出的哈希不符。 |
A boot application hash does not match the hash computed when BitLocker was turned on. |
| 0xC021001C | 由于 BitLocker 已启用，因此启动配置数据(BCD)设置不受支持或者被更改。 |
The Boot Configuration Data (BCD) settings are not supported or have changed since BitLocker was enabled. |
| 0xC021001D | 已启用启动调试。请运行 bcdedit 将其关闭。 |
Boot debugging is enabled. Run bcdedit to turn it off. |
| 0xC021001E | 无法获取 BitLocker 加密密钥。 |
The BitLocker encryption key could not be obtained. |
| 0xC021001F | 元数据磁盘区域指针不正确。 |
The metadata disk region pointer is incorrect. |
| 0xC0210020 | 元数据的备份副本已过期。 |
The backup copy of the metadata is out of date. |
| 0xC0210021 | 由于需要重新启动系统，因此未执行任何操作。 |
No action was taken as a system reboot is required. |
| 0xC0210022 | 由于 BitLocker 驱动器加密处于 RAW 访问模式，未进行任何操作。 |
No action was taken as BitLocker Drive Encryption is in RAW access mode. |
| 0xC0210023 | 此卷的 BitLocker 驱动器加密无法进入原始访问模式。 |
BitLocker Drive Encryption cannot enter raw access mode for this volume. |
| 0xC0210024 | 无法从操作系统卷中获得自动解锁主密钥。请使用 BitLocker WMI 接口重试该操作。 |
The auto-unlock master key was not available from the operating system volume. Retry the operation using the BitLocker WMI interface. |
| 0xC0210025 | 系统固件未能在重启时清除系统内存。 |
The system firmware failed to enable clearing of system memory on reboot. |
| 0xC0210026 | 此版本的 Windows 中不包含 BitLocker 驱动器加密的此项功能。 |
This feature of BitLocker Drive Encryption is not included with this version of Windows. |
| 0xC0210027 | 组策略不允许关闭漫游数据卷上的 BitLocker 驱动器加密。 |
Group policy does not permit turning off BitLocker Drive Encryption on roaming data volumes. |
| 0xC0210028 | Bitlocker 驱动器加密无法从中止的转换中恢复。这可能是由于所有转换日志都被损坏或者介质具有写保护。 |
Bitlocker Drive Encryption failed to recover from aborted conversion. This could be due to either all conversion logs being corrupted or the media being write-protected. |
| 0xC0210029 | 请求的虚拟化大小过大。 |
The requested virtualization size is too big. |
| 0xC021002A | 存储在此驱动器上的管理信息包含未知类型。如果你使用的是旧版本的 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. |
| 0xC0210030 | 驱动器太小，无法使用 BitLocker 驱动器加密进行保护。 |
The drive is too small to be protected using BitLocker Drive Encryption. |
| 0xC0210031 | 无法从受信任的平台模块(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. |
| 0xC0210032 | 在精简预配的存储上，BitLocker 驱动器加密仅支持“仅加密已用空间”。 |
BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage. |
| 0xC0210033 | BitLocker 驱动器加密不支持在精简预配的存储上擦除可用空间。 |
BitLocker Drive Encryption does not support wiping free space on thin provisioned storage. |
| 0xC0210034 | 只能从指定的 CSV 卷的协调器节点执行此命令。 |
This command can only be performed from the coordinator node for the specified CSV volume. |
| 0xC0210035 | 当卷是群集的一部分时，无法在卷上执行此命令。 |
This command cannot be performed on a volume when it is part of a cluster. |
| 0xC0210036 | 在磁盘加密或解密过程中，无法升级 BitLocker。 |
BitLocker cannot be upgraded during disk encryption or decryption. |
| 0xC0210037 | 当前未进行擦除可用空间的操作。 |
Wipe of free space is not currently taking place. |
| 0xC0210038 | 你的计算机不支持基于硬件的 BitLocker 加密。请与计算机制造商联系，以获取固件更新。 |
Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates. |
| 0xC0210039 | 已禁用安全启动。必须重新启用安全启动或者必须暂停 BitLocker，Windows 才能正常启动。 |
Secure Boot has been disabled. Either Secure Boot must be re-enabled, or BitLocker must be suspended for Windows to start normally. |
| 0xC021003A | 安全启动策略已被意外更改。 |
Secure Boot policy has unexpectedly changed. |
| 0xC021003B | 由于过多次输入了错误的密码，因此已触发设备锁定。 |
Device Lock has been triggered due to too many incorrect password attempts. |
| 0xC021003C | 设备加密删除被阻止，因为要扩展的卷超过其原始容量。 |
Device encryption removal is blocked due to volume being extended beyond its original size. |
| 0xC021003D | 不支持此操作，因为该驱动器并不通过设备加密来自动管理。 |
This action isn't supported because this drive isn't automatically managed with device encryption. |
| 0xC021003E | 在此驱动器上 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. |
| 0xC021003F | 在下次重新启动以前，将无法在此驱动器上暂停 BitLocker。 |
BitLocker can't be suspended on this drive until the next restart. |
| 0xC0210040 | BitLocker 驱动器加密策略不允许对受保护的 OS 卷进行 KSR 操作。 |
BitLocker Drive Encryption policy does not allow KSR operation with protected OS volume. |
| 0xC0220001 | 标注不存在。 |
The callout does not exist. |
| 0xC0220002 | 筛选条件不存在。 |
The filter condition does not exist. |
| 0xC0220003 | 筛选器不存在。 |
The filter does not exist. |
| 0xC0220004 | 层不存在。 |
The layer does not exist. |
| 0xC0220005 | 提供程序不存在。 |
The provider does not exist. |
| 0xC0220006 | 提供程序上下文不存在。 |
The provider context does not exist. |
| 0xC0220007 | 子层不存在。 |
The sublayer does not exist. |
| 0xC0220008 | 对象不存在。 |
The object does not exist. |
| 0xC0220009 | 具有该 GUID 或 LUID 的对象已经存在。 |
An object with that GUID or LUID already exists. |
| 0xC022000A | 其他对象引用了该对象，因此无法将其删除。 |
The object is referenced by other objects so cannot be deleted. |
| 0xC022000B | 不允许从动态会话内进行调用。 |
The call is not allowed from within a dynamic session. |
| 0xC022000C | 调用是从错误的会话进行的，因此无法完成。 |
The call was made from the wrong session so cannot be completed. |
| 0xC022000D | 必须从显式事务内进行该调用。 |
The call must be made from within an explicit transaction. |
| 0xC022000E | 不允许从显式事务内进行该调用。 |
The call is not allowed from within an explicit transaction. |
| 0xC022000F | 显式事务已经强制取消。 |
The explicit transaction has been forcibly cancelled. |
| 0xC0220010 | 会话已取消。 |
The session has been cancelled. |
| 0xC0220011 | 不允许从只读事务内进行调用。 |
The call is not allowed from within a read-only transaction. |
| 0xC0220012 | 等待获取事务锁定时调用超时。 |
The call timed out while waiting to acquire the transaction lock. |
| 0xC0220013 | 网络诊断事件的集合已禁用。 |
Collection of network diagnostic events is disabled. |
| 0xC0220014 | 指定的层不支持该操作。 |
The operation is not supported by the specified layer. |
| 0xC0220015 | 仅有内核模式的调用方允许使用该调用。 |
The call is allowed for kernel-mode callers only. |
| 0xC0220016 | 该调用尝试将两个生存时间不兼容的对象相互关联。 |
The call tried to associate two objects with incompatible lifetimes. |
| 0xC0220017 | 此对象为内置对象，因此无法删除。 |
The object is built in so cannot be deleted. |
| 0xC0220018 | 已达到标注的最大数目。 |
The maximum number of callouts has been reached. |
| 0xC0220019 | 无法发送该通知，因为消息队列已达到其最大容量。 |
A notification could not be delivered because a message queue is at its maximum capacity. |
| 0xC022001A | 流量参数与安全关联上下文参数不匹配。 |
The traffic parameters do not match those for the security association context. |
| 0xC022001B | 当前安全关联状态不允许使用该调用。 |
The call is not allowed for the current security association state. |
| 0xC022001C | 所需的指针为 Null。 |
A required pointer is null. |
| 0xC022001D | 枚举器无效。 |
An enumerator is not valid. |
| 0xC022001E | 标志字段包含无效值。 |
The flags field contains an invalid value. |
| 0xC022001F | 网络掩码无效。 |
A network mask is not valid. |
| 0xC0220020 | FWP_RANGE 无效。 |
An FWP_RANGE is not valid. |
| 0xC0220021 | 时间间隔无效。 |
The time interval is not valid. |
| 0xC0220022 | 必须至少包含一个元素的数组的长度为零。 |
An array that must contain at least one element is zero length. |
| 0xC0220023 | displayData.name 字段不能为 Null。 |
The displayData.name field cannot be null. |
| 0xC0220024 | 该操作类型不是筛选器允许的操作类型。 |
The action type is not one of the allowed action types for a filter. |
| 0xC0220025 | 筛选器权重无效。 |
The filter weight is not valid. |
| 0xC0220026 | 筛选条件包含与操作数不兼容的匹配类型。 |
A filter condition contains a match type that is not compatible with the operands. |
| 0xC0220027 | FWP_VALUE 或 FWPM_CONDITION_VALUE 类型错误。 |
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. |
| 0xC0220028 | 整数值超出允许的范围。 |
An integer value is outside the allowed range. |
| 0xC0220029 | 保留的字段为非零值。 |
A reserved field is non-zero. |
| 0xC022002A | 筛选器在单个字段上不能包含多个条件运算。 |
A filter cannot contain multiple conditions operating on a single field. |
| 0xC022002B | 策略不能多次包含同一键控模块。 |
A policy cannot contain the same keying module more than once. |
| 0xC022002C | 操作类型与层不兼容。 |
The action type is not compatible with the layer. |
| 0xC022002D | 操作类型与子层不兼容。 |
The action type is not compatible with the sublayer. |
| 0xC022002E | 原始上下文或提供程序上下文与层不兼容。 |
The raw context or the provider context is not compatible with the layer. |
| 0xC022002F | 原始上下文或提供程序上下文与标注不兼容。 |
The raw context or the provider context is not compatible with the callout. |
| 0xC0220030 | 身份验证方法与策略类型不兼容。 |
The authentication method is not compatible with the policy type. |
| 0xC0220031 | Diffie-Hellman 组与策略类型不兼容。 |
The Diffie-Hellman group is not compatible with the policy type. |
| 0xC0220032 | IKE 策略不能包含扩展模式策略。 |
An IKE policy cannot contain an Extended Mode policy. |
| 0xC0220033 | 枚举模板或订阅将不匹配任何对象。 |
The enumeration template or subscription will never match any objects. |
| 0xC0220034 | 提供程序上下文类型错误。 |
The provider context is of the wrong type. |
| 0xC0220035 | 参数错误。 |
The parameter is incorrect. |
| 0xC0220036 | 已达到子层的最大数目。 |
The maximum number of sublayers has been reached. |
| 0xC0220037 | 标注的通知功能返回了一个错误。 |
The notification function for a callout returned an error. |
| 0xC0220038 | IPSec 身份验证转换无效。 |
The IPsec authentication transform is not valid. |
| 0xC0220039 | IPSec 密码转换无效。 |
The IPsec cipher transform is not valid. |
| 0xC022003A | IPSec 密码转换与策略不兼容。 |
The IPsec cipher transform is not compatible with the policy. |
| 0xC022003B | IPSec 转换类型的组合无效。 |
The combination of IPsec transform types is not valid. |
| 0xC022003C | 策略不能多次包含同一个身份验证方法。 |
A policy cannot contain the same auth method more than once. |
| 0xC022003D | 隧道终结点配置无效。 |
A tunnel endpoint configuration is invalid. |
| 0xC022003E | WFP MAC 层未就绪。 |
The WFP MAC Layers are not ready. |
| 0xC022003F | 已经注册具有密钥识别功能的密钥管理器 |
A key manager capable of key dictation is already registered |
| 0xC0220040 | 密钥管理器指示密钥无效 |
A key manager dictated invalid keys |
| 0xC0220041 | BFE IPsec 连接跟踪已禁用。 |
The BFE IPsec Connection Tracking is disabled. |
| 0xC0220042 | DNS 名称无效。 |
The DNS name is invalid. |
| 0xC0220043 | 由于其他配置设置，引擎选项仍处于启用状态。 |
The engine option is still enabled due to other configuration settings. |
| 0xC0220044 | IKEEXT 服务未运行。只有在计算机已应用 IPSec 策略时，此服务才会运行。 |
The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine. |
| 0xC0220100 | TCP/IP 堆栈未准备就绪。 |
The TCP/IP stack is not ready. |
| 0xC0220101 | 注入句柄正由另一个线程关闭。 |
The injection handle is being closed by another thread. |
| 0xC0220102 | 注入句柄停滞。 |
The injection handle is stale. |
| 0xC0220103 | 无法挂起分类。 |
The classify cannot be pended. |
| 0xC0220104 | 数据包应丢弃，不应发送任何 ICMP。 |
The packet should be dropped, no ICMP should be sent. |
| 0xC0230002 | 到网络接口的绑定已关闭。 |
The binding to the network interface is being closed. |
| 0xC0230004 | 指定的版本无效。 |
An invalid version was specified. |
| 0xC0230005 | 使用了无效的特征表。 |
An invalid characteristics table was used. |
| 0xC0230006 | 找不到网络接口，或网络接口未就绪。 |
Failed to find the network interface or network interface is not ready. |
| 0xC0230007 | 未能打开网络接口。 |
Failed to open the network interface. |
| 0xC0230008 | 网络接口出现了不可恢复的内部故障。 |
Network interface has encountered an internal unrecoverable failure. |
| 0xC0230009 | 网络接口上的多播列表已满。 |
The multicast list on the network interface is full. |
| 0xC023000A | 已尝试将重复的多播地址添加到该列表。 |
An attempt was made to add a duplicate multicast address to the list. |
| 0xC023000B | 已尝试删除从未添加的多播地址。 |
At attempt was made to remove a multicast address that was never added. |
| 0xC023000C | 网络接口已中止请求。 |
Netowork interface aborted the request. |
| 0xC023000D | 由于网络接口正在重置，无法处理该请求。 |
Network interface can not process the request because it is being reset. |
| 0xC023000F | 已尝试在网络接口上发送无效的数据包。 |
An attempt was made to send an invalid packet on a network interface. |
| 0xC0230011 | 网络接口未就绪，无法完成此操作。 |
Network interface is not ready to complete this operation. |
| 0xC0230014 | 为此操作提交的缓冲区长度无效。 |
The length of the buffer submitted for this operation is not valid. |
| 0xC0230015 | 用于此操作的数据无效。 |
The data used for this operation is not valid. |
| 0xC0230016 | 为此操作提交的缓冲区长度太小。 |
The length of buffer submitted for this operation is too small. |
| 0xC0230017 | 网络接口不支持此 OID (对象标识符) |
Network interface does not support this OID (Object Identifier) |
| 0xC0230018 | 已删除网络接口。 |
The network interface has been removed. |
| 0xC0230019 | 网络接口不支持此媒体类型。 |
Network interface does not support this media type. |
| 0xC023001A | 已尝试删除其他组件正在使用的令牌环组地址。 |
An attempt was made to remove a token ring group address that is in use by other components. |
| 0xC023001B | 已试图映射无法找到的文件。 |
An attempt was made to map a file that can not be found. |
| 0xC023001C | NDIS 尝试映射文件时出错。 |
An error occurred while NDIS tried to map the file. |
| 0xC023001D | 已试图映射已映射的文件。 |
An attempt was made to map a file that is alreay mapped. |
| 0xC023001E | 尝试分配硬件资源失败，原因是另一组件在使用该资源。 |
An attempt to allocate a hardware resource failed because the resource is used by another component. |
| 0xC023001F | I/O 操作失败，原因是网络媒体断开连接或无线访问点超出范围。 |
The I/O operation failed because network media is disconnected or wireless access point is out of range. |
| 0xC0230022 | 请求中所使用的网络地址无效。 |
The network address used in the request is invalid. |
| 0xC023002A | 网络接口上的卸载操作已暂停。 |
The offload operation on the network interface has been paused. |
| 0xC023002B | 找不到网络接口。 |
Network interface was not found. |
| 0xC023002C | 不支持该结构中指定的修订号。 |
The revision number specified in the structure is not supported. |
| 0xC023002D | 此网络接口上不存在指定的端口。 |
The specified port does not exist on this network interface. |
| 0xC023002E | 此网络接口上指定端口的当前状态不支持所请求的操作。 |
The current state of the specified port on this network interface does not support the requested operation. |
| 0xC023002F | 微型端口适配器处于低功率状态。 |
The miniport adapter is in lower power state. |
| 0xC0230030 | 此操作要求重新初始化微型端口适配器。 |
This operation requires the miniport adapter to be reinitialized. |
| 0xC02300BB | 网络接口不支持此请求。 |
Netword interface does not support this request. |
| 0xC023100F | 由于本地策略设置，TCP 连接不可卸载。 |
The TCP connection is not offloadable because of a local policy setting. |
| 0xC0231012 | TCP 连接无法由烟囱卸载目标卸载。 |
The TCP connection is not offloadable by the Chimney offload target. |
| 0xC0231013 | IP 路径对象处于无法卸载的状态。 |
The IP Path object is not in an offloadable state. |
| 0xC0232000 | 无线局域网接口处于自动配置模式下，它不支持请求的参数更改操作。 |
The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation. |
| 0xC0232001 | 无线局域网接口忙，无法执行请求的操作。 |
The wireless local area network interface is busy and can not perform the requested operation. |
| 0xC0232002 | 无线局域网接口电源关闭，它不支持请求的操作。 |
The wireless local area network interface is powered down and doesn't support the requested operation. |
| 0xC0232003 | LAN 唤醒模式的列表已满。 |
The list of wake on LAN patterns is full. |
| 0xC0232004 | 低电量协议卸载列表已满。 |
The list of low power protocol offloads is full. |
| 0xC0232005 | 无线局域网接口现在无法在指定的通道上启动 AP。 |
The wireless local area network interface cannot start an AP on the specified channel right now. |
| 0xC0232006 | 无线局域网接口现在无法在指定的波段上启动 AP。 |
The wireless local area network interface cannot start an AP on the specified band right now. |
| 0xC0232007 | 由于监管原因，无线局域网接口无法在此通道上启动 AP。 |
The wireless local area network interface cannot start an AP on this channel due to regulatory reasons. |
| 0xC0232008 | 由于监管原因，无线局域网接口无法在此波段上启动 AP。 |
The wireless local area network interface cannot start an AP on this band due to regulatory reasons. |
| 0xC0290000 | 这是一种将 TPM 硬件错误转换为 Windows 错误的错误掩码。 |
This is an error mask to convert TPM hardware errors to win errors. |
| 0xC0290001 | 身份验证失败。 |
Authentication failed. |
| 0xC0290002 | 对 PCR、DIR 或其他注册表的索引不正确。 |
The index to a PCR, DIR or other register is incorrect. |
| 0xC0290003 | 一个或多个参数不正确。 |
One or more parameter is bad. |
| 0xC0290004 | 操作成功完成，但是此操作的审核失败。 |
An operation completed successfully but the auditing of that operation failed. |
| 0xC0290005 | 已设置清除禁用的标志，现在所有清除操作都需要物理访问。 |
The clear disable flag is set and all clear operations now require physical access. |
| 0xC0290006 | 激活受信任的平台模块(TPM)。 |
Activate the Trusted Platform Module (TPM). |
| 0xC0290007 | 启用受信任的平台模块(TPM)。 |
Enable the Trusted Platform Module (TPM). |
| 0xC0290008 | 目标命令已禁用。 |
The target command has been disabled. |
| 0xC0290009 | 操作失败。 |
The operation failed. |
| 0xC029000A | 序号未知或不一致。 |
The ordinal was unknown or inconsistent. |
| 0xC029000B | 安装所有者的功能已禁用。 |
The ability to install an owner is disabled. |
| 0xC029000C | 无法解释密钥句柄。 |
The key handle cannot be interpreted. |
| 0xC029000D | 密钥句柄指向无效的密钥。 |
The key handle points to an invalid key. |
| 0xC029000E | 不可接受的加密方案。 |
Unacceptable encryption scheme. |
| 0xC029000F | 迁移授权失败。 |
Migration authorization failed. |
| 0xC0290010 | 无法解释 PCR 信息。 |
PCR information could not be interpreted. |
| 0xC0290011 | 没有空间加载密钥。 |
No room to load key. |
| 0xC0290012 | 没有存储根密钥(SRK)集。 |
There is no Storage Root Key (SRK) set. |
| 0xC0290013 | 加密的 blob 无效或不是由此 TPM 创建的。 |
An encrypted blob is invalid or was not created by this TPM. |
| 0xC0290014 | 受信任的平台模块(TPM)已存在一个所有者。 |
The Trusted Platform Module (TPM) already has an owner. |
| 0xC0290015 | TPM 内部资源不足，无法执行请求的操作。 |
The TPM has insufficient internal resources to perform the requested action. |
| 0xC0290016 | 随机字符串过短。 |
A random string was too short. |
| 0xC0290017 | TPM 没有执行该操作的空间。 |
The TPM does not have the space to perform the operation. |
| 0xC0290018 | 命名的 PCR 值与当前的 PCR 值不匹配。 |
The named PCR value does not match the current PCR value. |
| 0xC0290019 | 此命令的 paramSize 参数包含不正确的值。 |
The paramSize argument to the command has the incorrect value . |
| 0xC029001A | 不存在现有的 SHA-1 线程。 |
There is no existing SHA-1 thread. |
| 0xC029001B | 计算无法进行，因为现有的 SHA-1 线程已遇到错误。 |
The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. |
| 0xC029001C | TPM 硬件设备在其内部自检期间报告了一个错误。请尝试重新启动计算机以解决该问题。如果该问题仍然存在，则可能需要更换 TPM 硬件或主板。 |
The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, you might need to replace your TPM hardware or motherboard. |
| 0xC029001D | 为 2 密钥函数中的第二个密钥授权失败。 |
The authorization for the second key in a 2 key function failed authorization. |
| 0xC029001E | 为命令发送的标记值无效。 |
The tag value sent to for a command is invalid. |
| 0xC029001F | 向 TPM 传输信息时发生 IO 错误。 |
An IO error occurred transmitting information to the TPM. |
| 0xC0290020 | 加密过程存在问题。 |
The encryption process had a problem. |
| 0xC0290021 | 加密过程未完成。 |
The decryption process did not complete. |
| 0xC0290022 | 使用了无效句柄。 |
An invalid handle was used. |
| 0xC0290023 | TPM 未安装认可密钥(EK)。 |
The TPM does not have an Endorsement Key (EK) installed. |
| 0xC0290024 | 不允许使用密钥。 |
The usage of a key is not allowed. |
| 0xC0290025 | 不允许已提交的实体类型。 |
The submitted entity type is not allowed. |
| 0xC0290026 | 相对于 TPM_Init 和后续的 TPM_Startup 而言，命令的接收顺序错误。 |
The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup. |
| 0xC0290027 | 签名的数据不能包含其他 DER 信息。 |
Signed data cannot include additional DER information. |
| 0xC0290028 | TPM_KEY_PARMs 中的密钥属性不受此 TPM 支持。 |
The key properties in TPM_KEY_PARMs are not supported by this TPM. |
| 0xC0290029 | 此密钥的迁移属性不正确。 |
The migration properties of this key are incorrect. |
| 0xC029002A | 此密钥的签名或加密方案不正确或在这种情况下不允许。 |
The signature or encryption scheme for this key is incorrect or not permitted in this situation. |
| 0xC029002B | data (或 blob)参数的大小不正确或与引用的密钥不一致。 |
The size of the data (or blob) parameter is bad or inconsistent with the referenced key. |
| 0xC029002C | 模式参数不正确，如 TPM_GetCapability 的 capArea 或 subCapArea、TPM_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. |
| 0xC029002D | physicalPresence 位或 physicalPresenceLock 位的值错误。 |
Either the physicalPresence or physicalPresenceLock bits have the wrong value. |
| 0xC029002E | TPM 无法执行此版本的功能。 |
The TPM cannot perform this version of the capability. |
| 0xC029002F | TPM 不允许换行的传输会话。 |
The TPM does not allow for wrapped transport sessions. |
| 0xC0290030 | TPM 审核构造失败，基础命令也返回故障代码。 |
TPM audit construction failed and the underlying command was returning a failure code also. |
| 0xC0290031 | TPM 审核构造失败，但基础命令返回成功。 |
TPM audit construction failed and the underlying command was returning success. |
| 0xC0290032 | 尝试重置不具有可重置属性的 PCR 注册表。 |
Attempt to reset a PCR register that does not have the resettable attribute. |
| 0xC0290033 | 尝试重置的 PCR 注册表需要不属于命令传输的区域和区域修饰符。 |
Attempt to reset a PCR register that requires locality and locality modifier not part of command transport. |
| 0xC0290034 | 使标识 blob 未正确键入。 |
Make identity blob not properly typed. |
| 0xC0290035 | 保存上下文时，已标识的资源类型与实际资源不匹配。 |
When saving context identified resource type does not match actual resource. |
| 0xC0290036 | TPM 正在尝试执行仅在 FIPS 模式中可用的命令。 |
The TPM is attempting to execute a command only available when in FIPS mode. |
| 0xC0290037 | 此命令正在尝试使用无效的系列 ID。 |
The command is attempting to use an invalid family ID. |
| 0xC0290038 | 无法使用用于操作 NV 存储的权限。 |
The permission to manipulate the NV storage is not available. |
| 0xC0290039 | 此操作需要签名的命令。 |
The operation requires a signed command. |
| 0xC029003A | 加载 NV 密钥的操作错误。 |
Wrong operation to load an NV key. |
| 0xC029003B | NV_LoadKey blob 需要所有者和 blob 授权。 |
NV_LoadKey blob requires both owner and blob authorization. |
| 0xC029003C | NV 区域已锁定，无法写入。 |
The NV area is locked and not writtable. |
| 0xC029003D | 此区域对于尝试的操作而言不正确。 |
The locality is incorrect for the attempted operation. |
| 0xC029003E | NV 区域为只读，无法写入。 |
The NV area is read only and can't be written to. |
| 0xC029003F | 没有对 NV 区域进行写保护。 |
There is no protection on the write to the NV area. |
| 0xC0290040 | 系列计数值不匹配。 |
The family count value does not match. |
| 0xC0290041 | 已写入 NV 区域。 |
The NV area has already been written to. |
| 0xC0290042 | NV 区域属性冲突。 |
The NV area attributes conflict. |
| 0xC0290043 | 结构标记和版本无效或不一致。 |
The structure tag and version are invalid or inconsistent. |
| 0xC0290044 | 此密钥受 TPM 所有者控制，只能由 TPM 所有者收回。 |
The key is under control of the TPM Owner and can only be evicted by the TPM Owner. |
| 0xC0290045 | 计数器句柄不正确。 |
The counter handle is incorrect. |
| 0xC0290046 | 此写入不是该区域的完全写入。 |
The write is not a complete write of the area. |
| 0xC0290047 | 已保存的上下文计数之间的间距过大。 |
The gap between saved context counts is too large. |
| 0xC0290048 | 已超出没有所有者的 NV 写入的最大数目。 |
The maximum number of NV writes without an owner has been exceeded. |
| 0xC0290049 | 未设置操作者 AuthData 值。 |
No operator AuthData value is set. |
| 0xC029004A | 未加载上下文指向的资源。 |
The resource pointed to by context is not loaded. |
| 0xC029004B | 委派管理已锁定。 |
The delegate administration is locked. |
| 0xC029004C | 尝试管理委派系列之外的系列。 |
Attempt to manage a family other then the delegated family. |
| 0xC029004D | 未启用委派表管理。 |
Delegation table management not enabled. |
| 0xC029004E | 存在一个在独占传输会话之外执行的命令。 |
There was a command executed outside of an exclusive transport session. |
| 0xC029004F | 尝试上下文保存所有者收回控制的密钥。 |
Attempt to context save a owner evict controlled key. |
| 0xC0290050 | DAA 命令没有可用的资源来执行此命令。 |
The DAA command has no resources availble to execute the command. |
| 0xC0290051 | 对 DAA 参数 inputData0 的一致性检查失败。 |
The consistency check on DAA parameter inputData0 has failed. |
| 0xC0290052 | 对 DAA 参数 inputData1 的一致性检查失败。 |
The consistency check on DAA parameter inputData1 has failed. |
| 0xC0290053 | 对 DAA_issuerSettings 的一致性检查失败。 |
The consistency check on DAA_issuerSettings has failed. |
| 0xC0290054 | 对 DAA_tpmSpecific 的一致性检查失败。 |
The consistency check on DAA_tpmSpecific has failed. |
| 0xC0290055 | 已提交的 DAA 命令指示的原子过程不是预期的过程。 |
The atomic process indicated by the submitted DAA command is not the expected process. |
| 0xC0290056 | 颁发者的有效性检查已检测到不一致。 |
The issuer's validity check has detected an inconsistency. |
| 0xC0290057 | 对 w 的一致性检查已失败。 |
The consistency check on w has failed. |
| 0xC0290058 | 句柄不正确。 |
The handle is incorrect. |
| 0xC0290059 | 委派不正确。 |
Delegation is not correct. |
| 0xC029005A | 上下文 blob 无效。 |
The context blob is invalid. |
| 0xC029005B | TPM 包含的上下文过多。 |
Too many contexts held by the TPM. |
| 0xC029005C | 迁移授权签名验证失败。 |
Migration authority signature validation failure. |
| 0xC029005D | 迁移目标尚未进行身份验证。 |
Migration destination not authenticated. |
| 0xC029005E | 迁移源不正确。 |
Migration source incorrect. |
| 0xC029005F | 迁移授权不正确。 |
Incorrect migration authority. |
| 0xC0290061 | 尝试吊销 EK，但 EK 不可吊销。 |
Attempt to revoke the EK and the EK is not revocable. |
| 0xC0290062 | CMK 票证的签名不正确。 |
Bad signature of CMK ticket. |
| 0xC0290063 | 上下文列表中没有用于其他上下文的空间。 |
There is no room in the context list for additional contexts. |
| 0xC0290400 | 命令被阻止。 |
The command was blocked. |
| 0xC0290401 | 找不到指定的句柄。 |
The specified handle was not found. |
| 0xC0290402 | TPM 已返回重复的句柄，需要重新提交此命令。 |
The TPM returned a duplicate handle and the command needs to be resubmitted. |
| 0xC0290403 | 传输中的命令被阻止。 |
The command within the transport was blocked. |
| 0xC0290404 | 传输中的命令不受支持。 |
The command within the transport is not supported. |
| 0xC0290800 | TPM 忙碌，无法立即响应命令，但是稍后可以重新提交此命令。 |
The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time. |
| 0xC0290801 | SelfTestFull 尚未运行。 |
SelfTestFull has not been run. |
| 0xC0290802 | TPM 当前正在执行完全自检。 |
The TPM is currently executing a full selftest. |
| 0xC0290803 | TPM 正在抵御字典攻击，且处于超时期限。 |
The TPM is defending against dictionary attacks and is in a time-out period. |
| 0xC0291001 | 命令已取消。 |
The command was cancelled. |
| 0xC0291002 | 无法创建新的 TPM 上下文，因为打开的上下文过多。 |
A new TPM context could not be created because there are too many open contexts. |
| 0xC0291003 | TPM 驱动程序与系统上找到的 TPM 版本不兼容。 |
TPM driver is not compatible with the version of TPM found on the system. |
| 0xC0291004 | 调用方没有相应的权限来执行请求的操作。 |
The caller does not have the appropriate rights to perform the requested operation. |
| 0xC0291006 | 此固件的物理存在接口不支持请求的方法。 |
The Physical Presence Interface of this firmware does not support the requested method. |
| 0xC0292000 | 这是一种将平台加密提供程序错误转换为 Windows 错误的错误掩码。 |
This is an error mask to convert Platform Crypto Provider errors to win errors. |
| 0xC0292001 | 平台加密设备当前未就绪。它需要进行完全预配才能运行。 |
The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational. |
| 0xC0292002 | 提供给平台加密提供程序的句柄无效。 |
The handle provided to the Platform Crypto Provider is invalid. |
| 0xC0292003 | 提供给平台加密提供程序的参数无效。 |
A parameter provided to the Platform Crypto Provider is invalid. |
| 0xC0292004 | 为平台加密提供程序提供的标志不受支持。 |
A provided flag to the Platform Crypto Provider is not supported. |
| 0xC0292005 | 此平台加密提供程序不支持请求的操作。 |
The requested operation is not supported by this Platform Crypto Provider. |
| 0xC0292006 | 缓冲区过小，无法包含所有数据。没有信息写入到缓冲区。 |
The buffer is too small to contain all data. No information has been written to the buffer. |
| 0xC0292007 | 在平台加密提供程序中发生了意外的内部错误。 |
An unexpected internal error has occurred in the Platform Crypto Provider. |
| 0xC0292008 | 授权使用提供程序对象失败。 |
The authorization to use a provider object has failed. |
| 0xC0292009 | 平台加密设备已经忽略了对提供程序对象的授权，以减少字典式攻击。 |
The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack. |
| 0xC029200A | 找不到引用的策略。 |
The referenced policy was not found. |
| 0xC029200B | 找不到引用的配置文件。 |
The referenced profile was not found. |
| 0xC029200C | 验证不成功。 |
The validation was not succesful. |
| 0xC029200D | 找不到平台加密设备。将不会提交需要平台加密设备的操作。 |
A Platform Crypto Device was not found. Operations that require a Platform Crypto Device will not be submitted. |
| 0xC029200E | 试图将某个键导入或加载到不正确的存储父项下。 |
An attempt was made to import or load a key under an incorrect storage parent. |
| 0xC029200F | 该 TPM 密钥未加载。 |
The TPM key is not loaded. |
| 0xC0292010 | 该 TPM 密钥证书尚未生成。 |
The TPM key certification has not been generated. |
| 0xC0292011 | 该 TPM 密钥尚未完成。 |
The TPM key is not yet finalized. |
| 0xC0292012 | 未设置 TPM 证明质询。 |
The TPM attestation challenge is not set. |
| 0xC0292013 | 该 TPM 密钥未绑定到 PCR 信息。 |
The TPM key is not bound to PCR info. |
| 0xC0292014 | 该 TPM 密钥已完成。 |
The TPM key is already finalized. |
| 0xC0292015 | 不支持该 TPM 密钥使用策略。 |
The TPM key usage policy is not supported. |
| 0xC0292016 | 该 TPM 密钥使用策略无效。 |
The TPM key usage policy is invalid. |
| 0xC0292017 | 要导入到 TPM 的软件密钥有问题。 |
There was a problem with the software key being imported into the TPM. |
| 0xC0292018 | 该 TPM 密钥未进行身份验证。 |
The TPM key is not authenticated. |
| 0xC0292019 | 该 TPM 密钥不是 AIK。 |
The TPM key is not an AIK. |
| 0xC029201A | 该 TPM 密钥不是签名密钥。 |
The TPM key is not a signing key. |
| 0xC029201B | 该 TPM 已锁定。 |
The TPM is locked out. |
| 0xC029201C | 不支持请求的声明类型。 |
The claim type requested is not supported. |
| 0xC029201D | 不支持当前的 TPM 版本。 |
The current TPM version is not supported. |
| 0xC029201E | 缓冲区长度不匹配。 |
The buffer lengths do not match. |
| 0xC0293002 | 不存在与此实例关联的结果。 |
No result associated with this instance exists. |
| 0xC0293003 | TPM 返回了不完整的 PCR 结果。原因可能是某个选择集不受支持。请尝试使用其他选择集重新读取。 |
The TPM returned incomplete PCR results. This maybe due to an unsupported selection set. Attempt the read again with a different selection set. |
| 0xC0293004 | rTPM 上下文已损坏。必须重启 rTPM 操作。 |
The rTPM context has been corrupted. The rTPM operation must be restarted. |
| 0xC0293005 | rTPM 目标不支持远程处理指定的 TPM 命令。 |
The rTPM target does not support remote processing of the specified TPM command. |
| 0xC0294000 | 由于客户端上启用了零排放模式，已阻止与 TPM 相关的网络操作。 |
TPM related network operations are blocked as Zero Exhaust mode is enabled on client. |
| 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 debugging 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. |
| 0xC0360001 | 数据包中的 SPI 与有效的 IPSec SA 不匹配。 |
The SPI in the packet does not match a valid IPsec SA. |
| 0xC0360002 | 生存时间已过期的 IPSec SA 接收到数据包。 |
Packet was received on an IPsec SA whose lifetime has expired. |
| 0xC0360003 | IPSec SA 接收到与数据包特征不匹配的数据包。 |
Packet was received on an IPsec SA that does not match the packet characteristics. |
| 0xC0360004 | 数据包序列号重播检查失败。 |
Packet sequence number replay check failed. |
| 0xC0360005 | 数据包中 IPSec 的头和/或尾无效。 |
IPsec header and/or trailer in the packet is invalid. |
| 0xC0360006 | IPSec 完整性检查失败。 |
IPsec integrity check failed. |
| 0xC0360007 | IPSec 丢弃了一个明文数据包。 |
IPsec dropped a clear text packet. |
| 0xC0360008 | IPSec 已丢弃已验证防火墙模式下的传入 ESP 数据包。此丢弃是良性的。 |
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign. |
| 0xC0360009 | 由于 DoS 节流，IPSec 已丢弃数据包。 |
IPsec dropped a packet due to DoS throttling. |
| 0xC0368000 | IPSec DoS 保护符合一个显式阻止规则。 |
IPsec DoS Protection matched an explicit block rule. |
| 0xC0368001 | IPSec DoS 保护收到一个禁止的 IPSec 特定多播数据包。 |
IPsec DoS Protection received an IPsec specific multicast packet which is not allowed. |
| 0xC0368002 | IPSec DoS 保护收到的数据包格式错误。 |
IPsec DoS Protection received an incorrectly formatted packet. |
| 0xC0368003 | IPSec DoS 保护查找状态失败。 |
IPsec DoS Protection failed to look up state. |
| 0xC0368004 | IPSec DoS 保护创建状态失败，因为已达到策略允许的最大条目数。 |
IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached. |
| 0xC0368005 | IPSec DoS 保护收到策略禁止的密钥模块的 IPSec 协商数据包。 |
IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. |
| 0xC0368006 | 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. |
| 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. |
| 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. |
| 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. |
| 0xC03A0031 | 请求的调整大小操作可能截断了位于虚拟磁盘上的用户数据。 |
The requested resize operation might truncate user data residing on the virtual disk. |
| 0xC03A0032 | 无法确定虚拟磁盘的安全大小下限。这可能是由于分区表丢失或损坏。 |
The minimum safe size of the virtual disk could not be determined. This may be due to a missing or corrupt partition table. |
| 0xC03A0033 | 虚拟磁盘的大小无法安全地进一步减小。 |
The size of the virtual disk cannot be safely reduced further. |
| 0xC0400001 | 恢复密钥筛选器无法找到为操作提供的恢复密钥。 |
The Resume Key Filter could not find the resume key supplied for the operation. |
| 0xC0400002 | 恢复密钥筛选器找到与提供给句柄的密钥相匹配的现有恢复密钥。 |
The Resume Key Filter found an existing resume key that matches the one supplied for the handle. |
| 0xC0400003 | 附加到句柄的恢复密钥筛选器数据 blob 已满。没有更多可用空间。 |
The Resume Key Filter data blob attached to the handle is full. No more space is available. |
| 0xC0400004 | 恢复密钥筛选器句柄存储已满。无法接受更多恢复句柄。 |
The Resume Key Filter handle store is full. No more resume handles can be accepted. |
| 0xC0400005 | 恢复密钥筛选器操作失败，因为文件临时被阻止，挂起文件上现有句柄的恢复操作。 |
The Resume Key Filter failed the operation because the file is temporarily blocked pending the resume of existing handles on the file. |
| 0xC0400006 | 恢复密钥筛选器找到一个与活动/已打开的句柄上提供的恢复密钥相匹配的现有恢复密钥。该操作需要一个不活动/已关闭的句柄。 |
The Resume Key Filter found an existing resume key that matches the one supplied on a handle that's active/open. The operation requires an inactive/closed handle. |
| 0xC0410001 | 操作必须由 RDBSS 重新启动。 |
The operation must be restarted by RDBSS. |
| 0xC0410002 | 操作必须继续进行。 |
The operation must continue processing. |
| 0xC0410003 | 必须将操作发布到线程才能在 Passive 级别的 IRQL 重试。 |
The operation must be posted to a thread to be retried at passive IRQL. |
| 0xC0420001 | 给定的属性句柄在此服务器上无效。 |
The attribute handle given was not valid on this server. |
| 0xC0420002 | 无法读取属性。 |
The attribute cannot be read. |
| 0xC0420003 | 无法写入属性。 |
The attribute cannot be written. |
| 0xC0420004 | 属性 PDU 无效。 |
The attribute PDU was invalid. |
| 0xC0420005 | 属性需要进行身份验证，然后才能读取或写入。 |
The attribute requires authentication before it can be read or written. |
| 0xC0420006 | 属性服务器不支持从客户端接收的请求。 |
Attribute server does not support the request received from the client. |
| 0xC0420007 | 指定的偏移量超出了属性的结尾。 |
Offset specified was past the end of the attribute. |
| 0xC0420009 | 排队的准备写入操作过多。 |
Too many prepare writes have been queued. |
| 0xC042000A | 在给定的属性句柄范围内未找到任何属性。 |
No attribute found within the given attribute handle range. |
| 0xC042000B | 使用读取 BLOB 请求无法读取或写入属性。 |
The attribute cannot be read or written using the Read Blob Request. |
| 0xC042000C | 用于加密此链接的加密密钥大小不足。 |
The Encryption Key Size used for encrypting this link is insufficient. |
| 0xC042000D | 此属性值长度对于此操作无效。 |
The attribute value length is invalid for the operation. |
| 0xC042000E | 请求的属性请求遇到不太可能发生的错误，因此无法根据请求完成。 |
The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. |
| 0xC042000F | 属性需要进行加密，然后才能读取或写入。 |
The attribute requires encryption before it can be read or written. |
| 0xC0420010 | 属性类型不是较高层规范所定义的支持的分组属性。 |
The attribute type is not a supported grouping attribute as defined by a higher layer specification. |
| 0xC0420011 | 资源不足，无法完成请求。 |
Insufficient Resources to complete the request. |
| 0xC0421000 | 接收到位于预留范围内的错误。 |
An error that lies in the reserved range has been received. |
| 0xC0430001 | 安全引导检测到已尝试进行保护数据回退操作。 |
Secure Boot detected that rollback of protected data has been attempted. |
| 0xC0430002 | 该值受安全引导策略保护，无法进行修改或删除。 |
The value is protected by Secure Boot policy and cannot be modified or deleted. |
| 0xC0430003 | 安全引导策略无效。 |
The Secure Boot policy is invalid. |
| 0xC0430004 | 新的安全引导策略在其更新列表中不包含当前发布者。 |
A new Secure Boot policy did not contain the current publisher on its update list. |
| 0xC0430005 | 安全引导策略未签名或被不可信的签名者签名。 |
The Secure Boot policy is either not signed or is signed by a non-trusted signer. |
| 0xC0430007 | 安全启动要求某些文件和驱动程序不可被其他文件或驱动程序替换。 |
Secure Boot requires that certain files and drivers are not replaced by other files or drivers. |
| 0xC0430008 | 未授权在此计算机上使用安全启动补充策略文件。 |
The Secure Boot Supplemental Policy file was not authorized on this machine. |
| 0xC0430009 | 在此设备上无法识别补充策略。 |
The Supplemntal Policy is not recognized on this device. |
| 0xC043000A | 未在安全启动策略中找到防回退版本。 |
The Antirollback version was not found in the Secure Boot Policy. |
| 0xC043000B | 安全启动策略中指定的平台 ID 与此设备上的平台 ID 不匹配。 |
The Platform ID specified in the Secure Boot policy does not match the Platform ID on this device. |
| 0xC043000C | 安全启动策略文件的防回退版本比此设备的旧。 |
The Secure Boot policy file has an older Antirollback Version than this device. |
| 0xC043000D | 安全启动策略文件与已升级的旧策略不匹配。 |
The Secure Boot policy file does not match the upgraded legacy policy. |
| 0xC043000E | 安全引导策略文件是必需的，但找不到。 |
The Secure Boot policy file is required but could not be found. |
| 0xC043000F | 补充安全引导策略文件无法作为基本安全引导策略加载。 |
Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy. |
| 0xC0430010 | 基本安全引导策略文件无法作为补充安全引导策略加载。 |
Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy. |
| 0xC0440001 | PortCl 无法找到声称支持 IMiniportAudioEngineNode 的微型端口驱动程序所暴露的音频引擎节点。 |
PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode. |
| 0xC0440002 | HD 音频小组件遇到意外的空连接列表。 |
HD Audio widget encountered an unexpected empty connection list. |
| 0xC0440003 | HD 音频小组件不支持连接列表参数。 |
HD Audio widget does not support the connection list parameter. |
| 0xC0440004 | 未成功创建任何 HD 音频子设备。 |
No HD Audio subdevices were successfully created. |
| 0xC0440005 | 链接的列表中遇到意外的 NULL 指针。 |
An unexpected NULL pointer was encountered in a linked list. |
| 0xC0450000 | 虚拟安全模式(VSM)未初始化。虚拟机监控程序或 VSM 可能不存在或未启用。 |
Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. |
| 0xC0450001 | 由于 IOMMU 不存在或未在 BIOS 中启用，虚拟机监控程序未在保护 DMA。 |
The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS. |
| 0xC0500003 | 启动文件过小，无法支持持续快照。 |
The bootfile is too small to support persistent snapshots. |
| 0xC0500004 | 激活此卷上的永久性快照所用时间超过了允许的时间。 |
Activation of persistent snapshots on this volume took longer than was allowed. |
| 0xC0510001 | 此操作已被更高优先级的操作取代。之后必须恢复该操作。 |
The operation was preempted by a higher priority operation. It must be resumed later. |
| 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 data is available for the initiator to query. |
| 0xC05CFF02 | 此设备的数据容量已更改，同时生成一个单元注意条件。 |
The data capacity of the device has changed, resulting in a Unit Attention condition. |
| 0xC05CFF03 | 此前的操作已导致这个发起程序的预留被占用，同时生成一个单元注意条件。 |
A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF04 | 此前的操作已导致这个发起程序的预留被释放，同时生成一个单元注意条件。 |
A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition. |
| 0xC05CFF05 | 此前的操作已导致这个发起程序的注册被占用，同时生成一个单元注意条件。 |
A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF06 | 此设备的数据存储格式已更改，同时生成一个单元注意条件。 |
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. |
| 0xC05D0002 | 你不能访问此共享文件夹，因为你组织的安全策略阻止未经身份验证的来宾访问。这些策略可帮助保护你的电脑免受网络上不安全设备或恶意设备的威胁。 |
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. |
| 0xC0E70001 | 指定的容错域类型或最小/最大容错域类型的组合无效。 |
The specified fault domain type or combination of minimum / maximum fault domain type is not valid. |
| 0xC0E70003 | 指定的复原类型无效。 |
The specified resiliency type is not valid. |
| 0xC0E70004 | 存储池不支持物理磁盘的扇区大小。 |
The sector size of the physical disk is not supported by the storage pool. |
| 0xC0E70006 | 容错值不在受支持的值范围内。 |
The value for fault tolerance is outside of the supported range of values. |
| 0xC0E70007 | 所请求的数据副本数不在受支持的值范围内。 |
The number of data copies requested is outside of the supported range of values. |
| 0xC0E70009 | 交错长度的值不在受支持的值范围内或者不是 2 的幂。 |
The value for interleave length is outside of the supported range of values or is not a power of 2. |
| 0xC0E7000A | 指定的列数超出支持的值的范围。 |
The number of columns specified is outside of the supported range of values. |
| 0xC0E7000B | 没有足够的物理磁盘空间完成请求的操作。 |
There were not enough physical disks to complete the requested operation. |
| 0xC0E7000C | 有扩展的错误信息可用。 |
Extended error information is available. |
| 0xC0E7000D | 指定的预配类型无效。 |
The specified provisioning type is not valid. |
| 0xC0E7000E | 分配大小不在受支持的值范围内。 |
The allocation size is outside of the supported range of values. |
| 0xC0E7000F | 此虚拟磁盘不支持外壳识别。 |
Enclosure awareness is not supported for this virtual disk. |
| 0xC0E70010 | 写缓存大小不在受支持的值范围内。 |
The write cache size is outside of the supported range of values. |
| 0xC0E70011 | 组数目的值不在受支持的值范围内。 |
The value for number of groups is outside of the supported range of values. |
| 0xC0E70012 | 物理磁盘的 OperationalState 对此操作无效。 |
The OperationalState of the physical disk is invalid for this operation. |
| 0xC0E70013 | 某个列的状态需要更新。 |
A column's state needs to be updated. |
| 0xC0E70014 | 需要分配某个盘区。 |
An extent needs to be allocated. |
| 0xC0E70015 | 元数据版本不受支持。 |
The metadata version is unsupported. |
| 0xC0E70016 | 元数据读取已损坏。 |
The metadata read was corrupt. |
| 0xC0E70017 | DRT 已满。 |
The DRT is full. |
| 0xC0E70018 | 发现不一致项。 |
An inconsistency was found. |
| 0xC0E70019 | 日志未就绪。 |
The log is not ready. |
| 0xC0E7001A | 没有好的数据副本可用。 |
No good copy of data was available. |
| 0xC0E7001B | 驱动器未就绪。 |
The drive is not ready. |
| 0xC0E7001C | 此驱动器上的数据已过时。 |
The data on this drive is stale. |
| 0xC0E7001D | 此驱动器上的数据已丢失。 |
The data on this drive has been lost. |
| 0xC0E80000 | 安全内核无法识别此命令 |
The command was not recognized by the security core |
| 0xC0E90001 | 系统完整性检测到已尝试进行策略回退。 |
System Integrity detected that policy rollback has been attempted. |
| 0xC0E90002 | 已违反系统完整性策略。 |
System Integrity policy has been violated. |
| 0xC0E90003 | 系统完整性策略无效。 |
The System Integrity policy is invalid. |
| 0xC0E90004 | 系统完整性策略未签名或被不可信的签名者签名。 |
The System Integrity policy is either not signed or is signed by a non-trusted signer. |
| 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. |
| 0xC0EB0001 | 未授权在此计算机上使用该平台清单文件。 |
The Platform Manifest file was not authorized on this machine. |
| 0xC0EB0002 | 该平台清单文件无效。 |
The Platform Manifest file was not valid. |
| 0xC0EB0003 | 该文件在此平台上未获得授权，因为在平台清单中未找到相应条目。 |
The file is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0xC0EB0004 | 该目录在此平台上未获得授权，因为在平台清单中未找到相应条目。 |
The catalog is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0xC0EB0005 | 该文件在此平台上未获得授权，因为在嵌入签名中未找到相应的二进制 ID。 |
The file is not authorized on this platform because a Binary ID was not found in the embedded signature. |
| 0xC0EB0006 | 此系统上不存在有效的平台清单。 |
No active Platform Manifest exists on this system. |
| 0xC0EB0007 | 该平台清单文件未正确签名。 |
The Platform Manifest file was not properly signed. |