| 0x37 | 在卷 %1 上的文件系统结构中发现了损坏。%n%n%8 |
A corruption was discovered in the file system structure on volume %1.%n%n%8 |
| 0x82 | 卷 %2 上的文件系统结构现在已经修复。 |
The file system structure on volume %2 has now been repaired. |
| 0x83 | 无法更正卷 %2 上的文件系统结构。%n请运行卷 %2 上的 chkdsk 实用程序。 |
The file system structure on volume %2 cannot be corrected.%nPlease run the chkdsk utility on the volume %2. |
| 0x84 | 短时间内发生太多修复事件。%n临时暂停发送更多修复事件。 |
Too many repair events have occurred in a short period of time.%nTemporarily suspending posting of further repair events. |
| 0x85 | 已跳过发送 %1 修复事件。现在将恢复修复事件发送。%n下面是修复动词跳过的发送修复事件计数:%nBadFRS: %2%nOrphanChildFRS: %3%nBadClusters: %4%nBadFreeClusters: %5%nCrossLink: %6%nSDEntry: %7%nInvalidSecurityId: %8%nIndexAttribute: %9%nIndexSubtree: %10%nIndexOffset: %11%nIndexEntry: %12%nIndexOrder: %13%n连接: %14%nBreakCycle: %15%nFRSAllocate: %16%n其他: %17%n |
Skipped posting of %1 repair events. Repair event posting will now be resumed.%nHere are the skipped posting repair events count by repair verbs:%nBadFRS: %2%nOrphanChildFRS: %3%nBadClusters: %4%nBadFreeClusters: %5%nCrossLink: %6%nSDEntry: %7%nInvalidSecurityId: %8%nIndexAttribute: %9%nIndexSubtree: %10%nIndexOffset: %11%nIndexEntry: %12%nIndexOrder: %13%nConnect: %14%nBreakCycle: %15%nFRSAllocate: %16%nOthers: %17%n |
| 0x1000 | No-Op |
No-Op |
| 0x1001 | 强制执行完整的 Chkdsk |
Force Full Chkdsk |
| 0x1002 | 强制执行主动扫描 |
Force Proactive Scan |
| 0x1003 | 坏的 FRS |
Bad FRS |
| 0x1004 | 孤立子 FRS |
Orphan Child FRS |
| 0x1005 | 坏群集 |
Bad Clusters |
| 0x1006 | 坏的空闲群集 |
Bad Free Clusters |
| 0x1007 | 交叉链接 |
Cross-Link |
| 0x1008 | SD 项 |
SD Entry |
| 0x1009 | 无效的安全 ID |
Invalid Security Id |
| 0x100A | 索引属性 |
Index Attribute |
| 0x100B | 索引子树 |
Index Subtree |
| 0x100C | 索引偏移 |
Index Offset |
| 0x100D | 索引项 |
Index Entry |
| 0x100E | 索引顺序 |
Index Order |
| 0x100F | 连接 |
Connect |
| 0x1010 | 中断周期 |
Break Cycle |
| 0x1011 | FRS 分配 |
FRS Allocate |
| 0x1012 | 索引排序 |
Index Sort |
| 0x1013 | 索引循环 |
Index Cycle |
| 0x1100 | 文件系统驱动程序 |
File System Driver |
| 0x1101 | 主动扫描仪 |
Proactive Scanner |
| 0x1102 | 用户应用程序 |
User Application |
| 0x1200 | 只读卷 |
Read Only Volume |
| 0x1201 | 自愈 |
Self Healed |
| 0x1202 | 已禁用错误点处理 |
Spot Corruption Handling Disabled |
| 0x1203 | 错误校验程序绕过严重错误 |
Spot Verifier Bypassed On Critical |
| 0x1204 | 错误校验程序绕过错误 |
Spot Verifier Bypassed On Error |
| 0x1205 | 发送到错误修复程序 |
Sent To Spot Fixer |
| 0x1206 | 错误修复程序绕过严重错误 |
Spot Fixer Bypassed On Critical |
| 0x1207 | 错误修复程序绕过错误 |
Spot Fixer Bypassed On Error |
| 0x1208 | 复制 |
Duplicate |
| 0x1209 | 格式错误 |
Malformed |
| 0x120A | 不受支持 |
Unsupported |
| 0x120B | 已验证 |
Verified |
| 0x120C | 误报 |
False Positive |
| 0x120D | 被取代 |
Superseded |
| 0x120E | 已清除 |
Purged |
| 0x120F | 伪动词 |
Pseudo Verb |
| 0x1210 | 意外损坏 |
Unexpected Corruption |
| 0x1211 | 卷不可用 |
Volume Not Available |
| 0x1300 | 维护 |
Maintenance |
| 0x1301 | 正常 |
Normal |
| 0x1302 | 关键 |
Critical |
| 0x1F00 | |
|
| 0x2010 | 损坏的确切性质未知。需要扫描文件系统结构并脱机修复。 |
The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline. |
| 0x2020 | 损坏的确切性质未知。需要联机扫描文件系统结构。 |
The exact nature of the corruption is unknown. The file system structures need to be scanned online. |
| 0x2030 | 主文件表(MFT)包含损坏的文件记录。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。 |
The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". |
| 0x2040 | 主文件表(MFT)包含的子文件记录段无法从其基本文件记录段访问。文件参考编号为 0x%1!0I64x!。 |
The Master File Table (MFT) contains a child file record segment that is not reachable from its base file record segment. The file reference number is 0x%1!0I64x!. |
| 0x2050 | 在访问文件数据时发现了坏群集。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。包含坏群集的扩展位于 Vcn 0x%3!0I64x!，Lcn 0x%4!0I64x!。 |
A bad cluster was discovered while accessing file data. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". The extent containing the bad cluster is located at Vcn 0x%3!0I64x!, Lcn 0x%4!0I64x!. |
| 0x2060 | 在卷上的任何现有文件外部都发现了坏群集。坏群集位于 Lcn 0x%1!0I64x!。 |
A bad cluster was discovered outside of any existing file on the volume. The bad cluster is located at Lcn 0x%1!0I64x!. |
| 0x2070 | 发现两个文件占用卷上的同一位置。所属文件参考编号为 0x%1!0I64x!。所属文件名为“%2!wZ!”。包含坏群集的所属扩展位于 Vcn 0x%3!0I64x!，Lcn 0x%4!0I64x!。交叉文件参考编号为 0x%5!0I64x!。交叉文件名为“%6!wZ!”。包含坏群集的交叉扩展位于 Vcn 0x%7!0I64x!。 |
Two files were found to occupy the same location on the volume. The owning file reference number is 0x%1!0I64x!. The name of the owning file is \"%2!wZ!\". The owning extent containing the bad cluster is located at Vcn 0x%3!0I64x!, Lcn 0x%4!0I64x!. The crossing file reference number is 0x%5!0I64x!. The name of the crossing file is \"%6!wZ!\". The crossing extent containing the bad cluster is located at Vcn 0x%7!0I64x!. |
| 0x2080 | 在安全描述符流中发现了损坏。损坏的项位于偏移 0x%1!I64x! 处。 |
A corruption was found in the security descriptor stream. The corrupted entry is at offset 0x%1!I64x!. |
| 0x2090 | 发现文件的安全 ID 在安全文件中未描述。无效的安全 ID 为 0x%1!lx!。文件参考编号为 0x%2!0I64x!。文件名为“%3!wZ!”。卷上可能还有其他文件也引用此无效安全 ID。 |
A file was found to have a security ID that is not described in the security file. The invalid security ID is 0x%1!lx!. The file reference number is 0x%2!0I64x!. The name of the file is \"%3!wZ!\". There may be additional files on the volume that also refer to this invalid security ID. |
| 0x20A0 | 在文件系统索引结构中发现损坏。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。损坏的索引属性为“%3!wZ!”。 |
A corruption was found in a file system index structure. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". The corrupted index attribute is \"%3!wZ!\". |
| 0x20C0 | 在文件系统索引结构中发现损坏。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。损坏的索引属性为“%3!wZ!”。损坏的索引块位于 Vcn 0x%4!0I64x!，Lcn 0x%5!0I64x!。损坏开始位置在索引块中的偏移 %6!lu! 处。 |
A corruption was found in a file system index structure. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". The corrupted index attribute is \"%3!wZ!\". The corrupted index block is located at Vcn 0x%4!0I64x!, Lcn 0x%5!0I64x!. The corruption begins at offset %6!lu! within the index block. |
| 0x20E0 | 文件系统索引结构包含的项违反了排序规则。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。损坏的索引属性为“%3!wZ!”。 |
A file system index structure contains entries that violate ordering rules. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". The corrupted index attribute is \"%3!wZ!\". |
| 0x20F0 | 卷上的文件无法再从其父目录访问。父文件参考编号为 0x%1!0I64x!。父目录名称为“%2!wZ!”。父索引属性为“%3!wZ!”。需要重新连接的文件的文件参考编号为 0x%4!0I64x!。卷上可能还有其他文件也需要重新连接到此父目录。 |
A file on the volume is no longer reachable from its parent directory. The parent file reference number is 0x%1!0I64x!. The name of the parent directory is \"%2!wZ!\". The parent index attribute is \"%3!wZ!\". The file reference number of the file that needs to be reconnected is 0x%4!0I64x!. There may be additional files on the volume that also need to be reconnected to this parent directory. |
| 0x2100 | 在卷上的目录层次结构中发现循环，这只能通过提供父-子关系修复。父文件参考编号为 0x%1!0I64x!。父目录名称为“%2!wZ!”。子文件参考编号为 0x%3!0I64x!。子目录名称为“%4!wZ!”。卷上可能还有其他目录也参与此循环。 |
A cycle was found in the directory hierarchy on the volume, which can only be fixed by severing a parent-child relationship. The parent file reference number is 0x%1!0I64x!. The name of the parent directory is \"%2!wZ!\". The child file reference number is 0x%3!0I64x!. The name of the child directory is \"%4!wZ!\". There may be additional directories on the volume that also participate in this cycle. |
| 0x2110 | 发现群集被文件使用，但在卷位图中未标记为已使用。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。未分配的群集位于 Vcn 0x%3!0I64x!，Lcn 0x%4!0I64x!。 |
A cluster was found to be used by a file but not marked as used in the volume bitmap. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". The unallocated cluster is located at Vcn 0x%3!0I64x!, Lcn 0x%4!0I64x!. |
| 0x2120 | 文件系统索引结构包含违反排序规则的条目。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。损坏的索引属性为“%3!wZ!”。损坏的子树以位于 Vcn 0x%5!0I64x! 处的索引块的条目(编号为 %4!lu!)为根。 |
A file system index structure contains entries that violate ordering rules. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". The corrupted index attribute is \"%3!wZ!\". The corrupted subtree is rooted at entry number %4!lu! of the index block located at Vcn 0x%5!0I64x!. |
| 0x2130 | 文件系统索引结构包含一个循环。文件参考编号为 0x%1!0I64x!。文件名为“%2!wZ!”。损坏的索引属性为“%3!wZ!”。该循环包括 %4!lu! 个索引块(开始于 Vcn 0x%5!0I64x!，结束于 Vcn 0x%6!0I64x!)。 |
A file system index structure contains a cycle. The file reference number is 0x%1!0I64x!. The name of the file is \"%2!wZ!\". The corrupted index attribute is \"%3!wZ!\". The cycle includes %4!lu! index blocks starting at Vcn 0x%5!0I64x! and ending at Vcn 0x%6!0I64x!. |
| 0x00004000 | $UNUSED |
$UNUSED |
| 0x00004001 | $STANDARD_INFORMATION |
$STANDARD_INFORMATION |
| 0x00004002 | $ATTRIBUTE_LIST |
$ATTRIBUTE_LIST |
| 0x00004003 | $FILE_NAME |
$FILE_NAME |
| 0x00004004 | $OBJECT_ID |
$OBJECT_ID |
| 0x00004005 | $SECURITY_DESCRIPTOR |
$SECURITY_DESCRIPTOR |
| 0x00004006 | $VOLUME_NAME |
$VOLUME_NAME |
| 0x00004007 | $VOLUME_INFORMATION |
$VOLUME_INFORMATION |
| 0x00004008 | $DATA |
$DATA |
| 0x00004009 | $INDEX_ROOT |
$INDEX_ROOT |
| 0x0000400A | $INDEX_ALLOCATION |
$INDEX_ALLOCATION |
| 0x0000400B | $BITMAP |
$BITMAP |
| 0x0000400C | $REPARSE_POINT |
$REPARSE_POINT |
| 0x0000400D | $EA_INFORMATION |
$EA_INFORMATION |
| 0x0000400E | $EA |
$EA |
| 0x00004010 | $LOGGED_UTILITY_STREAM |
$LOGGED_UTILITY_STREAM |
| 0x000061A8 | 正在清除文件记录 0x%1 使用的位。 |
Clearing the in use bit for file record 0x%1. |
| 0x000061A9 | 正在修复文件记录 0x%1 的序列号。 |
Repairing the sequence number for file record 0x%1. |
| 0x000061AA | 正在修复文件记录 0x%1 的第一个可用字节。 |
Repairing the first free byte for file record 0x%1. |
| 0x000061AB | 正在修复文件记录 0x%1 的段号。 |
Repairing the segment number for file record 0x%1. |
| 0x000061AC | 正在修复文件记录 0x%1 的文件属性。 |
Repairing the file attributes for file record 0x%1. |
| 0x000061AD | 正在删除文件记录 0x%3 的类型代码 0x%1 和实例标记 0x%2 的属性。 |
Deleting attribute of type code 0x%1 and instance tag 0x%2for file record 0x%3. |
| 0x000061AE | 正在修复文件记录 0x%1 的标志。 |
Repairing the flags for file record 0x%1. |
| 0x000061AF | 正在添加文件记录 0x%2 的类型代码 0x%1 的属性。 |
Adding attribute of type code 0x%1 for file record 0x%2. |
| 0x000061B0 | 在 %2/%3/%1 的 %4:%5:%6:%7% 开始修复 |
Start repair on %2/%3/%1 at %4:%5:%6:%7% |
| 0x000061B1 | 在 %2/%3/%1 的 %4:%5:%6:%7 结束修复 |
End repair on %2/%3/%1 at %4:%5:%6:%7 |
| 0x000061B2 | 在 MFT 位图中将文件记录 %1 标记为使用中。 |
Marked file record %1 as in use in MFT bitmap. |
| 0x000061B3 | 安全 ID 0x%2 在文件记录段 0x%1 中无效。它将被替换为仅管理员使用的安全 ID。 |
Security Id 0x%2 is invalid in file record segment 0x%1.It will be replaced with an administrator only Security Id. |
| 0x000061B4 | 类型代码为 0x%2 和实例标记为 0x%3 的属性 %4 中的 %5 个群集被卷位图中的文件 0x%1 标记为使用中。 |
Marked %5 clusters in attribute %4 of type code 0x%2 and instance tag 0x%3as in use by file 0x%1 in the volume bitmap. |
| 0x000061B5 | 正在处理修复动词 BadFrs: 0x%1标志: 0x%2，0x%3 |
Processing repair verb BadFrs: 0x%1Flags: 0x%2, 0x%3 |
| 0x000061B6 | 正在处理修复动词 InvalidSid: 0x%1，0x%2，0x%3,,, 0x%4标志: 0x%5，0x%6 |
Processing repair verb InvalidSid: 0x%1, 0x%2, 0x%3,,, 0x%4Flags: 0x%5, 0x%6 |
| 0x000061B7 | 正在处理修复动词 FrsAllocate: 0x%1，0x%2，“%3”，0x%4，0x%5，0x%6标志: 0x%7，0x%8 |
Processing repair verb FrsAllocate: 0x%1, 0x%2, \"%3\", 0x%4, 0x%5, 0x%6Flags: 0x%7, 0x%8 |
| 0x000061B8 | 正在处理修复动词 Connect: 0x%1，“%2”，0x%3，0x%4，0x%5,,, 0x%6标志: 0x%7，0x%8 |
Processing repair verb Connect: 0x%1, \"%2\", 0x%3, 0x%4, 0x%5,,, 0x%6Flags: 0x%7, 0x%8 |
| 0x000061B9 | 正在处理修复动词 IndexEntry: 0x%1，“%2”，“%3”标志: 0x%4，0x%5 |
Processing repair verb IndexEntry: 0x%1, \"%2\", \"%3\"Flags: 0x%4, 0x%5 |
| 0x000061BA | 正在处理修复动词 OrphanChildFrs: 0x%1，0x%2,,, 0x%3标志: 0x%4，0x%5 |
Processing repair verb OrphanChildFrs: 0x%1, 0x%2,,, 0x%3Flags: 0x%4, 0x%5 |
| 0x000061C6 | 此修复生成的消息太多。已跳过 %1 条消息。 |
This repair generated too many messages. %1 messages were skipped. |
| 0x000061C7 | 正在将类型代码为 0x%1、实例标记为 0x%2 的属性与文件记录 0x%5 中类型代码为 0x%3、实例标记为 0x%4 的属性交换。 |
Swapping attribute of type code 0x%1 and instance tag 0x%2 withattribute of type code 0x%3 and instance tag 0x%4 for file record 0x%5. |
| 0x00006590 | 正在删除损坏的文件记录段 0x%1。 |
Deleting corrupt file record segment 0x%1. |
| 0x000065AA | 对于类型代码为 0x%2 和实例标记为 0x%3 的属性 %4 中的 0x%7 群集，文件 0x%1 将开始位置在 VCN 0x%5 (LCN 0x%6)的群集在卷位图中标记为使用中。 |
Marking cluster starting at VCN 0x%5 with LCN 0x%6 for 0x%7 clusters inattribute %4 of type code 0x%2 and instance tag 0x%3as in use by file 0x%1 in the volume bitmap. |
| 0x000065CA | 正在更正文件 0x%1 中的小错误。 |
Correcting a minor error in file 0x%1. |
| 0x000065CE | 对于类型代码为 0x%2 和实例标记为 0x%3 的属性 %4 中的 0x%7 群集，文件 0x%1 将开始位置在 VCN 0x%5 ( LCN 0x%6)的群集在卷位图中标记为未使用。 |
Marking cluster starting at VCN 0x%5 with LCN 0x%6 for 0x%7 clusters inattribute %4 of type code 0x%2 and instance tag 0x%3as not in use by file 0x%1 in the volume bitmap. |
| 0x000065D1 | 正在删除文件 0x%1 的索引 0x%2 中的索引项 %3。 |
Deleting index entry %3 in index 0x%2 of file 0x%1. |
| 0x000065E4 | 正在删除文件 0x%1 的索引 0x%2 中的索引项。 |
Deleting an index entry from index 0x%2 of file 0x%1. |
| 0x000065F5 | 将索引项 %3 插入文件 0x%1 的索引 0x%2 中。 |
Inserting an index entry %3 into index 0x%2 of file 0x%1. |
| 0x0000660F | 将 ID 为 0x%3 的索引项插入文件 0x%1 的索引 0x%2 中。 |
Inserting an index entry with Id 0x%3 into index 0x%2 of file 0x%1. |
| 0x00006784 | 对于文件 0x%1 中的文件名实例 0x%2，将文件名标志从 0x%3 更改为 0x%4。 |
Change file name flags from 0x%3 to 0x%4 forfile name instance 0x%2 in file 0x%1. |
| 0x00006978 | 卷具有超过 32 位的 0x%1 文件记录段。 |
Volume has 0x%1 file record segments which is more than 32 bits. |
| 0x00006979 | 没有为文件 0x%1 设置文件名索引当前位。 |
The file name index present bit is not set for file 0x%1. |
| 0x0000697A | 没有为文件 0x%1 设置查看索引当前位。 |
The view index present bit is not set for file 0x%1. |
| 0x0000697B | 没有为文件 0x%1 设置系统文件位。 |
The system file bit is not set for file 0x%1. |
| 0x0000697C | 文件 0x%1 缺少 %2 索引。 |
The %2 index is missing from file 0x%1. |
| 0x0000697D | EA 信息是正确的。 实际 磁盘上PackedEaSize 0x%1 0x%4NeedEaCount 0x%2 0x%5UnpackedEaSize 0x%3 0x%6 |
EA Information is incorrect. Actual On DiskPackedEaSize 0x%1 0x%4NeedEaCount 0x%2 0x%5UnpackedEaSize 0x%3 0x%6 |
| 0x0000697E | EA INFORMATION 属性与文件 0x%1 的 EA DATA 属性不一致。如同 EA DATA 等于 0x%3，EA INFORMATION 等于 0x%2。 |
The EA INFORMATION attribute is not consistency with the EA DATA attributefor file 0x%1. EA INFORMATION equals 0x%2 while EA DATA equals 0x%3. |
| 0x0000697F | 对于文件 0x%1，EA INFORMATION 不可读取。 |
The EA INFORMATION is not readable for file 0x%1. |
| 0x00006980 | 文件 0x%1 中的 EA INFORMATION 大小 0x%2 不正确。要求的大小是 0x%3。 |
The EA INFORMATION size, 0x%2, in file 0x%1 is incorrect.The expected size is 0x%3. |
| 0x00006981 | 对于文件 0x%1，EA DATA 不可读取。 |
The EA DATA is not readable for file 0x%1. |
| 0x00006982 | 文件 0x%1 中的 EA DATA 大小 0x%2 不正确。要求的大小是 0x%3。 |
The EA DATA size, 0x%2, in file 0x%1 is incorrect.The expected size is 0x%3. |
| 0x00006983 | %1%2 |
%1%2 |
| 0x00006984 | 文件 0x%1 的损坏的 EA 集。剩余长度 0x%2太小。 |
Corrupt EA set for file 0x%1. The remaining length, 0x%2,is too small. |
| 0x00006985 | 文件 0x%1 的损坏的 EA 集。分离总长度 0x%2大于数据总长度 0x%3。 |
Corrupt EA set for file 0x%1. The unpacked total length, 0x%2,is larger than the total data length, 0x%3. |
| 0x00006986 | 文件 0x%1 的损坏的 EA 集。EA 名称的长度是 0x%2。 |
Corrupt EA set for file 0x%1. The EA name is of length 0x%2. |
| 0x00006987 | 文件 0x%1 的损坏的 EA 集。未打包总长度 0x%2与记录长度 0x%3 不一样。 |
Corrupt EA set for file 0x%1. The unpacked length, 0x%2,is not the same as the record length, 0x%3. |
| 0x00006988 | 文件 0x%2 中的 EA 信息数值长度 0x%1 不正确。 |
The EA Information value length, 0x%1, in file 0x%2 is incorrect. |
| 0x00006989 | EA 的总打包长度 0x%2 在文件 0x%1 中太长。 |
The EA total packed length, 0x%2, is too large in file 0x%1. |
| 0x0000698A | 在启动扇区中启动 LCN 的第二个 MFT 不正确。要求的数值是 0x%1，而实际数值为 0x%2。 |
The second MFT starting LCN in the boot sector is incorrect.The actual value is 0x%2 while the expected value is 0x%1. |
| 0x0000698B | 重新分析点长度 0x%1 超过了最大值 0x%2。 |
The reparse point length, 0x%1, has exceeded a maximum of 0x%2. |
| 0x0000698C | 重分析点长度 0x%1 少于最大值 0x%2。 |
The reparse point length, 0x%1, is less than a minimum of 0x%2. |
| 0x0000698D | 无法读取重分析点数据缓冲区。 |
Unable to read reparse point data buffer. |
| 0x0000698E | 从读取重分析数据缓冲区的 0x%d 个字节中只返回了 0x%1 个字节。 |
Only 0x%1 bytes returned from a read of 0x%d bytesof the reparse data buffer. |
| 0x0000698F | ReparseDataLength 0x%1 与属性长度 0x%2 不一致。 |
ReparseDataLength, 0x%1, inconsistence with the attribute length 0x%2. |
| 0x00006990 | 重分析标记 0x%1 是一个保留标记。 |
Reparse Tag, 0x%1, is a reserved tag. |
| 0x00006992 | 文件 0x%1 有一个不正确的重分析点属性。 |
File 0x%1 has bad reparse point attribute. |
| 0x00006993 | 重分析点和 EA INFORMATION 属性都在文件 0x%1 中。 |
Both reparse point and EA INFORMATION attributes exist in file 0x%1. |
| 0x00006994 | 属性定义表长度 0x%1 不能除以 0x%2。 |
The attribute definition table length, 0x%1, is not divisible by 0x%2. |
| 0x00006995 | 找不到序列号为 0x%2 的子 frs 0x%1。 |
Unable to find child frs 0x%1 with sequence number 0x%2. |
| 0x00006996 | 在文件 0x%4 中找不到类型为 0x%1、最低 vcn 为 0x%2、实例标记为 0x%3 的属性。 |
Unable to locate attribute of type 0x%1, lowest vcn 0x%2,instance tag 0x%3 in file 0x%4. |
| 0x00006997 | 这是文件 0x%1 中属性列表之内的属性列表属性。 |
The is an attribute list attribute within the attribute list in file 0x%1. |
| 0x00006998 | 在文件 0x%4 中，类型为 0x%1、实例标记为 0x%3 的属性的最低vcn 0x%2 不是零。 |
The lowest vcn, 0x%2, is not zero for attribute of type 0x%1and instance tag 0x%3 in file 0x%4. |
| 0x00006999 | 在文件 0x%3 中，类型为 0x%1的属性的最低 vcn 0x%2 不是零。 |
The lowest vcn, 0x%2, is not zero for attribute of type 0x%1in file 0x%3. |
| 0x0000699A | 在文件 0x%3 中，类型为 0x%1、实例标记为 0x%2的第一个属性不应常驻。 |
The first attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be resident. |
| 0x0000699B | 文件 0x%3 中的类型 0x%1 和实例标记 0x%2的属性不应该是常驻的。 |
The attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be resident. |
| 0x0000699C | 在文件 0x%5 中，实例标记为 0x%2 和 0x%4 的属性分别有不同的类型代码 0x%1 和 0x%3。 |
The attributes with instance tags 0x%2 and 0x%4 have differenttype codes 0x%1 and 0x%3 respectively in file 0x%5. |
| 0x0000699D | 在文件 0x%6 中，具有相同类型代码 0x%1 但不同实例标记0x%2 和 0x%4 的属性有不连贯的 VCN 号码0x%3 和 0x%5。 |
The attributes with same type code 0x%1 but different instance tags0x%2 and 0x%4 have non-contiguous VCN numbers 0x%3 and 0x%5respectively in file 0x%6. |
| 0x0000699E | 在文件 0x%6 中，具有相同类型代码 0x%1 但不同实例标记0x%2 和 0x%4 的属性有不同的名称%3 和 %5。 |
The attributes with same type code 0x%1 but different instance tags0x%2 and 0x%4 have different names %3 and %5respectively in file 0x%6. |
| 0x0000699F | 在文件 0x%5 中，类型为 0x%1、实例标记为 0x%2 的属性分配了长度 0x%3，而不是 0x%4。 |
The attribute of type 0x%1 and instance tag 0x%2 in file 0x%5has allocated length of 0x%3 instead of 0x%4. |
| 0x000069A0 | 在文件 0x%4 中，类型为 0x%1 的属性分配了长度 0x%2，而不是 0x%3。 |
The attribute of type 0x%1 in file 0x%4 has allocated lengthof 0x%2 instead of 0x%3. |
| 0x000069A1 | 文件 0x%3 中的文件属性标志 0x%1 不正确。要求的数值是 0x%2。 |
The file attributes flag 0x%1 in file 0x%3 is incorrect.The expected value is 0x%2. |
| 0x000069A2 | 文件 0x%2 中的序列号 0x%1 不正确。 |
The sequence number 0x%1 in file 0x%2 is incorrect. |
| 0x000069A3 | 在文件 0x%5 中，类型为 0x%1、实例标记为 0x%2 的属性的总分配大小0x%3 不正确。要求的数值是 %4。 |
The total allocated size 0x%3 of attribute of type 0x%1 and instancetag 0x%2 in file 0x%5 is incorrect. The expected value is %4. |
| 0x000069A4 | 读取失败，状态 0x%1 位于 0x%3 字节的偏移量 0x%2 处。 |
Read failure with status 0x%1 at offset 0x%2 for 0x%3 bytes. |
| 0x000069A5 | 在 0x%3 字节的偏移量 0x%1 处读取不正确，但是获得了 0x%2 字节。 |
Incorrect read at offset 0x%1 for 0x%3 bytes but got 0x%2 bytes. |
| 0x000069A6 | 0x%3 字节的偏移量 0x%2 处的状态为 0x%1 的写入故障。 |
Write failure with status 0x%1 at offset 0x%2 for 0x%3 bytes. |
| 0x000069A7 | 0x%3 字节的偏移量 0x%1 处的写入不正确，但写入了 0x%2 字节。 |
Incorrect write at offset 0x%1 for 0x%3 bytes but wrote 0x%2 bytes. |
| 0x000069A8 | 写出的数据与在 0x%2 字节的偏移量 0x%1处读回的数据不同。 |
The data written out is different from what is being read backat offset 0x%1 for 0x%2 bytes. |
| 0x000069A9 | 文件 0x%1 属于父项 0x%3，但却得到了 0x%2 作为其父项。 |
The file 0x%1 belongs to parent 0x%3 but got 0x%2 as parent. |
| 0x000069AA | 文件 0x%1 具有文件名 %2，文件名应该是 %3。 |
The file 0x%1 has file name %2 when it should be %3. |
| 0x000069AB | 总大小为 0x%1、USA 偏移量为 0x%2 并且 USA 计数为 0x%3 的多扇区头不正确。 |
The multi-sector header with total size 0x%1, USA offset 0x%2,and USA count 0x%3 is incorrect. |
| 0x000069AC | 块 0x%1 处的 USA 检查数值 0x%2 不正确。要求的数值是 0x%3。 |
The USA check value, 0x%2, at block 0x%1 is incorrect.The expected value is 0x%3. |
| 0x000069AD | 无法从类型为 0x%1 的属性的 VCN 0x%2 中查询 LCN。 |
Unable to query LCN from VCN 0x%2 for attribute of type 0x%1. |
| 0x000069AE | 类型为 0x%1、实例标记为 0x%2 的属性记录在0x%3 处开始交叉链接，大约占 0x%4 个簇。 |
Attribute record of type 0x%1 and instance tag 0x%2 is cross linkedstarting at 0x%3 for possibly 0x%4 clusters. |
| 0x000069AF | 类型 0x%1 的属性记录在 0x%3 个群集的群集0x%2 处开始交叉链接。 |
Attribute record of type 0x%1 is cross linked starting atcluster 0x%2 for possibly 0x%3 clusters. |
| 0x000069B0 | 文件 0x%1 中的属性列表不包含标准信息属性。 |
The attribute list in file 0x%1 does not containstandard information attribute. |
| 0x000069B1 | 文件 0x%1 中的属性列表表明标准信息属性在基本文件记录段外。 |
The attribute list in file 0x%1 indicates the standard informationattribute is outside the base file record segment. |
| 0x000069B2 | 文件 0x%1 中缺少索引根 %2。 |
The index root %2 is missing in file 0x%1. |
| 0x000069B3 | 文件 0x%1 中缺少索引位图 %2。 |
The index bitmap %2 is missing in file 0x%1. |
| 0x000069B4 | 文件 0x%1 中的索引位图 %2 不正确。 |
The index bitmap %2 in file 0x%1 is incorrect. |
| 0x000069B5 | 索引位图 %2 存在，但在文件 0x%1 中没有相应的索引分配属性。 |
The index bitmap %2 is present but there is no correspondingindex allocation attribute in file 0x%1. |
| 0x000069B6 | 文件 0x%4 中的根索引 %1 的长度 0x%2太小。最短长度为 0x%3。 |
The length, 0x%2, of the root index %1 in file 0x%4is too small. The minimum length is 0x%3. |
| 0x000069B7 | 文件 0x%3 中的根索引 %1 不正确。要求的名称为 %2。 |
The root index %1 in file 0x%3 is incorrect.The expected name is %2. |
| 0x000069B8 | 文件 0x%2 中索引根 %1 的排序规则 0x%3不正确。要求的数值是 0x%4。 |
The collation rule 0x%3 for index root %1 in file 0x%2is incorrect. The expected value is 0x%4. |
| 0x000069B9 | 正在打破父项 0x%1 和子项 0x%2 的文件关系。这也使子项成为孤立的。 |
Breaking the parent 0x%1 and child 0x%2file relationship. This also makes the child an orphan. |
| 0x000069BA | 在文件 0x%4 中，索引根为 %1、类型为 0x%2 的索引属性不正确。要求的数值是 0x%3。 |
The index attribute of type 0x%2 for index root %1in file 0x%4 is incorrect. The expected value is 0x%3. |
| 0x000069BB | 在文件 0x%2 中，索引 %1 是一个未知配额索引。 |
The index %1 is not a known quota index in file 0x%2. |
| 0x000069BC | 索引 %1 在文件 0x%2 中是个未知安全索引。 |
The index %1 is not a known security index in file 0x%2. |
| 0x000069BD | 在文件 0x%3 中，索引根为 %1、类型为 0x%2 的索引属性无法识别。 |
The index attribute of type 0x%2 for index root %1in file 0x%3 is not recognized. |
| 0x000069BE | 在文件 0x%3 中，索引根为 %1、类型为 0x%2 的索引属性不可编制索引。 |
The index attribute of type 0x%2 for index root %1in file 0x%3 is not indexable. |
| 0x000069BF | 在文件 0x%4 中，索引根 %1 的每索引缓冲区字节0x%2 不正确。要求的数值是 0x%3。 |
The bytes per index buffer, 0x%2, for index root %1 in file0x%4 is incorrect. The expected value is 0x%3. |
| 0x000069C0 | 在文件 0x%4 中，索引根 %1 的每索引缓冲区簇0x%2 不正确。要求的数值是 0x%3。 |
The clusters per index buffer, 0x%2, for index root %1 in file0x%4 is incorrect. The expected value is 0x%3. |
| 0x000069C1 | 文件 0x%4 中的索引 %1 的索引分配数值长度0x%2 不是 0x%3 的倍数。 |
The index allocation value length, 0x%2, for index %1 in file0x%4 is not in multiple of 0x%3. |
| 0x000069C2 | 在文件 0x%4 中，索引 %1 的索引分配分配的长度0x%2 不是 0x%3 的倍数。 |
The index allocation allocated length, 0x%2, for index %1 in file0x%4 is not in multiple of 0x%3. |
| 0x000069C3 | 在文件 0x%4 中，根索引 %1 的第一个可用字节 0x%2 和可用的字节 0x%3 不相等。 |
The first free byte, 0x%2, and bytes available, 0x%3, forroot index %1 in file 0x%4 are not equal. |
| 0x000069C4 | 文件 0x%4 中的索引 %1 和 VCN 0x%2 的索引项偏移量0x%3 不正确。 |
The index entry offset, 0x%3, of index %1 and VCN 0x%2in file 0x%4 is incorrect. |
| 0x000069C5 | 文件 0x%3 中的索引 %1 的索引项偏移量 0x%2不正确。 |
The index entry offset, 0x%2, of index %1in file 0x%3 is incorrect. |
| 0x000069C6 | 在文件 0x%4 中，索引 %1 的索引头中的可用字节 0x%2不等于 0x%3。 |
The bytes available, 0x%2, in index header for index %1 in file0x%4 is not equal to 0x%3. |
| 0x000069C7 | 在文件 0x%3 中，索引 %1 和 VCN 0x%2 的索引头没有被标为索引节点。 |
The index header for index %1 and VCN 0x%2 in file 0x%3is not marked as index node. |
| 0x000069C8 | 在文件 0x%3 中，索引 %1 的 VCN 0x%2 不正确。 |
The VCN 0x%2 of index %1 in file 0x%3 is incorrect. |
| 0x000069C9 | 文件 0x%2 中的索引 %1 的索引位图无效或找不到。 |
The index bitmap for index %1 in file 0x%2 is invalid or missing. |
| 0x000069CA | 文件 0x%3 中的索引 %1 的 VCN 0x%2 已在使用中。 |
The VCN 0x%2 of index %1 in file 0x%3 is already in use. |
| 0x000069CB | 在文件 0x%2 中，索引 %1 的索引分配无效或丢失。 |
The index allocation for index %1 in file 0x%2 is invalid or missing. |
| 0x000069CC | 文件 0x%3 中的索引 %1 的 VCN 0x%2 多扇区标头签名不正确。 |
The multi-sector header signature for VCN 0x%2 of index %1in file 0x%3 is incorrect. |
| 0x000069CD | 在文件 0x%5 中，索引 %1 的 VCN 0x%2 的 USA 偏移量 0x%3低于 0x%4。 |
The USA offset 0x%3 of VCN 0x%2 of index %1in file 0x%5 is below 0x%4. |
| 0x000069CE | 在文件 0x%4 中，索引 %1 的 VCN 0x%2 与存储在索引缓冲区内的 VCN 0x%3 不一致。 |
The VCN 0x%2 of index %1 in file 0x%4 is inconsistence withthe VCN 0x%3 stored inside the index buffer. |
| 0x000069CF | 从文件 0x%4 中索引 %1 的 VCN 0x%2 索引缓冲区读取的每块字节数 0x%3 不正确。 |
The bytes per block, 0x%3, read from index buffer of VCN 0x%2of index %1 in file 0x%4 is incorrect. |
| 0x000069D0 | 在文件 0x%4 中，索引 %1 的 VCN 0x%2 的 USA 偏移量 0x%3不正确。 |
The USA offset 0x%3 of VCN 0x%2 of index %1in file 0x%4 is incorrect. |
| 0x000069D1 | 在文件 0x%5 中，索引 %1 的 VCN 0x%2 的 USA 大小 0x%3不正确。要求的数值是 0x%4。 |
The USA size 0x%3 of VCN 0x%2 of index %1 in file0x%5 is incorrect. The expected value is 0x%4. |
| 0x000069D2 | 文件 0x%2 中的索引 %1 的索引标头被标为索引节点，但不应该被标为索引节点。 |
The index header of index %1 in file 0x%2is marked as index node when it should not. |
| 0x000069D3 | 在文件 0x%4 中，索引 %1 的索引头中的第一个可用字节 0x%2不等于 0x%3。 |
The first free byte, 0x%2, in index header of index %1in file 0x%4 is not equal to 0x%3. |
| 0x000069D4 | 在父项为 0x%1 的文件 0x%4 中，无法查询索引 %2 的长度为 0x%3的文件名索引项的名称。 |
Unable to query the name of a file name index entry of length 0x%3of index %2 in file 0x%4 with parent 0x%1. |
| 0x000069D5 | 索引 0x%1 的索引项 %2 指向未使用或重复使用的文件 0x%3。 |
Index entry %2 of index 0x%1 points to unused or reused file 0x%3. |
| 0x000069D6 | 索引 0x%1 的某个索引项指向未使用或重复使用的文件 0x%2。 |
An index entry of index 0x%1 points to unused or reused file 0x%2. |
| 0x000069D7 | 父文件为 0x%1 的索引 %2 的索引项 %3 指向的文件0x%4 不是基本文件记录段。 |
The file 0x%4 pointed to by index entry %3 of index %2 withparent file 0x%1 is not a base file record segment. |
| 0x000069D8 | 父文件为 0x%1 的索引 %2 的索引项指向的文件0x%3 不是基本文件记录段。 |
The file 0x%3 pointed to by an index entry of index %2 withparent file 0x%1 is not a base file record segment. |
| 0x000069D9 | 在文件 0x%4 中，找不到父项为 0x%1 的索引 %2 的索引项%3 的文件名属性。 |
Unable to locate the file name attribute of index entry %3of index %2 with parent 0x%1 in file 0x%4. |
| 0x000069DA | 在文件 0x%3 中，找不到父项为 0x%1 的索引 %2 的索引项的文件名属性。 |
Unable to locate the file name attribute of an index entryof index %2 with parent 0x%1 in file 0x%3. |
| 0x000069DB | 文件 0x%1 中的对象 ID 索引项指向文件 0x%2，但该文件中没有对象 ID。 |
The object id index entry in file 0x%1 points to file 0x%2but the file has no object id in it. |
| 0x000069DC | 文件 0x%1 中的对象 ID 索引项指向不是基本文件记录段的文件 0x%2。 |
The object id index entry in file 0x%1 points to file 0x%2which is not a base file record segment. |
| 0x000069DD | 在文件 0x%1 中，索引项中的对象 ID 不正确。项指向文件 0x%2。 |
The object id in index entry in file 0x%1 is incorrect.The entry points to file 0x%2. |
| 0x000069DE | 在文件 0x%1 中，对象 ID 索引项中的父项 0x%2 不正确。正确的数值是 0x%3。 |
The parent 0x%2 in an object id index entry in file 0x%1is incorrect. The correct value is 0x%3. |
| 0x000069DF | 文件 0x%2 中的对象 ID 已存在于文件 0x%1 的对象 ID 索引中。 |
The object id in file 0x%2 already existed in the objectid index in file 0x%1. |
| 0x000069E0 | 文件 0x%2 中的对象 ID 似乎不在文件 0x%1 中的对象 id 索引。 |
The object id in file 0x%2 does not appear in the objectid index in file 0x%1. |
| 0x000069E1 | 文件 0x%1 中的重分析点索引项指向不是基本文件记录段的文件 0x%2。 |
The reparse point index entry in file 0x%1 points to file 0x%2which is not a base file record segment. |
| 0x000069E2 | 文件 0x%1 中的重分析点索引项的重分析标记 0x%2不正确。文件 0x%4 中的正确重分析标记是 0x%3。 |
The reparse tag 0x%2 of reparse point index entry in file 0x%1is incorrect. The correct reparse tag in file 0x%4 is 0x%3. |
| 0x000069E3 | 文件 0x%1 中具有标记 0x%4 的重分析点索引项中的父项 0x%2不正确。正确的数值是 0x%3。 |
The parent 0x%2 in the reparse point index entry with tag 0x%4in file 0x%1 is incorrect. The correct value is 0x%3. |
| 0x000069E4 | 文件 0x%1 中的重新分析点索引项指向文件 0x%2，但是该文件中没有重新分析点。 |
The reparse point index entry in file 0x%1 points to file 0x%2but the file has no reparse point in it. |
| 0x000069E5 | 文件 0x%2 中的重分析点似乎不在文件 0x%1 中的重分析点索引中。 |
The reparse point in file 0x%2 does not appear inthe reparse point index in file 0x%1. |
| 0x000069E6 | 文件 0x%1 中设置了文件名索引当前位，但是没有文件名索引。 |
The file name index present bit is set in file 0x%1but there is no file name index. |
| 0x000069E7 | 文件 0x%1 中的根索引 %2 找不到或无效。 |
The root index %2 in file 0x%1 is missing or invalid. |
| 0x000069E8 | 索引项长度 0x%1 不正确。最大值为 0x%2。 |
The index entry length 0x%1 is incorrect. The maximum value is 0x%2. |
| 0x000069E9 | 索引项类型 0x%1 的索引项属性长度 0x%2不正确。正确的长度是 0x%3。 |
The index entry attribute length 0x%2 of index entry type 0x%1is incorrect. The correct length is 0x%3. |
| 0x000069EA | 索引项数据偏移量 0x%1 和长度 0x%2 与索引项长度 0x%3 不一致。 |
The index entry data offset 0x%1 and length 0x%2 isinconsistence with the index entry length 0x%3. |
| 0x000069EB | 索引项长度对于索引项类型 0x%1 不正确。 |
The index entry length is incorrect for index entry type 0x%1. |
| 0x000069EC | 索引项长度对于索引项类型 0x%1 太小。 |
The index entry length is too small for index entry type 0x%1. |
| 0x000069ED | 文件 0x%1 中缺少卷信息属性。 |
The volume information attribute is missing from file 0x%1. |
| 0x000069EE | 属性记录长度 0x%1 对于类型为 0x%3、实例标记为 0x%4的属性太小。最小值是 0x%2。 |
The attribute record length 0x%1 is too small for attribute oftype 0x%3 and instance tag 0x%4. The minimum value is 0x%2. |
| 0x000069EF | 属性格式代码 0x%1 对于类型为 0x%2、实例标记为 0x%3 的属性无效。 |
The attribute form code 0x%1 is invalid for attribute of type 0x%2and instance tag 0x%3. |
| 0x000069F0 | 类型为 0x%1、实例标记为 0x%2 的属性应该是常驻的。 |
The attribute of type 0x%1 and instance tag 0x%2 should be resident. |
| 0x000069F1 | 标准信息属性长度 0x%1 不正确。预期的值为 0x%2、0x%3 或 0x%4。 |
The standard information attribute length 0x%1 is incorrect.The expected value is 0x%2, 0x%3, or 0x%4. |
| 0x000069F2 | 类型为 0x%1、实例标记为 0x%2 的属性不允许属性名。 |
Attribute name is not allowed for attribute of type 0x%1and instance tag 0x%2. |
| 0x000069F3 | 类型为 0x%1、实例标记为 0x%2 的属性不应该是常驻的。 |
The attribute of type 0x%1 and instance tag 0x%2 should not be resident. |
| 0x000069F4 | 类型为 0x%1、实例标记为 0x%2 的属性的属性名偏移量不正确。 |
The attribute name offset for attribute of type 0x%1and instance tag 0x%2 is incorrect. |
| 0x000069F5 | 类型为 0x%1、实例标记为 0x%2 的属性的属性名包含 unicode NULL。 |
The attribute name for attribute of type 0x%1 and instance tag 0x%2contains unicode NULL. |
| 0x000069F6 | 类型为 0x%1、实例标记为 0x%2 的未知属性。 |
Unknown attribute of type 0x%1 and instance tag 0x%2. |
| 0x000069F7 | 不应该对类型为 0x%1、实例标记为 0x%2 的属性编制索引。 |
The attribute of type 0x%1 and instance tag 0x%2 should not be indexed. |
| 0x000069F8 | 应该对类型为 0x%1、实例标记为 0x%2 的属性编制索引。 |
The attribute of type 0x%1 and instance tag 0x%2 should be indexed. |
| 0x000069F9 | 类型 0x%1 和实例标记 0x%2 的可加索引的属性不应该有名称。 |
The indexable attribute of type 0x%1 and instance tag 0x%2should not have name. |
| 0x000069FA | 类型为 0x%1、实例标记为 0x%2 的属性应该有名称。 |
The attribute of type 0x%1 and instance tag 0x%2 should have a name. |
| 0x000069FB | 类型为 0x%3、实例标记为 0x%4 的属性的属性长度0x%1 太小。最小值是 0x%2。 |
The attribute length 0x%1 for attribute of type 0x%3 andinstance tag 0x%4 is too small. The minimum value is 0x%2. |
| 0x000069FC | 类型为 0x%3、实例标记为 0x%4 的属性的属性长度 0x%1 太大。最大值是 0x%2。 |
The attribute length 0x%1 for attribute of type 0x%3 andinstance tag 0x%4 is too big. The maximum value is 0x%2. |
| 0x000069FD | 类型为 0x%4、实例标记为 0x%5 的属性的常驻属性不正确。属性有长度 0x%1和偏移量 0x%2 的数值。属性长度为 0x%3。 |
The resident attribute for attribute of type 0x%4 and instancetag 0x%5 is incorrect. The attribute has value of length 0x%1,and offset 0x%2. The attribute length is 0x%3. |
| 0x000069FE | 常驻属性名与类型为 0x%4、实例标记为 0x%5 的属性的常驻数值有冲突。属性名偏移量是0x%2，长度是 0x%1，并且属性数值偏移量是 0x%3。 |
The resident attribute name is colliding with the resident value for attributeof type 0x%4 and instance tag 0x%5. The attribute name offset is0x%2, length 0x%1, and the attribute value offset is 0x%3. |
| 0x000069FF | 类型为 0x%3、实例标记为 0x%4 的属性的映射对偏移量 0x%1超过了属性长度 0x%2。 |
The mapping pairs offset 0x%1 for attribute of type 0x%3 and instancetag 0x%4 exceeded the attribute length 0x%2. |
| 0x00006A00 | 类型为 0x%3、实例标记为 0x%4 的属性的映射对偏移量 0x%1太小。最小值是 0x%2。 |
The mapping pairs offset 0x%1 for attribute of type 0x%3 and instancetag 0x%4 is too small. The minimum value is 0x%2. |
| 0x00006A01 | 属性名与类型 %4 和实例标记 0x%5 的属性的映射对有冲突。属性名偏移量是0x%2，长度是 0x%1，并且映射对偏移量是 0x%3。 |
The attribute name is colliding with the mapping pairs for attributeof type %4 and instance tag 0x%5. The attribute name offset is0x%2, length 0x%1, and the mapping pairs offset is 0x%3. |
| 0x00006A02 | 文件 0x%4 中类型 0x%2 和实例标记 0x%3 的属性在属性偏移量 0x%1 上有不正确的映射对。 |
The attribute of type 0x%2 and instance tag 0x%3 in file 0x%4has bad mapping pairs at attribute offset 0x%1. |
| 0x00006A03 | 无法为具有实例标记 0x%2 的属性类型 0x%1初始化范围列表。 |
Unable to initialize an extent list for attribute type 0x%1 withinstance tag 0x%2. |
| 0x00006A04 | 类型为 0x%3、实例标记为 0x%4 的属性的最高 VCN 0x%1 不正确。要求的数值是 0x%2。 |
The highest VCN 0x%1 of attribute of type 0x%3 and instancetag 0x%4 is incorrect. The expected value is 0x%2. |
| 0x00006A05 | 类型为 0x%4、实例标记为 0x%5 的非常驻属性不一致。有效的数据长度是 0x%1，文件大小是 0x%2，分配的长度是 0x%3。 |
The non resident attribute of type 0x%4 and instance tag 0x%5 isinconsistent. The valid data length is 0x%1, file size 0x%2, andallocated length 0x%3. |
| 0x00006A06 | 类型为 0x%4 的非常驻属性不一致。有效的数据长度是 0x%1，文件大小是 0x%2，分配的长度是 0x%3。 |
The non resident attribute of type 0x%4 is inconsistent. The valid datalength is 0x%1, file size 0x%2, and allocated length 0x%3. |
| 0x00006A07 | 分配长度 0x%1 不是类型为 0x%3、实例标记为 0x%4 的属性 0x%2 的倍数。 |
The allocated length 0x%1 is not in multiple of 0x%2 for attributeof type 0x%3 and instance tag 0x%4. |
| 0x00006A08 | 类型为 0x%3、实例标记为 0x%4 的属性的文件名数值长度 0x%1 太小。最小值是 0x%2。 |
The file name value length 0x%1 for attribute of type 0x%3 withinstance tag 0x%4 is too small. The minimum value is 0x%2. |
| 0x00006A09 | 类型为 0x%2、实例标记为 0x%3 的属性不一致。属性数值长度是 0x%1。 |
The attribute of type 0x%2 and instance tag 0x%3 is inconsistence.The attribute value length is 0x%1. |
| 0x00006A0A | 类型 0x%1 和实例标记 0x%2 的属性的文件名长度是零。 |
The file name length is zero for attribute of type 0x%1and instance tag 0x%2. |
| 0x00006A0B | 类型为 0x%1、实例标记为 %2 的属性中文件名数值中的文件名包含无效字符。 |
The file name in file name value in attribute of type 0x%1 and instancetag %2 contains invalid character. |
| 0x00006A0C | 文件 0x%1 中的多扇区标头签名不正确。 |
The multi-sector header signature in file 0x%1 is incorrect. |
| 0x00006A0D | 文件 0x%3 中的 USA 偏移量 0x%1 太小。最小值是 0x%2。 |
The USA offset 0x%1 in file 0x%3 is too small.The minimum value is 0x%2. |
| 0x00006A0E | 文件记录段大小 0x%1 在文件 0x%2 中无效。 |
The file record segment size 0x%1 is invalid in file 0x%2. |
| 0x00006A0F | 文件 0x%2 中的 USA 偏移量 0x%1 不正确。 |
The USA offset 0x%1 in file 0x%2 is incorrect. |
| 0x00006A10 | 文件 0x%3 中的 USA 大小 0x%1 不正确。要求的数值是 0x%2。 |
The USA size 0x%1 in file 0x%3 is incorrect.The expected value is 0x%2. |
| 0x00006A11 | 文件 0x%2 中的第一个属性偏移量 0x%1 不正确。 |
The first attribute offset 0x%1 in file 0x%2 is incorrect. |
| 0x00006A12 | 文件 0x%3 的文件记录段标头中的可用字节 0x%1 不正确。要求的数值是 0x%2。 |
The bytes available, 0x%1, in the file record segment header forfile 0x%3 is incorrect. The expected value is 0x%2. |
| 0x00006A13 | 在文件 0x%3 中，类型为 0x%1 的属性的实例标记 0x%2已在使用中。 |
The instance tag 0x%2 of attribute of type 0x%1 in file 0x%3is already in use. |
| 0x00006A14 | 在文件 0x%4 中，类型为 0x%1 的属性的实例标记 0x%2 太大。实例标记应该少于 0x%3。 |
The instance tag 0x%2 of attribute of type 0x%1 in file 0x%4is too large. The instance tag should be less than 0x%3. |
| 0x00006A15 | 文件 0x%1 中缺少标准信息属性。 |
The standard information attribute in file 0x%1 is missing. |
| 0x00006A16 | 在文件 0x%5 中，属性记录偏移量 0x%1 对于类型为 0x%3、实例标记为 0x%4 的属性太大。最大值是 0x%2。 |
The attribute record offset 0x%1 is too large for attribute of type 0x%3and instance tag 0x%4 in file 0x%5. The maximum value is 0x%2. |
| 0x00006A17 | 在文件 0x%3 中，类型为 0x%1、实例标记为 0x%2 的属性的记录长度不应该是零。 |
The record length of attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be zero. |
| 0x00006A18 | 在文件 0x%4 中，类型为 0x%2、实例标记为 0x%3 的属性的记录长度 0x%1 没有对齐。 |
The record length 0x%1 of attribute of type 0x%2 andinstance tag 0x%3 in file 0x%4 is not aligned. |
| 0x00006A19 | 在文件 0x%5 中，记录长度 0x%1 对于类型为 0x%3、实例标记为 0x%4 的属性太大。最大值是 0x%2。 |
The record length 0x%1 is too large for attribute of type 0x%3and instance tag 0x%4 in file 0x%5. The maximum value is 0x%2. |
| 0x00006A1A | 文件 0x%4 中的第一个可用字节 0x%1 不正确。文件记录段中的可用字节数量为 0x%2，总长度为0x%3。 |
The first free byte, 0x%1, in file 0x%4 is incorrect. The number ofbytes free in the file record segment is 0x%2 and the total lengthis 0x%3. |
| 0x00006A1B | 在文件 0x%5 中，类型为 0x%1、实例标记为 0x%2 的属性应该在类型为 0x%3、实例标记为 0x%4 的属性之后。 |
The attribute of type 0x%1 and instance tag 0x%2 should be afterattribute of type 0x%3 and instance tag 0x%4 in file 0x%5. |
| 0x00006A1C | 在文件 0x%5 中，类型为 0x%1、实例标记为 0x%2 的所有属性都应该编制索引。 |
All attribute of type 0x%1 and instance tag 0x%2 should be indexedin file 0x%5. |
| 0x00006A1D | 类型 0x%1 和实例标记 0x%2 的两个相同属性在文件 0x%3 中。 |
Two identical attributes of type 0x%1 and instance tag 0x%2 arein file 0x%3. |
| 0x00006A1E | 不应该设置文件 0x%1 中的文件名索引当前位。 |
The file name index present bit in file 0x%1 should not be set. |
| 0x00006A20 | 没有设置文件 0x%1 中的标准信息属性中的稀疏标志。 |
The sparse flag in the standard information attribute in file 0x%1is not set. |
| 0x00006A21 | 不应设置文件 0x%1 中标准信息属性内的稀疏标志。 |
The sparse flag in the standard information attribute in file 0x%1should not be set. |
| 0x00006A22 | 旧的加密标志正在被文件 0x%1 中的新加密标志代替。 |
The old encrypted flag is being replaced by the new encrypted flagin file 0x%1. |
| 0x00006A23 | 没有设置文件 0x%1 中的标准信息属性中的加密标志。 |
The encrypted flag in standard information attribute in file 0x%1is not set. |
| 0x00006A24 | 没有设置文件 0x%1 中的标准信息属性中的重新分析标志。 |
The reparse flag in standard information attribute in file 0x%1is not set. |
| 0x00006A25 | 不应该设置文件 0x%1 中的标准信息属性中的重新分析标志。 |
The reparse flag in standard information attribute in file 0x%1should not be set. |
| 0x00006A26 | 文件 0x%1 中存在多个 NTFS 文件名属性。 |
There are more than one NTFS file name attribute in file 0x%1. |
| 0x00006A27 | 文件 0x%3 中的文件名属性具有不同的父项DOS 名称有 0x%1 作为其父项。NTFS 名称有 0x%2 作为其父项。 |
The file name attributes in file 0x%3 has different parents.The DOS name has 0x%1 as parent. The NTFS name has 0x%2 as parent. |
| 0x00006A28 | 文件 0x%1 中有一个以上 DOS 文件名属性。 |
There are more than one DOS file name attribute in file 0x%1. |
| 0x00006A29 | 文件 0x%1 中的 DOS 文件名属性不正确。 |
The DOS file name attribute in file 0x%1 is incorrect. |
| 0x00006A2A | 文件 0x%1 中没有 NTFS 文件名属性。 |
There is no NTFS file name attribute in file 0x%1. |
| 0x00006A2B | 文件 0x%1 中没有 DOS 文件名属性。 |
There is no DOS file name attribute in file 0x%1. |
| 0x00006A2C | 文件 0x%1 中的 DOS 和 NTFS 文件名属性相同。 |
The DOS and NTFS file name attributes in file 0x%1 are identical. |
| 0x00006A2D | 无法在文件 0x%1 中设置属性列表。 |
Unable to setup the attribute list in file 0x%1. |
| 0x00006A2E | 文件 0x%3 中缺少名称为 %2 的属性类型 0x%1。 |
The attribute type 0x%1 with name %2 in file 0x%3 is missing. |
| 0x00006A2F | 文件 0x%2 中缺少类型为 0x%1 的属性。 |
The attribute of type 0x%1 in file 0x%2 is missing. |
| 0x00006A30 | 文件 0x%1 中缺少未命名数据属性。 |
The unnamed data attribute in file 0x%1 is missing. |
| 0x00006A31 | 文件 0x%1 中缺少属性列表。 |
The attribute list in file 0x%1 is missing. |
| 0x00006A32 | 文件 0x%4 中的具有类型 0x%1 和实例标记 0x%2 的属性的属性列表项的长度 0x%3 没有对齐。 |
The length, 0x%3, of the attribute list entry with attribute of type0x%1 and instance tag 0x%2 in file 0x%4 is not aligned. |
| 0x00006A33 | 在文件 0x%6 中，具有类型为 0x%1、实例标记为 0x%2 的属性的属性列表项不正确。属性列表项名称长度为 0x%3，偏移量为 0x%4。属性列表长度为 0x%5。 |
The attribute list entry with attribute of type 0x%1 and instance tag 0x%2in file 0x%6 is incorrect. The attribute list entry name length is 0x%3,and offset 0x%4. The attribute list length is 0x%5. |
| 0x00006A34 | 在文件 0x%5 中，具有类型为 0x%1、实例标记为 0x%2 的属性的属性列表项的属性名偏移量 0x%3 太小。最小值是 0x%4。 |
The attribute name offset 0x%3 of attribute list entry with attribute oftype 0x%1 and instance tag 0x%2 in file 0x%5 is too small.The minimum value is 0x%4. |
| 0x00006A35 | 文件 0x%3 中的属性列表长度 0x%2 不正确。要求的数值是 0x%1。 |
The attribute list length 0x%2 in file 0x%3 is incorrect.The expected value is 0x%1. |
| 0x00006A36 | 属性列表的范围列表可能在文件 0x%3 的 0x%2 群集的0x%1 处交叉链接。 |
The extent list of the attribute list is crossed linked at 0x%1for possibly 0x%2 clusters in file 0x%3. |
| 0x00006A37 | 具有类型为 0x%1、实例标记为 0x%2 的属性的属性列表项应该在类型为 0x%3、实例标记为 0x%4 的属性之后。 |
The attribute list entry with attribute of type 0x%1 and instance tag0x%2 should be after attribute of type 0x%3 and instance tag 0x%4. |
| 0x00006A38 | 找到了两个同样的类型 0x%1 和实例标记 0x%2 的属性列表项。 |
Two identical attribute list entries of type 0x%1 and instance tag 0x%2are found. |
| 0x00006A39 | 在文件 0x%5 中，类型为 0x%1、名称为 %2 的属性的属性长度 0x%3 太小。最小值是 0x%4。 |
The attribute length 0x%3 of attribute of type 0x%1 and name %2 infile 0x%5 is too small. The minimum value is 0x%4. |
| 0x00006A3A | 文件 0x%3 中没有设置类型为 0x%1、名称为 %2 的属性的稀疏标志。 |
The sparse flag of attribute of type 0x%1 and name %2 in file0x%3 is not set. |
| 0x00006A3B | 文件 0x%2 中的 USN 日志偏移量 0x%1 不是页面边界。 |
The USN Journal offset 0x%1 in file 0x%2 is not at a page boundary. |
| 0x00006A3C | 文件 0x%3 中的 USN 日志长度 0x%1 太大。最大值是 0x%2。 |
The USN Journal length 0x%1 in file 0x%3 is too large.The maximum value is 0x%2. |
| 0x00006A3D | 文件 0x%3 中的 USN 日志长度 0x%1 小于其偏移量 0x%2。 |
The USN Journal length 0x%1 in file 0x%3 is less thanits offset 0x%2. |
| 0x00006A3E | 文件 0x%2 中偏移量 0x%1 处的剩余 USN 块少于一个页面。 |
The remaining USN block at offset 0x%1 in file 0x%2 isless than a page. |
| 0x00006A3F | 文件 0x%2 中偏移量 0x%1 处的 USN 页的剩余部分应该用零来填充。 |
The remaining of an USN page at offset 0x%1 in file 0x%2should be filled with zeros. |
| 0x00006A40 | 偏移量 0x%1、长度 0x%2 处的 USN 日志项越过了页面边界。 |
The USN Journal entry at offset 0x%1 and length 0x%2 crossesthe page boundary. |
| 0x00006A41 | 文件 0x%4 中偏移量 0x%1 处的 USN 日志项长度 0x%2 大于一个页面的剩余长度 0x%3。 |
The USN Journal entry length 0x%2 at offset 0x%1, in file0x%4 is larger than the remaining length 0x%3 of a page. |
| 0x00006A42 | 文件 0x%4 中偏移量 0x%1 处的 USN 日志长度 0x%2超出了页面大小 0x%3。 |
The USN Journal entry length 0x%2 at offset 0x%1 in file0x%4 exceeded the page size 0x%3. |
| 0x00006A43 | 文件 0x%3 中偏移量 0x%1 处的 USN 日志长度 0x%2没有对齐。 |
The USN Journal entry length 0x%2 at offset 0x%1 in file0x%3 is not aligned. |
| 0x00006A44 | 文件 0x%4 中偏移量 0x%1 处的 USN 日志项版本 %2.%3不可识别。 |
The USN Journal entry version %2.%3 at offset 0x%1in file 0x%4 is not recognized. |
| 0x00006A45 | 文件 0x%4 中偏移量 0x%1 处的 USN 日志项长度 0x%2太小。最小值是 0x%3。 |
The USN Journal entry length 0x%2 at offset 0x%1 in file0x%4 is too small. The minimum value is 0x%3. |
| 0x00006A46 | 剩余的 USN 页面长度 0x%2 太小，无法容下文件 0x%4中偏移量 0x%1 处的另一个 USN 日志。至少需要 0x%3 个字节。 |
The remaining USN page length 0x%2 is too small to fit anotherUSN Journal entry at offset 0x%1 in file 0x%4.It needs at least 0x%3 bytes. |
| 0x00006A47 | 文件 0x%3 中偏移量 0x%2 处的 USN 日志项的 USN 数值 0x%1 不正确。 |
The USN value 0x%1 of USN Journal entry at offset 0x%2in file 0x%3 is incorrect. |
| 0x00006A48 | 文件 0x%4 中偏移量 0x%1 处的 USN 日志项不一致。项长度为 0x%3，文件名长度为 0x%2。 |
The USN Journal entry at offset 0x%1 in file 0x%4 is notconsistence. The entry has length of 0x%3 and a file name length of 0x%2. |
| 0x00006A49 | 文件 0x%4 中的 USN 日志长度 0x%1 少于遇到的最大 USN: 0x%2，再加上文件 0x%3 中的八个。 |
The USN Journal length 0x%1 in file 0x%4 is less thelargest USN encountered, 0x%2, plus eight in file 0x%3. |
| 0x00006A4A | 文件 0x%1 中缺少安全数据流。 |
The security data stream is missing from file 0x%1. |
| 0x00006A4B | 安全数据流大小 0x%1 应该少于 0x%2。 |
The security data stream size 0x%1 should not be less than 0x%2. |
| 0x00006A4C | 在 0x%2 字节的 0x%1 偏移量处开始的安全数据流页面的剩余部分含有非零值。 |
The remaining of a security data stream page starting at offset 0x%1for 0x%2 bytes contains non-zero. |
| 0x00006A4D | 长度为 0x%2 的偏移量 0x%1 处的安全数据流项越过了页面边界。 |
The security data stream entry at offset 0x%1 with length 0x%2crosses the page boundary. |
| 0x00006A4E | 偏移量 0x%1 处的安全数据流项的长度 0x%2 太小。最小值为 0x%3。 |
The length, 0x%2, of the security data stream entry at offset0x%1 is too small. The minimum value is 0x%3. |
| 0x00006A4F | 偏移量 0x%1 处的安全数据流项的长度 0x%2 超过了页面大小 0x%3。 |
The length, 0x%2, of the security data stream entry at offset0x%1 exceeded the page size 0x%3. |
| 0x00006A50 | 偏移量 0x%1 处的安全数据流项容不进页面的剩余剩余长度 0x%2。最小值是 0x%3。 |
The security data stream entry at offset 0x%1 does not fit into theremaining length, 0x%2, of a page. The minimum value is 0x%3. |
| 0x00006A51 | 偏移量 0x%1 处 ID 为 0x%2 的安全描述符无效。 |
The security descriptor entry with Id 0x%2 at offset 0x%1 is invalid. |
| 0x00006A52 | 偏移量 0x%1 处安全描述符项的安全 ID 0x%2是重复的。 |
The security Id 0x%2 of security descriptor entry at offset 0x%1is a duplicate. |
| 0x00006A53 | 偏移量 0x%1 处的 ID 为 0x%4 的安全描述符项的哈希数值 0x%2 无效。正确的数值为 0x%3。 |
The hash value 0x%2 of the security descriptor entry with Id0x%4 at offset 0x%1 is invalid. The correct value is 0x%3. |
| 0x00006A54 | 存储在偏移量 0x%1 处 ID 为 0x%4 的安全描述符项中的偏移量 0x%2 无效。正确的数值为 0x%3。 |
The offset 0x%2 stored in the security descriptor entry with Id0x%4 at offset 0x%1 is invalid. The correct value is 0x%3. |
| 0x00006A55 | 文件 0x%1 中的安全描述符无效。 |
The security descriptor in file 0x%1 is invalid. |
| 0x00006A56 | 文件 0x%2 中的安全 ID 0x%1 无效。 |
The security Id 0x%1 in file 0x%2 is invalid. |
| 0x00006A57 | 文件 0x%2 中名称为 %1 的数据流无法识别。 |
The data stream with name %1 in file 0x%2 is not recognized. |
| 0x00006A58 | 属性定义表长度 0x%1 不正确。正确的数值是 0x%2。 |
The attribute definition table length 0x%1 is incorrect.The correct value is 0x%2. |
| 0x00006A59 | 属性定义表内容不正确。 |
The attribute definition table content is incorrect. |
| 0x00006A5A | 启动文件的数据属性中缺少群集零。 |
Cluster zero is missing from the data attribute in boot file. |
| 0x00006A5B | 在日志文件中发现属性列表。 |
Attribute list found in the log file. |
| 0x00006A5C | 数据属性是常驻的，或者日志文件中缺少数据属性。 |
The data attribute is either resident or missing in the log file. |
| 0x00006A5D | 在 MFT 镜像的数据属性中无法获得 LCN。 |
Unable to obtain the LCN in data attribute of the MFT mirror. |
| 0x00006A5E | 在 MFT 镜像的数据属性中没有 VCN 0 的物理 LCN。 |
There is no physical LCN for VCN 0 in data attribute of the MFT mirror. |
| 0x00006A5F | MFT 镜像的数据属性对于 0x%1 扇区不是相连的。 |
The data attribute of the MFT mirror is not contiguous for 0x%1 sectors. |
| 0x00006A60 | MFT 镜像不同于 MFT。 |
The MFT mirror is different from the MFT. |
| 0x00006A61 | Upcase 文件缺少数据属性。 |
The data attribute is missing from the upcase file. |
| 0x00006A62 | Upcase 文件长度 0x%1 不正确。要求的数值是 0x%2。 |
The upcase file length 0x%1 is incorrect. The expected value is 0x%2. |
| 0x00006A63 | Upcase 文件内容不正确。 |
The upcase file content is incorrect. |
| 0x00006A64 | 数据属性在 MFT 镜像中是常驻的或找不到。 |
The data attribute is either resident or missing in the MFT mirror. |
| 0x00006A65 | 长度为 0x%1 和 0x%2 的两个索引项相同或者出现的顺序不正确。 |
The two index entries of length 0x%1 and 0x%2 are either identicalor appear in the wrong order. |
| 0x00006A66 | 长度 0x%1 的第一个索引项是一个分叶，但是不在根目录中。 |
The first index entry of length 0x%1 is a leaf but it is not in the root. |
| 0x00006A67 | 长度 0x%1 的第一个索引项是一个分叶，但是上一项不是。 |
The first index entry of length 0x%1 is a leaf but the previous entry is not. |
| 0x00006A68 | 长度 0x%3 的当前叶索引项在深度 0x%2 处，这与深度为 0x%1 的其他叶索引项不同。 |
Current leaf index entry of length 0x%3 is at depth 0x%2 whichis different from other leaf index entry which has a depth of 0x%1. |
| 0x00006A69 | 长度为 0x%1 的当前索引项的向下指针无效。 |
The down pointer of current index entry with length 0x%1 is invalid. |
| 0x00006A6A | 索引项长度 0x%1 太大。最大值是 0x%2。 |
The index entry length 0x%1 is too large. The maximum value is 0x%2. |
| 0x00006A6B | 分配属性不存在。 |
The allocation attribute does not exist. |
| 0x00006A6C | 正在清除没有使用的安全描述符流项。 |
Clearing unused security descriptor stream entries. |
| 0x00006A6D | 镜像安全描述符块与偏移量 0x%1 处的主要安全描述符块不同。 |
Mirror security descriptor block different from that ofmaster security descriptor at offset 0x%1. |
| 0x00006A6E | 无法读取属性定义表。 |
The attribute definition table cannot be read. |
| 0x00006A6F | 无法读取文件 0x%3 中索引 %1 的 VCN 0x%2 处的索引缓冲区。 |
The index buffer at VCN 0x%2 of index %1 in file 0x%3cannot be read. |
| 0x00006A70 | 无法读取在 0x%2 扇区的群集 0x%1 处开始的MFT 镜像。 |
The MFT mirror starting at cluster 0x%1 for 0x%2 sectorscannot be read. |
| 0x00006A71 | 无法读取文件 0x%1 中的安全描述符。 |
The security descriptor in file 0x%1 cannot be read. |
| 0x00006A72 | 无法读取 Upcase 表格。 |
The upcase table cannot be read. |
| 0x00006A73 | 无法读取文件 0x%3 中类型代码为 0x%1、名称为 %2 的USN 属性。 |
The USN attrib of type code 0x%1 and name %2 cannot beread in file 0x%3. |
| 0x00006A74 | 文件 0x%2 中的 EA 数据数值长度 0x%1 不正确。 |
The EA Data value length, 0x%1, in file 0x%2 is incorrect. |
| 0x00006A75 | 文件 0x%4 中的索引 %1 的索引项长度 0x%2 太大。最大值是 0x%3。 |
The index entry length 0x%2 for index %1 in file 0x%4is too large. The maximum value is 0x%3. |
| 0x00006A76 | 无法从类型为 0x%1、实例标记为 0x%2 的属性中查询范围列表项 0x%3。 |
Unable to query extent list entry 0x%3 from attributeof type 0x%1 and instance tag 0x%2. |
| 0x00006A77 | 类型为 0x%3、实例标记为 0x%4 的属性的总分配大小 0x%1大于分配长度 0x%2。 |
The total allocated size 0x%1 for attribute of type 0x%3 andinstance tag 0x%4 is larger than the allocated length 0x%2. |
| 0x00006A78 | 无法找到实例标记为 0x%2、段参考为 0x%3 的属性。要求的属性类型是 0x%1。 |
Unable to locate attribute with instance tag 0x%2 and segmentreference 0x%3. The expected attribute type is 0x%1. |
| 0x00006A79 | 文件 0x%4 中索引 %1 的第一个索引项偏移量 0x%2指向索引的长度 0x%3 之外。VCN 未知。 |
The first index entry offset, 0x%2, for index %1 in file 0x%4points beyond the length, 0x%3, of the index. VCN is unknown. |
| 0x00006A7A | 文件 0x%3 中的类型 0x%1 和实例标记 0x%2 的属性占领的一些群集已在使用中。 |
Some clusters occupied by attribute of type 0x%1 and instance tag 0x%2in file 0x%3 is already in use. |
| 0x00006A7B | 在文件 0x%1 中无法设置子文件记录段 0x%2。 |
Unable to setup the child file record segment 0x%2 in file 0x%1. |
| 0x00006A7C | 文件 0x%4 中索引项 %3 的父项 0x%2 不正确。要求的父项是 0x%1。 |
The parent 0x%2 of index entry %3in file 0x%4 is incorrect. The expected parent is 0x%1. |
| 0x00006A7D | 父项 0x%1 中索引项 %2 的文件参考 0x%3 与 0x%4 不同。 |
The file reference 0x%3 of an index entry %2 inparent 0x%1 is not the same as 0x%4. |
| 0x00006A7E | 父项为 0x%1 的索引 %2 的索引项的文件参考0x%3 与 0x%4 不同。 |
The file reference 0x%3 of an index entry of index %2with parent 0x%1 is not the same as 0x%4. |
| 0x00006A7F | 文件 0x%1 中的多个对象 ID 索引项指向同一个文件 0x%2。 |
Multiple object id index entries in file 0x%1point to the same file 0x%2. |
| 0x00006A80 | 文件 0x%1 中的对象 ID 索引项指向不可读取的文件 0x%2。 |
The object id index entry in file 0x%1 points to file 0x%2which is unreadable. |
| 0x00006A81 | 文件 0x%1 中的对象 ID 索引项指向不在使用中的文件 0x%2。 |
The object id index entry in file 0x%1 points to file 0x%2which is not in use. |
| 0x00006A82 | 文件 0x%1 中的重分析点索引项指向不在使用中的文件 0x%2。 |
The reparse point index entry in file 0x%1 points to file 0x%2which is not in use. |
| 0x00006A83 | 文件 0x%1 中的重分析点索引项指向不可读取的文件 0x%2。 |
The reparse point index entry in file 0x%1 points to file 0x%2which is unreadable. |
| 0x00006A84 | ---------------------------------------------------------------------- |
---------------------------------------------------------------------- |
| 0x00006A85 | 正在清除文件 0x%1 的实例标记。 |
Cleaning up instance tags for file 0x%1. |
| 0x00006A86 | 正在清除文件 0x%1 的加密标志。 |
Cleaning up encrypted flag for file 0x%1. |
| 0x00006A87 | 正在清除文件 0x%1 的稀疏标志。 |
Cleaning up sparse flag for file 0x%1. |
| 0x00006A88 | 正在从文件 0x%1 的索引 %2 清除 %3 个未经使用的索引项。 |
Cleaning up %3 unused index entries from index %2 of file 0x%1. |
| 0x00006A89 | 正在清除 %1 个未经使用的安全描述符。 |
Cleaning up %1 unused security descriptors. |
| 0x00006A8A | MFT 镜像的数值长度 0x%1 太小。最小值为 0x%2。 |
The value length, 0x%1, of the MFT mirror is too small.The minimum value is 0x%2. |
| 0x00006A8B | MFT 镜像的有效数据长度 0x%1 太小。最小值为 0x%2。 |
The valid data length, 0x%1, of the MFT mirror is too small.The minimum value is 0x%2. |
| 0x00006A8C | 文件 0x%1 中的索引 %2 的索引项 %3 指向未使用过的文件 0x%4。 |
Index entry %3 of index %2 in file 0x%1 points to unused file 0x%4. |
| 0x00006A8D | 文件 0x%1 中的索引 %2 的一个索引项指向未使用过的文件 0x%3。 |
An index entry of index %2 in file 0x%1 points to unused file 0x%3. |
| 0x00006A8E | 在 MFT 的 VCN 0x%1 的数据属性中无法获得 LCN。 |
Unable to obtain the LCN in data attribute for VCN 0x%1 of the MFT. |
| 0x00006A8F | 文件 0x%1 中索引 %2 的一个索引项指向文件 0x%3，该文件在 MFT 外。 |
An index entry of index %2 in file 0x%1 points to file 0x%3which is beyond the MFT. |
| 0x00006A90 | 文件 0x%2 中的段号 0x%1 不正确。 |
The segment number 0x%1 in file 0x%2 is incorrect. |
| 0x00006A91 | 内部信息: |
Internal Info: |
| 0x00006A92 | 类型为 0x%2、实例标记为 0x%3 的属性的映射对偏移量 0x%1没有对齐。 |
The mapping pairs offset 0x%1 for attribute of type 0x%2 and instancetag 0x%3 is not quad aligned. |
| 0x00006A93 | 文件 0x%1 中的 NTFS 文件名属性不正确。 |
The NTFS file name attribute in file 0x%1 is incorrect. |
| 0x00006A94 | 类型 0x%1 和实例标记 0x%2 属性在范围列表中有意外的漏洞。 |
The attribute of type 0x%1 and instance tag 0x%2 has unexpected holes in the extent list. |
| 0x00006A95 | 文件 0x%1 中的 TxF 文件名属性已损坏。 |
The TxF file name attribute in file 0x%1 is corrupt. |
| 0x00006A96 | 文件 0x%1 中的 $Txf 文件名属性是副本。 |
The $Txf file name attribute in file 0x%1 is a duplicate. |
| 0x00006A97 | 文件 0x%1 中的 $Txf 文件名属性已损坏。 |
The $Txf file name attribute in file 0x%1 is corrupt. |
| 0x00006A98 | $Txf 目录的 $STANDARD_INFORMATION 属性已损坏。 |
The $STANDARD_INFORMATION attribute was corrupted for a $Txf directory. |
| 0x00006A99 | RM Root 目录的 $STANDARD_INFORMATION 属性已损坏。 |
The $STANDARD_INFORMATION attribute was corrupted for a RM Root directory. |
| 0x00006A9A | 文件 0x%1 中的 TxF 文件名属性是副本。 |
The TxF file name attribute in file 0x%1 is a duplicate. |
| 0x00006A9B | TxF RM 根文件参考已损坏。 |
A TxF RM root file reference was corrupt. |
| 0x00006A9C | 检测到文件记录 0x%3 的类型代码 0x%1 和实例标记 0x%2 的交叉链接属性。 |
Detected cross linked attribute of type code 0x%1 and instance tag 0x%2for file record 0x%3. |
| 0x00006A9D | 文件记录 0x%1 映射到“%2”。 |
File record 0x%1 maps to \"%2\". |
| 0x00006A9E | 缺少文件 0x%1 的索引 0x%2 中的索引项 %3。 |
The index entry %3 in index 0x%2 of file 0x%1 is missing. |
| 0x00006A9F | 找不到文件 0x%3 中的文件名属性 %2 的父 0x%1。 |
The parent 0x%1 of file name attribute %2 in file 0x%3 cannot be found. |
| 0x00006AA0 | 父 0x%3 的索引项 %2 中的文件名标志 0x%1 与文件 0x%4 中的标志不一致。 |
The file name flags 0x%1 in index entry %2 of parent 0x%3 is inconsistentwith that in file 0x%4. |
| 0x00006AA1 | 0x%1 文件中只有标准信息这个属性。 |
The only attribute in the file 0x%1 is the standard information. |
| 0x01000062 | 卷 %1 (%2) %3 |
Volume %1 (%2) %3 |
| 0x0100008C | 系统无法将数据刷新到事务日志。可能发生损坏: VolumeId: %1，DeviceName: %2。%n(%3) |
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: %1, DeviceName: %2.%n(%3) |
| 0x0100008F | Surprise removal of a persistent memory device with active DAX mappings. This might lead to data corruption.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n%nGuidance:%nA reboot is required to clean up the DAX mappings. |
Surprise removal of a persistent memory device with active DAX mappings. This might lead to data corruption.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n%nGuidance:%nA reboot is required to clean up the DAX mappings. |
| 0x01000090 | A volume that already has DAX mappings is being mounted. This generally occurs after surprise removal. This might lead to data corruption.%n%n Volume GUID: %4%n Volume Name: %6%n%nGuidance:%nA reboot is required to clean up the DAX mappings. |
A volume that already has DAX mappings is being mounted. This generally occurs after surprise removal. This might lead to data corruption.%n%n Volume GUID: %4%n Volume Name: %6%n%nGuidance:%nA reboot is required to clean up the DAX mappings. |
| 0x01000096 | An IO failed with %12 and NTFS has relocated the clusters. The original clusters are now marked as bad and they will not be reused.%nThis may indicate a failing disk.%n%n Process Id: %5%n Process name: %6%n File name: %8%n File offset: %9%n %11 cluster(s) were marked as bad starting at cluster %10%n%n Volume guid: %1%n Volume name: %3%n Is boot volume: %4%n |
An IO failed with %12 and NTFS has relocated the clusters. The original clusters are now marked as bad and they will not be reused.%nThis may indicate a failing disk.%n%n Process Id: %5%n Process name: %6%n File name: %8%n File offset: %9%n %11 cluster(s) were marked as bad starting at cluster %10%n%n Volume guid: %1%n Volume name: %3%n Is boot volume: %4%n |
| 0x010000D2 | 以前不会在群集 %3 与 %4 之间映射精简预配的卷 %1 (%2)%n。%n现已修复此问题。 |
Thinly provisioned volume %1 (%2)%nwere not being mapped between clusters %3 and %4.%nIt is now fixed. |
| 0x010000D3 | 以前不会在群集 %3 与 %4 之间映射精简预配的卷 %1 (%2)%n。%n修复未成功。%n可能碎片已用尽。 |
Thinly provisioned volume %1 (%2)%nwere not being mapped between clusters %3 and %4.%nRepair was unsucccessful.%nPossibly out of available slabs. |
| 0x11000016 | 统计信息 |
Statistics |
| 0x11000019 | BadClusterHotFix |
BadClusterHotFix |
| 0x31000000 | 信息 |
Info |
| 0x31000001 | 开始 |
Start |
| 0x31000002 | 停止 |
Stop |
| 0x31000007 | 继续 |
Resume |
| 0x31000008 | 暂停 |
Suspend |
| 0x40040024 | 一个用户已达到卷 %2 上的配额阈值。 |
A user hit their quota threshold on volume %2. |
| 0x40040025 | 一个用户已达到卷 %2 上的配额限量。 |
A user hit their quota limit on volume %2. |
| 0x40040026 | 系统已开始重建带有标签“%2”的设备 %1 上的用户 磁盘限额信息。 |
The system has started rebuilding the user disk quota information ondevice %1 with label \"%2\". |
| 0x40040027 | 系统已成功地重建带有标签“%2”的设备 %1 上的用户 磁盘限额信息。 |
The system has successfully rebuilt the user disk quota information ondevice %1 with label \"%2\". |
| 0x50000002 | 错误 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x80040028 | 系统在重建标签为“%2”的设备 %1 上的用户 磁盘限额信息时出错。 |
The system has encounted an error rebuilding the user disk quotainformation on device %1 with label \"%2\". |
| 0x80040032 | {延迟写入失败}Windows 无法保存文件 %2 的所有数据。数据已丢失。此错误可能是由计算机硬件或网络连接问题所致。请尝试将此文件保存到其他位置。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %2. 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. |
| 0x80040086 | 卷 %2 上的事务资源管理器在恢复期间遇到错误。该资源管理器将继续恢复。 |
The transaction resource manager on volume %2 encountered an error during recovery. The resource manager will continue recovery. |
| 0x80040088 | 卷 %2 上默认的事务资源管理器在启动期间遇到错误并且其元数据被重置。该数据含有错误代码。 |
The default transaction resource manager on volume %2 encountered an error while starting and its metadata was reset. The data contains the error code. |
| 0x8004008B | {延迟写入失败}Windows 无法保存文件 %2 的所有数据；数据已丢失。此错误可能是由网络连接问题所致。请尝试将此文件保存到其他位置。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %2; the data has been lost.This error may be caused by network connectivity issues. Please try to save this file elsewhere. |
| 0x8004008C | {延迟写入失败}Windows 无法保存文件 %2 的所有数据；数据已丢失。此错误由文件所在的服务器返回。请尝试将此文件保存到其他位置。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %2; the data has been lost.This error was returned by the server on which the file exists. Please try to save this file elsewhere. |
| 0x8004008D | {延迟写入失败}Windows 无法保存文件 %2 的所有数据；数据已丢失。如果设备已被移除或介质为写保护状态，则可能导致此错误。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %2; the data has been lost.This error may be caused if the device has been removed or the media is write-protected. |
| 0x90000001 | System |
System |
| 0xB1000001 | RundownStart |
RundownStart |
| 0xB1000002 | RundownComplete |
RundownComplete |
| 0xB1000003 | RundownVolumeInformation VolumeId: %1, DeviceName: %3 |
RundownVolumeInformation VolumeId: %1, DeviceName: %3 |
| 0xB1000004 | The NTFS volume has been successfully mounted.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n Device Name: %3%n |
The NTFS volume has been successfully mounted.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n Device Name: %3%n |
| 0xB1000064 | NTFS 全局损坏操作状态现在为 %1。 |
NTFS global corruption action state is now %1. |
| 0xB100008B | 在卷 %1 (%2) 上保留安全信息的文件系统结构增长得过大，已被分段。该结构已达到其最大分段限制的 %3%%。如果该结构继续增长并达到此限制，可能无法在此卷上创建新文件。强烈建议将卷脱机进行预防性维护。 |
The file system structure that maintains security information on volume %1 (%2) has grown excessively large and fragmented. The structure has reached %3%% of its maximum fragmentation limit. If the structure continues to grow and reaches this limit, it may not be possible to create new files on this volume. It is strongly recommended that the volume be taken offline for preventative maintenance. |
| 0xB100008D | An operation failed because the disk was full.%n%n Process: %5%n Free space in bytes: %7%n Page file size in bytes: 0%n Volume guid: %1%n Volume name: %3%n Is boot volume: %6%n%nYour disk '%3' is full. Use disk cleanup to free up disk space by deleting unnecessary files. If this is a thinly provisioned volume the physical storage backing this volume may have been exhausted.%n |
An operation failed because the disk was full.%n%n Process: %5%n Free space in bytes: %7%n Page file size in bytes: 0%n Volume guid: %1%n Volume name: %3%n Is boot volume: %6%n%nYour disk '%3' is full. Use disk cleanup to free up disk space by deleting unnecessary files. If this is a thinly provisioned volume the physical storage backing this volume may have been exhausted.%n |
| 0xB100008E | Summary of disk space usage, since last event:%n%n Lowest free space in bytes: %4%n Highest free space in bytes: %5%n Page file size in bytes: 0%n Volume guid: %1%n Volume name: %3%n Is boot volume: %6%n |
Summary of disk space usage, since last event:%n%n Lowest free space in bytes: %4%n Highest free space in bytes: %5%n Page file size in bytes: 0%n Volume guid: %1%n Volume name: %3%n Is boot volume: %6%n |
| 0xB10000C9 | NTFS 日志文件已满 卷 ID: %1，原因: %2 |
NtfsLogFileFull VolumeId: %1, Reason: %2 |
| 0xB10000CA | 定期检查点开始 卷 ID: %1，原因: %2，用法: %3% |
PeriodicCheckpointStart VolumeId: %1, Reason: %2, Usage: %3% |
| 0xB10000CB | 定期检查点完成 卷 ID: %1，脏元数据页: %2 |
PeriodicCheckpointComplete VolumeId: %1, DirtyMetaDataPages: %2 |
| 0xB10000CC | 清理检查点开始 卷 ID: %1，原因: %2，用法: %3% |
CleanCheckpointStart VolumeId: %1, Reason: %2, Usage: %3% |
| 0xB10000CD | 清理检查点完成 卷 ID: %1，脏元数据页: %2 |
CleanCheckpointComplete VolumeId: %1, DirtyMetaDataPages: %2 |
| 0xB10000CE | MftRecordRead VolumeId: %1, BaseFileId: %2, FileId: %3, CacheHit: %4 |
MftRecordRead VolumeId: %1, BaseFileId: %2, FileId: %3, CacheHit: %4 |
| 0xB10000D0 | MftRecordRead VolumeId: %1, BaseFileId: %2, FileId: %3 |
MftRecordRead VolumeId: %1, BaseFileId: %2, FileId: %3 |
| 0xB10000E6 | 工作项已排队，工作项: %1，原因: %2 |
WorkItem queued, WorkItem: %1, Reason: %2 |
| 0xB10000E7 | 工作项队列失败，工作项: %1，原因: %2，错误: %3 |
WorkItem queue failed, WorkItem: %1, Reason: %2, Error: %3 |
| 0xB10000E8 | 工作项已开始，工作项: %1，原因: %2 |
WorkItem started, WorkItem: %1, Reason: %2 |
| 0xB10000E9 | 工作项已完成，工作项: %1，原因: %2 |
WorkItem completed, WorkItem: %1, Reason: %2 |
| 0xB10000F0 | File metadata optimization started.%n%n Volume guid: %1%n Volume name: %3%n File reference: %4%n |
File metadata optimization started.%n%n Volume guid: %1%n Volume name: %3%n File reference: %4%n |
| 0xB10000F1 | File metadata optimization completed.%n%n Volume guid: %1%n Volume name: %3%n File reference: %4%n |
File metadata optimization completed.%n%n Volume guid: %1%n Volume name: %3%n File reference: %4%n |
| 0xB100012C | NTFS volume dismount has started.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n |
NTFS volume dismount has started.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n |
| 0xB100012D | NTFS 已发送卷卸除事件通知，目前正在等待完成通知。 |
NTFS has sent volume dismount event notification and is waiting for the notifications to complete. |
| 0xB100012E | NTFS 卷上的卷卸除事件通知已完成。 |
The volume dismount event notification on the NTFS volume has completed. |
| 0xB100012F | The NTFS volume has successfully dismounted.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n |
The NTFS volume has successfully dismounted.%n%n Volume GUID: %4%n Volume Name: %6%n Volume Label: %8%n |
| 0xB1000130 | The NTFS volume dismount failed.%n%n Error:%1%n |
The NTFS volume dismount failed.%n%n Error:%1%n |
| 0xB1000131 | NTFS failed to mount the volume.%n%n Error: %1%n Volume GUID: %2%n Volume Name: %4%n%nGuidance:%nThe volume is recognized by NTFS but it is corrupted that NTFS could not mount it. Run CHKDSK /F to fix any errors on this volume, and then try accessing it. |
NTFS failed to mount the volume.%n%n Error: %1%n Volume GUID: %2%n Volume Name: %4%n%nGuidance:%nThe volume is recognized by NTFS but it is corrupted that NTFS could not mount it. Run CHKDSK /F to fix any errors on this volume, and then try accessing it. |
| 0xB1000191 | Efs offloading initiated.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
Efs offloading initiated.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
| 0xB1000192 | Efs offloading read regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
Efs offloading read regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
| 0xB1000193 | Efs offloading write regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
Efs offloading write regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
| 0xB1000194 | Efs legacy initiated.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
Efs legacy initiated.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
| 0xB1000195 | Efs legacy read regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
Efs legacy read regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
| 0xB1000196 | Efs legacy write regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
Efs legacy write regular file.%n%n Volume serial: %1%n File reference: %2%n File name: %4%n |
| 0xB1010092 | IO latency summary:%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n%n Interval duration: %6 us%n%n Non-cached reads:%n IO count: %7%n Total bytes: %8%n Avg latency: %9 ns%n%n Non-cached writes: %n IO count: %10%n Total bytes: %11%n Avg latency: %12 ns%n%n File flushes: %n IO count: %13%n Avg latency: %14 ns%n%n Volume flushes: %n IO count: %15%n Avg latency: %16 ns%n%n File level trims: %n IO count: %17%n Total bytes: %18%n Extents count: %19%n Avg latency: %20 ns%n%n Volume trims: %n IO count: %21%n Total bytes: %22%n Extents count: %23%n Avg latency: %24 ns%n%nFor more details see the details tab.%n |
IO latency summary:%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n%n Interval duration: %6 us%n%n Non-cached reads:%n IO count: %7%n Total bytes: %8%n Avg latency: %9 ns%n%n Non-cached writes: %n IO count: %10%n Total bytes: %11%n Avg latency: %12 ns%n%n File flushes: %n IO count: %13%n Avg latency: %14 ns%n%n Volume flushes: %n IO count: %15%n Avg latency: %16 ns%n%n File level trims: %n IO count: %17%n Total bytes: %18%n Extents count: %19%n Avg latency: %20 ns%n%n Volume trims: %n IO count: %21%n Total bytes: %22%n Extents count: %23%n Avg latency: %24 ns%n%nFor more details see the details tab.%n |
| 0xB1010094 | A %9 failed with %14.%nThis may indicate a failing disk.%n%n Process Id: %5%n Process name: %6%n File name: %8%n IO Size: %10 bytes%n File offset: %11%n %13 cluster(s) starting at cluster %12%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n |
A %9 failed with %14.%nThis may indicate a failing disk.%n%n Process Id: %5%n Process name: %6%n File name: %8%n IO Size: %10 bytes%n File offset: %11%n %13 cluster(s) starting at cluster %12%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n |
| 0xB1010095 | In the past %5 seconds we had IO failures.%nThis may indicate a failing disk.%n%n High latency IO count: %6%n Failed writes: %7%n Failed reads: %8%n Bad clusters relocated: %9%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n |
In the past %5 seconds we had IO failures.%nThis may indicate a failing disk.%n%n High latency IO count: %6%n Failed writes: %7%n Failed reads: %8%n Bad clusters relocated: %9%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n |
| 0xB1020091 | IO latency summary common data for volume:%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n%n Max Acceptable IO Latency: %5 ms%n Read/Write latency buckets (ns): [%6, %7, %8, %9, %10, %11, %12]%n Trim latency buckets (ns): [%13, %14, %15, %16, %17, %18, %19]%n Flush latency buckets (ns): [%20, %21, %22, %23, %24, %25, %26]%n |
IO latency summary common data for volume:%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n%n Max Acceptable IO Latency: %5 ms%n Read/Write latency buckets (ns): [%6, %7, %8, %9, %10, %11, %12]%n Trim latency buckets (ns): [%13, %14, %15, %16, %17, %18, %19]%n Flush latency buckets (ns): [%20, %21, %22, %23, %24, %25, %26]%n |
| 0xB1020093 | An IO took more than %5 ms to complete:%n%n Process Id: %6%n Process name: %7%n File name: %9%n File offset: %12%n IO Type: %10%n IO Size: %11 bytes%n %15 cluster(s) starting at cluster %14%n Latency: %13 ms%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n |
An IO took more than %5 ms to complete:%n%n Process Id: %6%n Process name: %7%n File name: %9%n File offset: %12%n IO Type: %10%n IO Size: %11 bytes%n %15 cluster(s) starting at cluster %14%n Latency: %13 ms%n%n Volume Id: %1%n Volume name: %3%n Is boot volume: %4%n |
| 0xC0040029 | 磁盘上的文件系统结构已损坏，不能使用。请在标签为“%2”的 %1 设备上运行 chkdsk 实用程序。 |
The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the device %1 with label \"%2\". |
| 0xC004002A | 用户磁盘配额信息不可用。若要确保准确性，将重建标签为“%2”的设备 %1 上的文件系统配额信息。 |
The user disk quota information is unusable.To ensure accuracy, the file system quota information on the device %1 with label \"%2\" willbe rebuilt. |
| 0xC0040037 | 磁盘上的文件系统结构已损坏，不能使用。请在卷 %2 上运行 chkdsk 实用程序。 |
The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the volume %2. |
| 0xC0040087 | 由于出现不可重试的错误，卷 %2 上的事务资源管理器无法在其日志中创建可用空间。该数据含有错误代码。 |
The transaction resource manager on volume %2 was unable to create free space in its log due to a non-retryable error. The data contains the error code. |
| 0xC0040089 | 卷 %2 上默认的事务资源管理器遇到不可重试的错误并且无法启动。该数据含有错误代码。 |
The default transaction resource manager on volume %2 encountered a non-retryable error and could not start. The data contains the error code. |
| 0xC004008A | %2%3 的事务资源管理器遇到致命错误并且被关闭。该数据含有错误代码。 |
The transaction resource manager at %2%3 encountered a fatal error and was shut down. The data contains the error code. |
| 0xD1000001 | 运行状况良好。无需执行任何操作。 |
is healthy. No action is needed. |
| 0xD1000002 | 需要进行在线扫描。在计划的下一次维护任务期间，将自动执行在线扫描。或者，你也可以在本机通过命令行运行 \"CHKDSK /SCAN\"，或者在本机或远程通过 PowerShell 运行 \"REPAIR-VOLUME -SCAN\"。 |
requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run \"CHKDSK /SCAN\" locally via the command line, or run \"REPAIR-VOLUME -SCAN\" locally or remotely via PowerShell. |
| 0xD1000003 | 需要脱机一段时间以执行错误修复。请在本机通过命令行运行 \"CHKDSK /SPOTFIX\"，或者在本机或远程通过 PowerShell 运行 \"REPAIR-VOLUME \"。 |
needs to be taken offline for a short time to perform a Spot Fix. Please run \"CHKDSK /SPOTFIX\" locally via the command line, or run \"REPAIR-VOLUME \" locally or remotely via PowerShell. |
| 0xD1000004 | 需要脱机一段时间以执行完整的 Chkdsk。请在本机通过命令行运行 \"CHKDSK /F\"，或者在本机或远程通过 PowerShell 运行 \"REPAIR-VOLUME \"。 |
needs to be taken offline to perform a Full Chkdsk. Please run \"CHKDSK /F\" locally via the command line, or run \"REPAIR-VOLUME \" locally or remotely via PowerShell. |
| 0xD1000005 | LogSpace |
LogSpace |
| 0xD1000006 | DirtyPages |
DirtyPages |
| 0xD1000007 | OpenAttributes |
OpenAttributes |
| 0xD1000008 | TransactionDrain |
TransactionDrain |
| 0xD1000009 | FastIOCallback |
FastIOCallback |
| 0xD100000A | DeallocatedClusters |
DeallocatedClusters |
| 0xD100000B | DeallocatedClustersMem |
DeallocatedClustersMem |
| 0xD100000C | RecordStackCheck |
RecordStackCheck |
| 0xD100000D | Dismount |
Dismount |
| 0xD100000E | Compression |
Compression |
| 0xD100000F | Snapshot |
Snapshot |
| 0xD1000010 | Mount |
Mount |
| 0xD1000011 | Shutdown |
Shutdown |
| 0xD1000012 | RecursiveCompression |
RecursiveCompression |
| 0xD1000013 | Testing |
Testing |
| 0xD1000014 | PostRequest |
PostRequest |
| 0xD1000015 | Checkpoint |
Checkpoint |
| 0xD1000016 | DelayClose |
DelayClose |
| 0xD1000017 | MarkUnusedContextCompletion |
MarkUnusedContextCompletion |
| 0xD1000018 | HotFix |
HotFix |
| 0xD1000019 | DiskFlushCompletion |
DiskFlushCompletion |
| 0xD100001A | McbCleanup |
McbCleanup |
| 0xD100001B | UsnTimeOut |
UsnTimeOut |
| 0xD100001C | Repair |
Repair |
| 0xD100001D | TxfRmDelayedWorkItem |
TxfRmDelayedWorkItem |
| 0xD100001E | TxfRmCriticalWorkItem |
TxfRmCriticalWorkItem |
| 0xD100001F | TxfRmRestartWorkItem |
TxfRmRestartWorkItem |
| 0xD1000020 | TxfThawRmsWorker |
TxfThawRmsWorker |
| 0xD1000021 | ScavengeDeleteUsn |
ScavengeDeleteUsn |
| 0xD1000022 | ScavengeRepairObjectId |
ScavengeRepairObjectId |
| 0xD1000023 | ScavengeRepairQuotaIndex |
ScavengeRepairQuotaIndex |
| 0xD1000024 | ScavengeMarkUserLimit |
ScavengeMarkUserLimit |
| 0xD1000025 | ScavengeResolveVolumeAndLogEvent |
ScavengeResolveVolumeAndLogEvent |
| 0xD1000026 | 写入: 非分页，非缓存，异步 |
Write: NonPaging, NonCached, Async |
| 0xD1000027 | 写入: 非分页，非缓存，同步 |
Write: NonPaging, NonCached, Sync |
| 0xD1000028 | 写入: 非分页，非缓存，异步，直写 |
Write: NonPaging, NonCached, Async, Writethrough |
| 0xD1000029 | 写入: 非分页，非缓存，同步，直写 |
Write: NonPaging, NonCached, Sync, Writethrough |
| 0xD100002A | 写入: 非分页，缓存，异步 |
Write: NonPaging, Cached, Async |
| 0xD100002B | 写入: 非分页，缓存，同步 |
Write: NonPaging, Cached, Sync |
| 0xD100002C | 写入: 非分页，缓存，异步，直写 |
Write: NonPaging, Cached, Async, Writethrough |
| 0xD100002D | 写入: 非分页，缓存，同步，直写 |
Write: NonPaging, Cached, Sync, Writethrough |
| 0xD100002E | 写入: 分页，非缓存，异步 |
Write: Paging, NonCached, Async |
| 0xD100002F | 写入: 分页，非缓存，同步 |
Write: Paging, NonCached, Sync |
| 0xD1000030 | 写入: 分页，非缓存，异步，直写 |
Write: Paging, NonCached, Async, Writethrough |
| 0xD1000031 | 写入: 分页，非缓存，同步，直写 |
Write: Paging, NonCached, Sync, Writethrough |
| 0xD1000032 | 读取: 非分页，非缓存，异步 |
Read: NonPaging, NonCached, Async |
| 0xD1000033 | 读取: 非分页，非缓存，同步 |
Read: NonPaging, NonCached, Sync |
| 0xD1000034 | 读取: 非分页，缓存，异步 |
Read: NonPaging, Cached, Async |
| 0xD1000035 | 读取: 非分页，缓存，同步 |
Read: NonPaging, Cached, Sync |
| 0xD1000036 | 读取: 分页，非缓存，异步 |
Read: Paging, NonCached, Async |
| 0xD1000037 | 读取: 分页，非缓存，同步 |
Read: Paging, NonCached, Sync |
| 0xD1000038 | 读取 |
read |
| 0xD1000039 | 写入 |
write |