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%nConnect: %14%nBreakCycle: %15%nFRSAllocate: %16%nOthers: %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 |
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 | 安全性識別碼無效 |
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 | 發現某個檔案包含安全性檔案中未指定的安全性識別碼。無效的安全性識別碼為 0x%1!lx!。檔案參照號碼為 0x%2!0I64x!。檔案名稱為 \"%3!wZ!\"。磁碟區上可能還有其他檔案也參照這個無效的安全性識別碼。 |
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 | 開始修復 %4:%5:%6:%7% 的 %2/%3/%1 |
Start repair on %2/%3/%1 at %4:%5:%6:%7% |
0x000061B1 | 結束修復 %4:%5:%6:%7 的 %2/%3/%1 |
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 | 檔案記錄區段 0x%1 中的安全性識別碼 0x%2 無效。它將被取代為僅限系統管理員使用的安全性識別碼。 |
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 個叢集中,自 VCN 0x%5 開始且 LCN 為 0x%6 的叢集標示為已被檔案 0x%1 使用。 |
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 個叢集中,自 VCN 0x%5 開始且 LCN 為 0x%6 的叢集標示為未被檔案 0x%1 使用。 |
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 | 正在將識別碼為 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 | 磁碟區有 0x%1 個檔案記錄區段超過 32 位元。 |
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 Information 不正確。 實際 磁碟上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 Information 值長度 0x%1 不正確。 |
The EA Information value length, 0x%1, in file 0x%2 is incorrect. |
0x00006989 | 檔案 0x%1 中的 EA 總封包長度 0x%2 太大。 |
The EA total packed length, 0x%2, is too large in file 0x%1. |
0x0000698A | 開機磁區的第二個 MFT 起始 LCN 不正確。預期值為 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 找到子樹系 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%2 起的 0x%3 位元組。 |
Read failure with status 0x%1 at offset 0x%2 for 0x%3 bytes. |
0x000069A5 | 讀取不正確,自位移 0x%1 起的 0x%3 位元組,但已讀取 0x%2 位元組。 |
Incorrect read at offset 0x%1 for 0x%3 bytes but got 0x%2 bytes. |
0x000069A6 | 寫入失敗,狀態 0x%1,自位移 0x%2 起的 0x%3 位元組。 |
Write failure with status 0x%1 at offset 0x%2 for 0x%3 bytes. |
0x000069A7 | 寫入不正確,自位移 0x%1 起的 0x%3 位元組,但已寫入 0x%2 位元組。 |
Incorrect write at offset 0x%1 for 0x%3 bytes but wrote 0x%2 bytes. |
0x000069A8 | 已寫出的資料,與讀回自位移 0x%1 起的 0x%2 位元組的資料不同。 |
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 | 無法查詢 VCN 0x%2 的 LCN 中是否有類型 0x%1 的屬性。 |
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%2 起交互連結,且大約佔 0x%3 個叢集。 |
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 | 索引 %1 不是檔案 0x%2 中的已知配額索引。 |
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 中的物件識別碼索引項目指向檔案 0x%2,但該檔案中沒有物件識別碼。 |
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 中的物件識別碼索引項目指向檔案 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 中,索引項目的物件識別碼不正確。該項目指向檔案 0x%2。 |
The object id in index entry in file 0x%1 is incorrect.The entry points to file 0x%2. |
0x000069DE | 檔案 0x%1 中,物件識別碼索引項目內的父系 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 中的物件識別碼已存在於檔案 0x%1 中的物件識別碼索引。 |
The object id in file 0x%2 already existed in the objectid index in file 0x%1. |
0x000069E0 | 檔案 0x%2 中的物件識別碼未出現於檔案 0x%1 中的物件識別碼索引。 |
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%3 及例項標記 0x%4 的屬性而言,屬性記錄長度 0x%1 太短。最小值為 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%2 及例項標記 0x%3 的屬性而言,屬性表單代碼 0x%1 不正確。 |
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%3 及例項標記 0x%4 的屬性所配置的長度 0x%1 不是 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%4 的類型0x%3的屬性而言,檔案名稱數值長度 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%2 中的檔案記錄區段大小 0x%1 無效。 |
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%3 及例項標記 0x%4 之屬性的屬性記錄位移 0x%1 太大。最大值為 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%3及例項標記 0x%4 之屬性的記錄長度 0x%1 太大。最大值為 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%3 中,類型 0x%1 及例項標記 0x%2 有兩個相同的屬性。 |
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%1交互連結,可能佔 0x%2 個叢集。 |
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 日誌項目的日誌值 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%3 所遭遇的最大值 0x%2 再加上 8。 |
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%1,持續 0x%2 位元組) 含有不為零的值。 |
The remaining of a security data stream page starting at offset 0x%1for 0x%2 bytes contains non-zero. |
0x00006A4D | 安全性資料流項目 (所在位移為 0x%1,長度為 0x%2) 跨越頁面界限。 |
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 的安全性描述元項目的安全性識別碼 0x%2 重複。 |
The security Id 0x%2 of security descriptor entry at offset 0x%1is a duplicate. |
0x00006A53 | 安全性描述元項目 (ID 為 0x%4,所在位移為 0x%1)的雜湊值 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 | 存放在安全性描述元項目 (ID 為 0x%4,所在位移為 0x%1)的位移 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 的安全性識別碼 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 | 開機檔的資料屬性遺失叢集 0。 |
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%1 起持續 0x%2 個磁區的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 Data 值長度 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 中的多個物件識別碼索引項目指向相同的檔案 0x%2。 |
Multiple object id index entries in file 0x%1point to the same file 0x%2. |
0x00006A80 | 檔案 0x%1 中的物件識別碼索引項目指向一個無法讀取的檔案 0x%2。 |
The object id index entry in file 0x%1 points to file 0x%2which is unreadable. |
0x00006A81 | 檔案 0x%1 中的物件識別碼索引項目指向一個尚未使用的檔案 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 | RAM 根目錄的 $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 | 精簡佈建的磁碟區 %1 (%2)%n未在叢集 %3 與 %4 之間對應。%n現在已修正此問題。 |
Thinly provisioned volume %1 (%2)%nwere not being mapped between clusters %3 and %4.%nIt is now fixed. |
0x010000D3 | 精簡佈建的磁碟區 %1 (%2)%n未在叢集 %3 與 %4 之間對應。%n修復失敗。%n可用 Slab 數目可能不足。 |
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 | 系統已經開始重建使用者磁碟配額資訊於裝置 %1 標籤 \"%2\"。 |
The system has started rebuilding the user disk quota information ondevice %1 with label \"%2\". |
0x40040027 | 系統已順利重建使用者磁碟配額資訊於裝置 %1 標籤 \"%2\"。 |
The system has successfully rebuilt the user disk quota information ondevice %1 with label \"%2\". |
0x50000002 | 錯誤 |
Error |
0x50000003 | 警告 |
Warning |
0x80040028 | 系統在重建使用者磁碟配額資訊於裝置 %1 標籤 \"%2\" 時發生錯誤。 |
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 | NtfsLogFileFull VolumeId: %1,原因: %2 |
NtfsLogFileFull VolumeId: %1, Reason: %2 |
0xB10000CA | PeriodicCheckpointStart VolumeId: %1,原因: %2,使用狀況: %3% |
PeriodicCheckpointStart VolumeId: %1, Reason: %2, Usage: %3% |
0xB10000CB | PeriodicCheckpointComplete VolumeId: %1,DirtyMetaDataPages: %2 |
PeriodicCheckpointComplete VolumeId: %1, DirtyMetaDataPages: %2 |
0xB10000CC | CleanCheckpointStart VolumeId: %1,原因: %2,使用狀況: %3% |
CleanCheckpointStart VolumeId: %1, Reason: %2, Usage: %3% |
0xB10000CD | CleanCheckpointComplete VolumeId: %1,DirtyMetaDataPages: %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 | WorkItem 已佇列,WorkItem: %1,原因: %2 |
WorkItem queued, WorkItem: %1, Reason: %2 |
0xB10000E7 | WorkItem 佇列失敗,WorkItem: %1,原因: %2,錯誤: %3 |
WorkItem queue failed, WorkItem: %1, Reason: %2, Error: %3 |
0xB10000E8 | WorkItem 已啟動,WorkItem: %1,原因: %2 |
WorkItem started, WorkItem: %1, Reason: %2 |
0xB10000E9 | WorkItem 已完成,WorkItem: %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 | 磁碟上的檔案系統結構已損毀,無法使用。請於裝置 %1 標籤 \"%2\" 上執行 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 | 使用者磁碟配額資訊無法使用。將對裝置 %1 (標籤 \"%2\") 重建檔案系統配額資訊,以確保其正確。 |
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 | 需要離線以執行「完整Full 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 | 寫入: NonPaging、NonCached、Async |
Write: NonPaging, NonCached, Async |
0xD1000027 | 寫入: NonPaging、NonCached、Sync |
Write: NonPaging, NonCached, Sync |
0xD1000028 | 寫入: NonPaging、NonCached、Async、Writethrough |
Write: NonPaging, NonCached, Async, Writethrough |
0xD1000029 | 寫入: NonPaging、NonCached、Sync、Writethrough |
Write: NonPaging, NonCached, Sync, Writethrough |
0xD100002A | 寫入: NonPaging、Cached、Async |
Write: NonPaging, Cached, Async |
0xD100002B | 寫入: NonPaging、Cached、Sync |
Write: NonPaging, Cached, Sync |
0xD100002C | 寫入: NonPaging、Cached、Async、Writethrough |
Write: NonPaging, Cached, Async, Writethrough |
0xD100002D | 寫入: NonPaging、Cached、Sync、Writethrough |
Write: NonPaging, Cached, Sync, Writethrough |
0xD100002E | 寫入: Paging、NonCached、Async |
Write: Paging, NonCached, Async |
0xD100002F | 寫入: Paging、NonCached、Sync |
Write: Paging, NonCached, Sync |
0xD1000030 | 寫入: Paging、NonCached、Async、Writethrough |
Write: Paging, NonCached, Async, Writethrough |
0xD1000031 | 寫入: Paging、NonCached、Sync、Writethrough |
Write: Paging, NonCached, Sync, Writethrough |
0xD1000032 | 讀取: NonPaging、NonCached、Async |
Read: NonPaging, NonCached, Async |
0xD1000033 | 讀取: NonPaging、NonCached、Sync |
Read: NonPaging, NonCached, Sync |
0xD1000034 | 讀取: NonPaging、Cached、Async |
Read: NonPaging, Cached, Async |
0xD1000035 | 讀取: NonPaging、Cached、Sync |
Read: NonPaging, Cached, Sync |
0xD1000036 | 讀取: Paging、NonCached、Async |
Read: Paging, NonCached, Async |
0xD1000037 | 讀取: Paging、NonCached、Sync |
Read: Paging, NonCached, Sync |
0xD1000038 | 讀取 |
read |
0xD1000039 | 寫入 |
write |