ntfs.sys.mui NT File System Driver eaeef57f1f5e26c042e11d3b4f9102dd

File name:	ntfs.sys.mui
Size:	99328 byte
MD5:	eaeef57f1f5e26c042e11d3b4f9102dd
SHA1:	8db5ba2579bdc5480a492b64af3ac37a58c67124
SHA256:	fb46886b68bffbf0ca015bc63e2eaaf4d7015ab5e63e28020056e1ef7e481b29
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id	English (U.S.)	English
0x37	A corruption was discovered in the file system structure on volume %1.%n%n%8	A corruption was discovered in the file system structure on volume %1.%n%n%8
0x82	The file system structure on volume %2 has now been repaired.	The file system structure on volume %2 has now been repaired.
0x83	The file system structure on volume %2 cannot be corrected.%nPlease run the chkdsk utility on the volume %2.	The file system structure on volume %2 cannot be corrected.%nPlease run the chkdsk utility on the volume %2.
0x84	Too many repair events have occurred in a short period of time.%nTemporarily suspending posting of further repair events.	Too many repair events have occurred in a short period of time.%nTemporarily suspending posting of further repair events.
0x85	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	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	Force Full Chkdsk	Force Full Chkdsk
0x1002	Force Proactive Scan	Force Proactive Scan
0x1003	Bad FRS	Bad FRS
0x1004	Orphan Child FRS	Orphan Child FRS
0x1005	Bad Clusters	Bad Clusters
0x1006	Bad Free Clusters	Bad Free Clusters
0x1007	Cross-Link	Cross-Link
0x1008	SD Entry	SD Entry
0x1009	Invalid Security Id	Invalid Security Id
0x100A	Index Attribute	Index Attribute
0x100B	Index Subtree	Index Subtree
0x100C	Index Offset	Index Offset
0x100D	Index Entry	Index Entry
0x100E	Index Order	Index Order
0x100F	Connect	Connect
0x1010	Break Cycle	Break Cycle
0x1011	FRS Allocate	FRS Allocate
0x1012	Index Sort	Index Sort
0x1013	Index Cycle	Index Cycle
0x1100	File System Driver	File System Driver
0x1101	Proactive Scanner	Proactive Scanner
0x1102	User Application	User Application
0x1200	Read Only Volume	Read Only Volume
0x1201	Self Healed	Self Healed
0x1202	Spot Corruption Handling Disabled	Spot Corruption Handling Disabled
0x1203	Spot Verifier Bypassed On Critical	Spot Verifier Bypassed On Critical
0x1204	Spot Verifier Bypassed On Error	Spot Verifier Bypassed On Error
0x1205	Sent To Spot Fixer	Sent To Spot Fixer
0x1206	Spot Fixer Bypassed On Critical	Spot Fixer Bypassed On Critical
0x1207	Spot Fixer Bypassed On Error	Spot Fixer Bypassed On Error
0x1208	Duplicate	Duplicate
0x1209	Malformed	Malformed
0x120A	Unsupported	Unsupported
0x120B	Verified	Verified
0x120C	False Positive	False Positive
0x120D	Superseded	Superseded
0x120E	Purged	Purged
0x120F	Pseudo Verb	Pseudo Verb
0x1210	Unexpected Corruption	Unexpected Corruption
0x1211	Volume Not Available	Volume Not Available
0x1300	Maintenance	Maintenance
0x1301	Normal	Normal
0x1302	Critical	Critical
0x1F00
0x2010	The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.	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.	The exact nature of the corruption is unknown. The file system structures need to be scanned online.
0x2030	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!\".	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	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!.	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	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!.	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	A bad cluster was discovered outside of any existing file on the volume. The bad cluster is located at 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	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!.	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	A corruption was found in the security descriptor stream. The corrupted entry is at offset 0x%1!I64x!.	A corruption was found in the security descriptor stream. The corrupted entry is at offset 0x%1!I64x!.
0x2090	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.	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	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!\".	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	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.	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	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!\".	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	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.	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	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.	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	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!.	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	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!.	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	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!.	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	Clearing the in use bit for file record 0x%1.	Clearing the in use bit for file record 0x%1.
0x000061A9	Repairing the sequence number for file record 0x%1.	Repairing the sequence number for file record 0x%1.
0x000061AA	Repairing the first free byte for file record 0x%1.	Repairing the first free byte for file record 0x%1.
0x000061AB	Repairing the segment number for file record 0x%1.	Repairing the segment number for file record 0x%1.
0x000061AC	Repairing the file attributes for file record 0x%1.	Repairing the file attributes for file record 0x%1.
0x000061AD	Deleting attribute of type code 0x%1 and instance tag 0x%2for file record 0x%3.	Deleting attribute of type code 0x%1 and instance tag 0x%2for file record 0x%3.
0x000061AE	Repairing the flags for file record 0x%1.	Repairing the flags for file record 0x%1.
0x000061AF	Adding attribute of type code 0x%1 for file record 0x%2.	Adding attribute of type code 0x%1 for file record 0x%2.
0x000061B0	Start repair on %2/%3/%1 at %4:%5:%6:%7%	Start repair on %2/%3/%1 at %4:%5:%6:%7%
0x000061B1	End repair on %2/%3/%1 at %4:%5:%6:%7	End repair on %2/%3/%1 at %4:%5:%6:%7
0x000061B2	Marked file record %1 as in use in MFT bitmap.	Marked file record %1 as in use in MFT bitmap.
0x000061B3	Security Id 0x%2 is invalid in file record segment 0x%1.It will be replaced with an administrator only Security Id.	Security Id 0x%2 is invalid in file record segment 0x%1.It will be replaced with an administrator only Security Id.
0x000061B4	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.	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	Processing repair verb BadFrs: 0x%1Flags: 0x%2, 0x%3	Processing repair verb BadFrs: 0x%1Flags: 0x%2, 0x%3
0x000061B6	Processing repair verb InvalidSid: 0x%1, 0x%2, 0x%3,,, 0x%4Flags: 0x%5, 0x%6	Processing repair verb InvalidSid: 0x%1, 0x%2, 0x%3,,, 0x%4Flags: 0x%5, 0x%6
0x000061B7	Processing repair verb FrsAllocate: 0x%1, 0x%2, \"%3\", 0x%4, 0x%5, 0x%6Flags: 0x%7, 0x%8	Processing repair verb FrsAllocate: 0x%1, 0x%2, \"%3\", 0x%4, 0x%5, 0x%6Flags: 0x%7, 0x%8
0x000061B8	Processing repair verb Connect: 0x%1, \"%2\", 0x%3, 0x%4, 0x%5,,, 0x%6Flags: 0x%7, 0x%8	Processing repair verb Connect: 0x%1, \"%2\", 0x%3, 0x%4, 0x%5,,, 0x%6Flags: 0x%7, 0x%8
0x000061B9	Processing repair verb IndexEntry: 0x%1, \"%2\", \"%3\"Flags: 0x%4, 0x%5	Processing repair verb IndexEntry: 0x%1, \"%2\", \"%3\"Flags: 0x%4, 0x%5
0x000061BA	Processing repair verb OrphanChildFrs: 0x%1, 0x%2,,, 0x%3Flags: 0x%4, 0x%5	Processing repair verb OrphanChildFrs: 0x%1, 0x%2,,, 0x%3Flags: 0x%4, 0x%5
0x000061C6	This repair generated too many messages. %1 messages were skipped.	This repair generated too many messages. %1 messages were skipped.
0x000061C7	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.	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	Deleting corrupt file record segment 0x%1.	Deleting corrupt file record segment 0x%1.
0x000065AA	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.	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	Correcting a minor error in file 0x%1.	Correcting a minor error in file 0x%1.
0x000065CE	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.	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	Deleting index entry %3 in index 0x%2 of file 0x%1.	Deleting index entry %3 in index 0x%2 of file 0x%1.
0x000065E4	Deleting an index entry from index 0x%2 of file 0x%1.	Deleting an index entry from index 0x%2 of file 0x%1.
0x000065F5	Inserting an index entry %3 into index 0x%2 of file 0x%1.	Inserting an index entry %3 into index 0x%2 of file 0x%1.
0x0000660F	Inserting an index entry with Id 0x%3 into index 0x%2 of file 0x%1.	Inserting an index entry with Id 0x%3 into index 0x%2 of file 0x%1.
0x00006784	Change file name flags from 0x%3 to 0x%4 forfile name instance 0x%2 in file 0x%1.	Change file name flags from 0x%3 to 0x%4 forfile name instance 0x%2 in file 0x%1.
0x00006978	Volume has 0x%1 file record segments which is more than 32 bits.	Volume has 0x%1 file record segments which is more than 32 bits.
0x00006979	The file name index present bit is not set for file 0x%1.	The file name index present bit is not set for file 0x%1.
0x0000697A	The view index present bit is not set for file 0x%1.	The view index present bit is not set for file 0x%1.
0x0000697B	The system file bit is not set for file 0x%1.	The system file bit is not set for file 0x%1.
0x0000697C	The %2 index is missing from file 0x%1.	The %2 index is missing from file 0x%1.
0x0000697D	EA Information is incorrect. Actual On DiskPackedEaSize 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	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.	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	The EA INFORMATION is not readable for file 0x%1.	The EA INFORMATION is not readable for file 0x%1.
0x00006980	The EA INFORMATION size, 0x%2, in file 0x%1 is incorrect.The expected size is 0x%3.	The EA INFORMATION size, 0x%2, in file 0x%1 is incorrect.The expected size is 0x%3.
0x00006981	The EA DATA is not readable for file 0x%1.	The EA DATA is not readable for file 0x%1.
0x00006982	The EA DATA size, 0x%2, in file 0x%1 is incorrect.The expected size is 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	Corrupt EA set for file 0x%1. The remaining length, 0x%2,is too small.	Corrupt EA set for file 0x%1. The remaining length, 0x%2,is too small.
0x00006985	Corrupt EA set for file 0x%1. The unpacked total length, 0x%2,is larger than the total data length, 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	Corrupt EA set for file 0x%1. The EA name is of length 0x%2.	Corrupt EA set for file 0x%1. The EA name is of length 0x%2.
0x00006987	Corrupt EA set for file 0x%1. The unpacked length, 0x%2,is not the same as the record length, 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	The EA Information value length, 0x%1, in file 0x%2 is incorrect.	The EA Information value length, 0x%1, in file 0x%2 is incorrect.
0x00006989	The EA total packed length, 0x%2, is too large in file 0x%1.	The EA total packed length, 0x%2, is too large in file 0x%1.
0x0000698A	The second MFT starting LCN in the boot sector is incorrect.The actual value is 0x%2 while the expected value is 0x%1.	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	The reparse point length, 0x%1, has exceeded a maximum of 0x%2.	The reparse point length, 0x%1, has exceeded a maximum of 0x%2.
0x0000698C	The reparse point length, 0x%1, is less than a minimum of 0x%2.	The reparse point length, 0x%1, is less than a minimum of 0x%2.
0x0000698D	Unable to read reparse point data buffer.	Unable to read reparse point data buffer.
0x0000698E	Only 0x%1 bytes returned from a read of 0x%d bytesof the reparse data buffer.	Only 0x%1 bytes returned from a read of 0x%d bytesof the reparse data buffer.
0x0000698F	ReparseDataLength, 0x%1, inconsistence with the attribute length 0x%2.	ReparseDataLength, 0x%1, inconsistence with the attribute length 0x%2.
0x00006990	Reparse Tag, 0x%1, is a reserved tag.	Reparse Tag, 0x%1, is a reserved tag.
0x00006992	File 0x%1 has bad reparse point attribute.	File 0x%1 has bad reparse point attribute.
0x00006993	Both reparse point and EA INFORMATION attributes exist in file 0x%1.	Both reparse point and EA INFORMATION attributes exist in file 0x%1.
0x00006994	The attribute definition table length, 0x%1, is not divisible by 0x%2.	The attribute definition table length, 0x%1, is not divisible by 0x%2.
0x00006995	Unable to find child frs 0x%1 with sequence number 0x%2.	Unable to find child frs 0x%1 with sequence number 0x%2.
0x00006996	Unable to locate attribute of type 0x%1, lowest vcn 0x%2,instance tag 0x%3 in file 0x%4.	Unable to locate attribute of type 0x%1, lowest vcn 0x%2,instance tag 0x%3 in file 0x%4.
0x00006997	The is an attribute list attribute within the attribute list in file 0x%1.	The is an attribute list attribute within the attribute list in file 0x%1.
0x00006998	The lowest vcn, 0x%2, is not zero for attribute of type 0x%1and instance tag 0x%3 in file 0x%4.	The lowest vcn, 0x%2, is not zero for attribute of type 0x%1and instance tag 0x%3 in file 0x%4.
0x00006999	The lowest vcn, 0x%2, is not zero for attribute of type 0x%1in file 0x%3.	The lowest vcn, 0x%2, is not zero for attribute of type 0x%1in file 0x%3.
0x0000699A	The first attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be resident.	The first attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be resident.
0x0000699B	The attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be resident.	The attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be resident.
0x0000699C	The attributes with instance tags 0x%2 and 0x%4 have differenttype codes 0x%1 and 0x%3 respectively in file 0x%5.	The attributes with instance tags 0x%2 and 0x%4 have differenttype codes 0x%1 and 0x%3 respectively in file 0x%5.
0x0000699D	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.	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	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.	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	The attribute of type 0x%1 and instance tag 0x%2 in file 0x%5has allocated length of 0x%3 instead of 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	The attribute of type 0x%1 in file 0x%4 has allocated lengthof 0x%2 instead of 0x%3.	The attribute of type 0x%1 in file 0x%4 has allocated lengthof 0x%2 instead of 0x%3.
0x000069A1	The file attributes flag 0x%1 in file 0x%3 is incorrect.The expected value is 0x%2.	The file attributes flag 0x%1 in file 0x%3 is incorrect.The expected value is 0x%2.
0x000069A2	The sequence number 0x%1 in file 0x%2 is incorrect.	The sequence number 0x%1 in file 0x%2 is incorrect.
0x000069A3	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.	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	Read failure with status 0x%1 at offset 0x%2 for 0x%3 bytes.	Read failure with status 0x%1 at offset 0x%2 for 0x%3 bytes.
0x000069A5	Incorrect read at offset 0x%1 for 0x%3 bytes but got 0x%2 bytes.	Incorrect read at offset 0x%1 for 0x%3 bytes but got 0x%2 bytes.
0x000069A6	Write failure with status 0x%1 at offset 0x%2 for 0x%3 bytes.	Write failure with status 0x%1 at offset 0x%2 for 0x%3 bytes.
0x000069A7	Incorrect write at offset 0x%1 for 0x%3 bytes but wrote 0x%2 bytes.	Incorrect write at offset 0x%1 for 0x%3 bytes but wrote 0x%2 bytes.
0x000069A8	The data written out is different from what is being read backat offset 0x%1 for 0x%2 bytes.	The data written out is different from what is being read backat offset 0x%1 for 0x%2 bytes.
0x000069A9	The file 0x%1 belongs to parent 0x%3 but got 0x%2 as parent.	The file 0x%1 belongs to parent 0x%3 but got 0x%2 as parent.
0x000069AA	The file 0x%1 has file name %2 when it should be %3.	The file 0x%1 has file name %2 when it should be %3.
0x000069AB	The multi-sector header with total size 0x%1, USA offset 0x%2,and USA count 0x%3 is incorrect.	The multi-sector header with total size 0x%1, USA offset 0x%2,and USA count 0x%3 is incorrect.
0x000069AC	The USA check value, 0x%2, at block 0x%1 is incorrect.The expected value is 0x%3.	The USA check value, 0x%2, at block 0x%1 is incorrect.The expected value is 0x%3.
0x000069AD	Unable to query LCN from VCN 0x%2 for attribute of type 0x%1.	Unable to query LCN from VCN 0x%2 for attribute of type 0x%1.
0x000069AE	Attribute record of type 0x%1 and instance tag 0x%2 is cross linkedstarting at 0x%3 for possibly 0x%4 clusters.	Attribute record of type 0x%1 and instance tag 0x%2 is cross linkedstarting at 0x%3 for possibly 0x%4 clusters.
0x000069AF	Attribute record of type 0x%1 is cross linked starting atcluster 0x%2 for possibly 0x%3 clusters.	Attribute record of type 0x%1 is cross linked starting atcluster 0x%2 for possibly 0x%3 clusters.
0x000069B0	The attribute list in file 0x%1 does not containstandard information attribute.	The attribute list in file 0x%1 does not containstandard information attribute.
0x000069B1	The attribute list in file 0x%1 indicates the standard informationattribute is outside the base file record segment.	The attribute list in file 0x%1 indicates the standard informationattribute is outside the base file record segment.
0x000069B2	The index root %2 is missing in file 0x%1.	The index root %2 is missing in file 0x%1.
0x000069B3	The index bitmap %2 is missing in file 0x%1.	The index bitmap %2 is missing in file 0x%1.
0x000069B4	The index bitmap %2 in file 0x%1 is incorrect.	The index bitmap %2 in file 0x%1 is incorrect.
0x000069B5	The index bitmap %2 is present but there is no correspondingindex allocation attribute in file 0x%1.	The index bitmap %2 is present but there is no correspondingindex allocation attribute in file 0x%1.
0x000069B6	The length, 0x%2, of the root index %1 in file 0x%4is too small. The minimum length is 0x%3.	The length, 0x%2, of the root index %1 in file 0x%4is too small. The minimum length is 0x%3.
0x000069B7	The root index %1 in file 0x%3 is incorrect.The expected name is %2.	The root index %1 in file 0x%3 is incorrect.The expected name is %2.
0x000069B8	The collation rule 0x%3 for index root %1 in file 0x%2is incorrect. The expected value is 0x%4.	The collation rule 0x%3 for index root %1 in file 0x%2is incorrect. The expected value is 0x%4.
0x000069B9	Breaking the parent 0x%1 and child 0x%2file relationship. This also makes the child an orphan.	Breaking the parent 0x%1 and child 0x%2file relationship. This also makes the child an orphan.
0x000069BA	The index attribute of type 0x%2 for index root %1in file 0x%4 is incorrect. The expected value is 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	The index %1 is not a known quota index in file 0x%2.	The index %1 is not a known quota index in file 0x%2.
0x000069BC	The index %1 is not a known security index in file 0x%2.	The index %1 is not a known security index in file 0x%2.
0x000069BD	The index attribute of type 0x%2 for index root %1in file 0x%3 is not recognized.	The index attribute of type 0x%2 for index root %1in file 0x%3 is not recognized.
0x000069BE	The index attribute of type 0x%2 for index root %1in file 0x%3 is not indexable.	The index attribute of type 0x%2 for index root %1in file 0x%3 is not indexable.
0x000069BF	The bytes per index buffer, 0x%2, for index root %1 in file0x%4 is incorrect. The expected value is 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	The clusters per index buffer, 0x%2, for index root %1 in file0x%4 is incorrect. The expected value is 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	The index allocation value length, 0x%2, for index %1 in file0x%4 is not in multiple of 0x%3.	The index allocation value length, 0x%2, for index %1 in file0x%4 is not in multiple of 0x%3.
0x000069C2	The index allocation allocated length, 0x%2, for index %1 in file0x%4 is not in multiple of 0x%3.	The index allocation allocated length, 0x%2, for index %1 in file0x%4 is not in multiple of 0x%3.
0x000069C3	The first free byte, 0x%2, and bytes available, 0x%3, forroot index %1 in file 0x%4 are not equal.	The first free byte, 0x%2, and bytes available, 0x%3, forroot index %1 in file 0x%4 are not equal.
0x000069C4	The index entry offset, 0x%3, of index %1 and VCN 0x%2in file 0x%4 is incorrect.	The index entry offset, 0x%3, of index %1 and VCN 0x%2in file 0x%4 is incorrect.
0x000069C5	The index entry offset, 0x%2, of index %1in file 0x%3 is incorrect.	The index entry offset, 0x%2, of index %1in file 0x%3 is incorrect.
0x000069C6	The bytes available, 0x%2, in index header for index %1 in file0x%4 is not equal to 0x%3.	The bytes available, 0x%2, in index header for index %1 in file0x%4 is not equal to 0x%3.
0x000069C7	The index header for index %1 and VCN 0x%2 in file 0x%3is not marked as index node.	The index header for index %1 and VCN 0x%2 in file 0x%3is not marked as index node.
0x000069C8	The VCN 0x%2 of index %1 in file 0x%3 is incorrect.	The VCN 0x%2 of index %1 in file 0x%3 is incorrect.
0x000069C9	The index bitmap for index %1 in file 0x%2 is invalid or missing.	The index bitmap for index %1 in file 0x%2 is invalid or missing.
0x000069CA	The VCN 0x%2 of index %1 in file 0x%3 is already in use.	The VCN 0x%2 of index %1 in file 0x%3 is already in use.
0x000069CB	The index allocation for index %1 in file 0x%2 is invalid or missing.	The index allocation for index %1 in file 0x%2 is invalid or missing.
0x000069CC	The multi-sector header signature for VCN 0x%2 of index %1in file 0x%3 is incorrect.	The multi-sector header signature for VCN 0x%2 of index %1in file 0x%3 is incorrect.
0x000069CD	The USA offset 0x%3 of VCN 0x%2 of index %1in file 0x%5 is below 0x%4.	The USA offset 0x%3 of VCN 0x%2 of index %1in file 0x%5 is below 0x%4.
0x000069CE	The VCN 0x%2 of index %1 in file 0x%4 is inconsistence withthe VCN 0x%3 stored inside the index buffer.	The VCN 0x%2 of index %1 in file 0x%4 is inconsistence withthe VCN 0x%3 stored inside the index buffer.
0x000069CF	The bytes per block, 0x%3, read from index buffer of VCN 0x%2of index %1 in file 0x%4 is incorrect.	The bytes per block, 0x%3, read from index buffer of VCN 0x%2of index %1 in file 0x%4 is incorrect.
0x000069D0	The USA offset 0x%3 of VCN 0x%2 of index %1in file 0x%4 is incorrect.	The USA offset 0x%3 of VCN 0x%2 of index %1in file 0x%4 is incorrect.
0x000069D1	The USA size 0x%3 of VCN 0x%2 of index %1 in file0x%5 is incorrect. The expected value is 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	The index header of index %1 in file 0x%2is marked as index node when it should not.	The index header of index %1 in file 0x%2is marked as index node when it should not.
0x000069D3	The first free byte, 0x%2, in index header of index %1in file 0x%4 is not equal to 0x%3.	The first free byte, 0x%2, in index header of index %1in file 0x%4 is not equal to 0x%3.
0x000069D4	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.	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	Index entry %2 of index 0x%1 points to unused or reused file 0x%3.	Index entry %2 of index 0x%1 points to unused or reused file 0x%3.
0x000069D6	An index entry of index 0x%1 points to unused or reused file 0x%2.	An index entry of index 0x%1 points to unused or reused file 0x%2.
0x000069D7	The file 0x%4 pointed to by index entry %3 of index %2 withparent file 0x%1 is not a base file record segment.	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	The file 0x%3 pointed to by an index entry of index %2 withparent file 0x%1 is not a base file record segment.	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	Unable to locate the file name attribute of index entry %3of index %2 with parent 0x%1 in file 0x%4.	Unable to locate the file name attribute of index entry %3of index %2 with parent 0x%1 in file 0x%4.
0x000069DA	Unable to locate the file name attribute of an index entryof index %2 with parent 0x%1 in file 0x%3.	Unable to locate the file name attribute of an index entryof index %2 with parent 0x%1 in file 0x%3.
0x000069DB	The object id index entry in file 0x%1 points to file 0x%2but the file has no object id in it.	The object id index entry in file 0x%1 points to file 0x%2but the file has no object id in it.
0x000069DC	The object id index entry in file 0x%1 points to file 0x%2which is not a base file record segment.	The object id index entry in file 0x%1 points to file 0x%2which is not a base file record segment.
0x000069DD	The object id in index entry in file 0x%1 is incorrect.The entry points to file 0x%2.	The object id in index entry in file 0x%1 is incorrect.The entry points to file 0x%2.
0x000069DE	The parent 0x%2 in an object id index entry in file 0x%1is incorrect. The correct value is 0x%3.	The parent 0x%2 in an object id index entry in file 0x%1is incorrect. The correct value is 0x%3.
0x000069DF	The object id in file 0x%2 already existed in the objectid index in file 0x%1.	The object id in file 0x%2 already existed in the objectid index in file 0x%1.
0x000069E0	The object id in file 0x%2 does not appear in the objectid index in file 0x%1.	The object id in file 0x%2 does not appear in the objectid index in file 0x%1.
0x000069E1	The reparse point index entry in file 0x%1 points to file 0x%2which is not a base file record segment.	The reparse point index entry in file 0x%1 points to file 0x%2which is not a base file record segment.
0x000069E2	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.	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	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.	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	The reparse point index entry in file 0x%1 points to file 0x%2but the file has no reparse point in it.	The reparse point index entry in file 0x%1 points to file 0x%2but the file has no reparse point in it.
0x000069E5	The reparse point in file 0x%2 does not appear inthe reparse point index in file 0x%1.	The reparse point in file 0x%2 does not appear inthe reparse point index in file 0x%1.
0x000069E6	The file name index present bit is set in file 0x%1but there is no file name index.	The file name index present bit is set in file 0x%1but there is no file name index.
0x000069E7	The root index %2 in file 0x%1 is missing or invalid.	The root index %2 in file 0x%1 is missing or invalid.
0x000069E8	The index entry length 0x%1 is incorrect. The maximum value is 0x%2.	The index entry length 0x%1 is incorrect. The maximum value is 0x%2.
0x000069E9	The index entry attribute length 0x%2 of index entry type 0x%1is incorrect. The correct length is 0x%3.	The index entry attribute length 0x%2 of index entry type 0x%1is incorrect. The correct length is 0x%3.
0x000069EA	The index entry data offset 0x%1 and length 0x%2 isinconsistence with the index entry length 0x%3.	The index entry data offset 0x%1 and length 0x%2 isinconsistence with the index entry length 0x%3.
0x000069EB	The index entry length is incorrect for index entry type 0x%1.	The index entry length is incorrect for index entry type 0x%1.
0x000069EC	The index entry length is too small for index entry type 0x%1.	The index entry length is too small for index entry type 0x%1.
0x000069ED	The volume information attribute is missing from file 0x%1.	The volume information attribute is missing from file 0x%1.
0x000069EE	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.	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	The attribute form code 0x%1 is invalid for attribute of type 0x%2and instance tag 0x%3.	The attribute form code 0x%1 is invalid for attribute of type 0x%2and instance tag 0x%3.
0x000069F0	The attribute of type 0x%1 and instance tag 0x%2 should be resident.	The attribute of type 0x%1 and instance tag 0x%2 should be resident.
0x000069F1	The standard information attribute length 0x%1 is incorrect.The expected value is 0x%2, 0x%3, or 0x%4.	The standard information attribute length 0x%1 is incorrect.The expected value is 0x%2, 0x%3, or 0x%4.
0x000069F2	Attribute name is not allowed for attribute of type 0x%1and instance tag 0x%2.	Attribute name is not allowed for attribute of type 0x%1and instance tag 0x%2.
0x000069F3	The attribute of type 0x%1 and instance tag 0x%2 should not be resident.	The attribute of type 0x%1 and instance tag 0x%2 should not be resident.
0x000069F4	The attribute name offset for attribute of type 0x%1and instance tag 0x%2 is incorrect.	The attribute name offset for attribute of type 0x%1and instance tag 0x%2 is incorrect.
0x000069F5	The attribute name for attribute of type 0x%1 and instance tag 0x%2contains unicode NULL.	The attribute name for attribute of type 0x%1 and instance tag 0x%2contains unicode NULL.
0x000069F6	Unknown attribute of type 0x%1 and instance tag 0x%2.	Unknown attribute of type 0x%1 and instance tag 0x%2.
0x000069F7	The attribute of type 0x%1 and instance tag 0x%2 should not be indexed.	The attribute of type 0x%1 and instance tag 0x%2 should not be indexed.
0x000069F8	The attribute of type 0x%1 and instance tag 0x%2 should be indexed.	The attribute of type 0x%1 and instance tag 0x%2 should be indexed.
0x000069F9	The indexable attribute of type 0x%1 and instance tag 0x%2should not have name.	The indexable attribute of type 0x%1 and instance tag 0x%2should not have name.
0x000069FA	The attribute of type 0x%1 and instance tag 0x%2 should have a name.	The attribute of type 0x%1 and instance tag 0x%2 should have a name.
0x000069FB	The attribute length 0x%1 for attribute of type 0x%3 andinstance tag 0x%4 is too small. The minimum value is 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	The attribute length 0x%1 for attribute of type 0x%3 andinstance tag 0x%4 is too big. The maximum value is 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	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.	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	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.	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	The mapping pairs offset 0x%1 for attribute of type 0x%3 and instancetag 0x%4 exceeded the attribute length 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	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.	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	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.	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	The attribute of type 0x%2 and instance tag 0x%3 in file 0x%4has bad mapping pairs at attribute offset 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	Unable to initialize an extent list for attribute type 0x%1 withinstance tag 0x%2.	Unable to initialize an extent list for attribute type 0x%1 withinstance tag 0x%2.
0x00006A04	The highest VCN 0x%1 of attribute of type 0x%3 and instancetag 0x%4 is incorrect. The expected value is 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	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.	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	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.	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	The allocated length 0x%1 is not in multiple of 0x%2 for attributeof type 0x%3 and instance tag 0x%4.	The allocated length 0x%1 is not in multiple of 0x%2 for attributeof type 0x%3 and instance tag 0x%4.
0x00006A08	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.	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	The attribute of type 0x%2 and instance tag 0x%3 is inconsistence.The attribute value length is 0x%1.	The attribute of type 0x%2 and instance tag 0x%3 is inconsistence.The attribute value length is 0x%1.
0x00006A0A	The file name length is zero for attribute of type 0x%1and instance tag 0x%2.	The file name length is zero for attribute of type 0x%1and instance tag 0x%2.
0x00006A0B	The file name in file name value in attribute of type 0x%1 and instancetag %2 contains invalid character.	The file name in file name value in attribute of type 0x%1 and instancetag %2 contains invalid character.
0x00006A0C	The multi-sector header signature in file 0x%1 is incorrect.	The multi-sector header signature in file 0x%1 is incorrect.
0x00006A0D	The USA offset 0x%1 in file 0x%3 is too small.The minimum value is 0x%2.	The USA offset 0x%1 in file 0x%3 is too small.The minimum value is 0x%2.
0x00006A0E	The file record segment size 0x%1 is invalid in file 0x%2.	The file record segment size 0x%1 is invalid in file 0x%2.
0x00006A0F	The USA offset 0x%1 in file 0x%2 is incorrect.	The USA offset 0x%1 in file 0x%2 is incorrect.
0x00006A10	The USA size 0x%1 in file 0x%3 is incorrect.The expected value is 0x%2.	The USA size 0x%1 in file 0x%3 is incorrect.The expected value is 0x%2.
0x00006A11	The first attribute offset 0x%1 in file 0x%2 is incorrect.	The first attribute offset 0x%1 in file 0x%2 is incorrect.
0x00006A12	The bytes available, 0x%1, in the file record segment header forfile 0x%3 is incorrect. The expected value is 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	The instance tag 0x%2 of attribute of type 0x%1 in file 0x%3is already in use.	The instance tag 0x%2 of attribute of type 0x%1 in file 0x%3is already in use.
0x00006A14	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.	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	The standard information attribute in file 0x%1 is missing.	The standard information attribute in file 0x%1 is missing.
0x00006A16	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.	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	The record length of attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be zero.	The record length of attribute of type 0x%1 and instance tag 0x%2in file 0x%3 should not be zero.
0x00006A18	The record length 0x%1 of attribute of type 0x%2 andinstance tag 0x%3 in file 0x%4 is not aligned.	The record length 0x%1 of attribute of type 0x%2 andinstance tag 0x%3 in file 0x%4 is not aligned.
0x00006A19	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.	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	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.	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	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.	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	All attribute of type 0x%1 and instance tag 0x%2 should be indexedin file 0x%5.	All attribute of type 0x%1 and instance tag 0x%2 should be indexedin file 0x%5.
0x00006A1D	Two identical attributes of type 0x%1 and instance tag 0x%2 arein file 0x%3.	Two identical attributes of type 0x%1 and instance tag 0x%2 arein file 0x%3.
0x00006A1E	The file name index present bit in file 0x%1 should not be set.	The file name index present bit in file 0x%1 should not be set.
0x00006A20	The sparse flag in the standard information attribute in file 0x%1is not set.	The sparse flag in the standard information attribute in file 0x%1is not set.
0x00006A21	The sparse flag in the standard information attribute in file 0x%1should not be set.	The sparse flag in the standard information attribute in file 0x%1should not be set.
0x00006A22	The old encrypted flag is being replaced by the new encrypted flagin file 0x%1.	The old encrypted flag is being replaced by the new encrypted flagin file 0x%1.
0x00006A23	The encrypted flag in standard information attribute in file 0x%1is not set.	The encrypted flag in standard information attribute in file 0x%1is not set.
0x00006A24	The reparse flag in standard information attribute in file 0x%1is not set.	The reparse flag in standard information attribute in file 0x%1is not set.
0x00006A25	The reparse flag in standard information attribute in file 0x%1should not be set.	The reparse flag in standard information attribute in file 0x%1should not be set.
0x00006A26	There are more than one NTFS file name attribute in file 0x%1.	There are more than one NTFS file name attribute in file 0x%1.
0x00006A27	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.	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	There are more than one DOS file name attribute in file 0x%1.	There are more than one DOS file name attribute in file 0x%1.
0x00006A29	The DOS file name attribute in file 0x%1 is incorrect.	The DOS file name attribute in file 0x%1 is incorrect.
0x00006A2A	There is no NTFS file name attribute in file 0x%1.	There is no NTFS file name attribute in file 0x%1.
0x00006A2B	There is no DOS file name attribute in file 0x%1.	There is no DOS file name attribute in file 0x%1.
0x00006A2C	The DOS and NTFS file name attributes in file 0x%1 are identical.	The DOS and NTFS file name attributes in file 0x%1 are identical.
0x00006A2D	Unable to setup the attribute list in file 0x%1.	Unable to setup the attribute list in file 0x%1.
0x00006A2E	The attribute type 0x%1 with name %2 in file 0x%3 is missing.	The attribute type 0x%1 with name %2 in file 0x%3 is missing.
0x00006A2F	The attribute of type 0x%1 in file 0x%2 is missing.	The attribute of type 0x%1 in file 0x%2 is missing.
0x00006A30	The unnamed data attribute in file 0x%1 is missing.	The unnamed data attribute in file 0x%1 is missing.
0x00006A31	The attribute list in file 0x%1 is missing.	The attribute list in file 0x%1 is missing.
0x00006A32	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.	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	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.	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	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.	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	The attribute list length 0x%2 in file 0x%3 is incorrect.The expected value is 0x%1.	The attribute list length 0x%2 in file 0x%3 is incorrect.The expected value is 0x%1.
0x00006A36	The extent list of the attribute list is crossed linked at 0x%1for possibly 0x%2 clusters in file 0x%3.	The extent list of the attribute list is crossed linked at 0x%1for possibly 0x%2 clusters in file 0x%3.
0x00006A37	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.	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	Two identical attribute list entries of type 0x%1 and instance tag 0x%2are found.	Two identical attribute list entries of type 0x%1 and instance tag 0x%2are found.
0x00006A39	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.	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	The sparse flag of attribute of type 0x%1 and name %2 in file0x%3 is not set.	The sparse flag of attribute of type 0x%1 and name %2 in file0x%3 is not set.
0x00006A3B	The USN Journal offset 0x%1 in file 0x%2 is not at a page boundary.	The USN Journal offset 0x%1 in file 0x%2 is not at a page boundary.
0x00006A3C	The USN Journal length 0x%1 in file 0x%3 is too large.The maximum value is 0x%2.	The USN Journal length 0x%1 in file 0x%3 is too large.The maximum value is 0x%2.
0x00006A3D	The USN Journal length 0x%1 in file 0x%3 is less thanits offset 0x%2.	The USN Journal length 0x%1 in file 0x%3 is less thanits offset 0x%2.
0x00006A3E	The remaining USN block at offset 0x%1 in file 0x%2 isless than a page.	The remaining USN block at offset 0x%1 in file 0x%2 isless than a page.
0x00006A3F	The remaining of an USN page at offset 0x%1 in file 0x%2should be filled with zeros.	The remaining of an USN page at offset 0x%1 in file 0x%2should be filled with zeros.
0x00006A40	The USN Journal entry at offset 0x%1 and length 0x%2 crossesthe page boundary.	The USN Journal entry at offset 0x%1 and length 0x%2 crossesthe page boundary.
0x00006A41	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.	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	The USN Journal entry length 0x%2 at offset 0x%1 in file0x%4 exceeded the page size 0x%3.	The USN Journal entry length 0x%2 at offset 0x%1 in file0x%4 exceeded the page size 0x%3.
0x00006A43	The USN Journal entry length 0x%2 at offset 0x%1 in file0x%3 is not aligned.	The USN Journal entry length 0x%2 at offset 0x%1 in file0x%3 is not aligned.
0x00006A44	The USN Journal entry version %2.%3 at offset 0x%1in file 0x%4 is not recognized.	The USN Journal entry version %2.%3 at offset 0x%1in file 0x%4 is not recognized.
0x00006A45	The USN Journal entry length 0x%2 at offset 0x%1 in file0x%4 is too small. The minimum value is 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	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.	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	The USN value 0x%1 of USN Journal entry at offset 0x%2in file 0x%3 is incorrect.	The USN value 0x%1 of USN Journal entry at offset 0x%2in file 0x%3 is incorrect.
0x00006A48	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.	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	The USN Journal length 0x%1 in file 0x%4 is less thelargest USN encountered, 0x%2, plus eight in file 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	The security data stream is missing from file 0x%1.	The security data stream is missing from file 0x%1.
0x00006A4B	The security data stream size 0x%1 should not be less than 0x%2.	The security data stream size 0x%1 should not be less than 0x%2.
0x00006A4C	The remaining of a security data stream page starting at offset 0x%1for 0x%2 bytes contains non-zero.	The remaining of a security data stream page starting at offset 0x%1for 0x%2 bytes contains non-zero.
0x00006A4D	The security data stream entry at offset 0x%1 with length 0x%2crosses the page boundary.	The security data stream entry at offset 0x%1 with length 0x%2crosses the page boundary.
0x00006A4E	The length, 0x%2, of the security data stream entry at offset0x%1 is too small. The minimum value is 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	The length, 0x%2, of the security data stream entry at offset0x%1 exceeded the page size 0x%3.	The length, 0x%2, of the security data stream entry at offset0x%1 exceeded the page size 0x%3.
0x00006A50	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.	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	The security descriptor entry with Id 0x%2 at offset 0x%1 is invalid.	The security descriptor entry with Id 0x%2 at offset 0x%1 is invalid.
0x00006A52	The security Id 0x%2 of security descriptor entry at offset 0x%1is a duplicate.	The security Id 0x%2 of security descriptor entry at offset 0x%1is a duplicate.
0x00006A53	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.	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	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.	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	The security descriptor in file 0x%1 is invalid.	The security descriptor in file 0x%1 is invalid.
0x00006A56	The security Id 0x%1 in file 0x%2 is invalid.	The security Id 0x%1 in file 0x%2 is invalid.
0x00006A57	The data stream with name %1 in file 0x%2 is not recognized.	The data stream with name %1 in file 0x%2 is not recognized.
0x00006A58	The attribute definition table length 0x%1 is incorrect.The correct value is 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.	The attribute definition table content is incorrect.
0x00006A5A	Cluster zero is missing from the data attribute in boot file.	Cluster zero is missing from the data attribute in boot file.
0x00006A5B	Attribute list found in the log file.	Attribute list found in the log file.
0x00006A5C	The data attribute is either resident or missing in the log file.	The data attribute is either resident or missing in the log file.
0x00006A5D	Unable to obtain the LCN in data attribute of the MFT mirror.	Unable to obtain the LCN in data attribute of the MFT mirror.
0x00006A5E	There is no physical LCN for VCN 0 in data attribute of the MFT mirror.	There is no physical LCN for VCN 0 in data attribute of the MFT mirror.
0x00006A5F	The data attribute of the MFT mirror is not contiguous for 0x%1 sectors.	The data attribute of the MFT mirror is not contiguous for 0x%1 sectors.
0x00006A60	The MFT mirror is different from the MFT.	The MFT mirror is different from the MFT.
0x00006A61	The data attribute is missing from the upcase file.	The data attribute is missing from the upcase file.
0x00006A62	The upcase file length 0x%1 is incorrect. The expected value is 0x%2.	The upcase file length 0x%1 is incorrect. The expected value is 0x%2.
0x00006A63	The upcase file content is incorrect.	The upcase file content is incorrect.
0x00006A64	The data attribute is either resident or missing in the MFT mirror.	The data attribute is either resident or missing in the MFT mirror.
0x00006A65	The two index entries of length 0x%1 and 0x%2 are either identicalor appear in the wrong order.	The two index entries of length 0x%1 and 0x%2 are either identicalor appear in the wrong order.
0x00006A66	The first index entry of length 0x%1 is a leaf but it is not in the root.	The first index entry of length 0x%1 is a leaf but it is not in the root.
0x00006A67	The first index entry of length 0x%1 is a leaf but the previous entry is not.	The first index entry of length 0x%1 is a leaf but the previous entry is not.
0x00006A68	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.	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	The down pointer of current index entry with length 0x%1 is invalid.	The down pointer of current index entry with length 0x%1 is invalid.
0x00006A6A	The index entry length 0x%1 is too large. The maximum value is 0x%2.	The index entry length 0x%1 is too large. The maximum value is 0x%2.
0x00006A6B	The allocation attribute does not exist.	The allocation attribute does not exist.
0x00006A6C	Clearing unused security descriptor stream entries.	Clearing unused security descriptor stream entries.
0x00006A6D	Mirror security descriptor block different from that ofmaster security descriptor at offset 0x%1.	Mirror security descriptor block different from that ofmaster security descriptor at offset 0x%1.
0x00006A6E	The attribute definition table cannot be read.	The attribute definition table cannot be read.
0x00006A6F	The index buffer at VCN 0x%2 of index %1 in file 0x%3cannot be read.	The index buffer at VCN 0x%2 of index %1 in file 0x%3cannot be read.
0x00006A70	The MFT mirror starting at cluster 0x%1 for 0x%2 sectorscannot be read.	The MFT mirror starting at cluster 0x%1 for 0x%2 sectorscannot be read.
0x00006A71	The security descriptor in file 0x%1 cannot be read.	The security descriptor in file 0x%1 cannot be read.
0x00006A72	The upcase table cannot be read.	The upcase table cannot be read.
0x00006A73	The USN attrib of type code 0x%1 and name %2 cannot beread in file 0x%3.	The USN attrib of type code 0x%1 and name %2 cannot beread in file 0x%3.
0x00006A74	The EA Data value length, 0x%1, in file 0x%2 is incorrect.	The EA Data value length, 0x%1, in file 0x%2 is incorrect.
0x00006A75	The index entry length 0x%2 for index %1 in file 0x%4is too large. The maximum value is 0x%3.	The index entry length 0x%2 for index %1 in file 0x%4is too large. The maximum value is 0x%3.
0x00006A76	Unable to query extent list entry 0x%3 from attributeof type 0x%1 and instance tag 0x%2.	Unable to query extent list entry 0x%3 from attributeof type 0x%1 and instance tag 0x%2.
0x00006A77	The total allocated size 0x%1 for attribute of type 0x%3 andinstance tag 0x%4 is larger than the allocated length 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	Unable to locate attribute with instance tag 0x%2 and segmentreference 0x%3. The expected attribute type is 0x%1.	Unable to locate attribute with instance tag 0x%2 and segmentreference 0x%3. The expected attribute type is 0x%1.
0x00006A79	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.	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	Some clusters occupied by attribute of type 0x%1 and instance tag 0x%2in file 0x%3 is already in use.	Some clusters occupied by attribute of type 0x%1 and instance tag 0x%2in file 0x%3 is already in use.
0x00006A7B	Unable to setup the child file record segment 0x%2 in file 0x%1.	Unable to setup the child file record segment 0x%2 in file 0x%1.
0x00006A7C	The parent 0x%2 of index entry %3in file 0x%4 is incorrect. The expected parent is 0x%1.	The parent 0x%2 of index entry %3in file 0x%4 is incorrect. The expected parent is 0x%1.
0x00006A7D	The file reference 0x%3 of an index entry %2 inparent 0x%1 is not the same as 0x%4.	The file reference 0x%3 of an index entry %2 inparent 0x%1 is not the same as 0x%4.
0x00006A7E	The file reference 0x%3 of an index entry of index %2with parent 0x%1 is not the same as 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	Multiple object id index entries in file 0x%1point to the same file 0x%2.	Multiple object id index entries in file 0x%1point to the same file 0x%2.
0x00006A80	The object id index entry in file 0x%1 points to file 0x%2which is unreadable.	The object id index entry in file 0x%1 points to file 0x%2which is unreadable.
0x00006A81	The object id index entry in file 0x%1 points to file 0x%2which is not in use.	The object id index entry in file 0x%1 points to file 0x%2which is not in use.
0x00006A82	The reparse point index entry in file 0x%1 points to file 0x%2which is not in use.	The reparse point index entry in file 0x%1 points to file 0x%2which is not in use.
0x00006A83	The reparse point index entry in file 0x%1 points to file 0x%2which is unreadable.	The reparse point index entry in file 0x%1 points to file 0x%2which is unreadable.
0x00006A84	----------------------------------------------------------------------	----------------------------------------------------------------------
0x00006A85	Cleaning up instance tags for file 0x%1.	Cleaning up instance tags for file 0x%1.
0x00006A86	Cleaning up encrypted flag for file 0x%1.	Cleaning up encrypted flag for file 0x%1.
0x00006A87	Cleaning up sparse flag for file 0x%1.	Cleaning up sparse flag for file 0x%1.
0x00006A88	Cleaning up %3 unused index entries from index %2 of file 0x%1.	Cleaning up %3 unused index entries from index %2 of file 0x%1.
0x00006A89	Cleaning up %1 unused security descriptors.	Cleaning up %1 unused security descriptors.
0x00006A8A	The value length, 0x%1, of the MFT mirror is too small.The minimum value is 0x%2.	The value length, 0x%1, of the MFT mirror is too small.The minimum value is 0x%2.
0x00006A8B	The valid data length, 0x%1, of the MFT mirror is too small.The minimum value is 0x%2.	The valid data length, 0x%1, of the MFT mirror is too small.The minimum value is 0x%2.
0x00006A8C	Index entry %3 of index %2 in file 0x%1 points to unused file 0x%4.	Index entry %3 of index %2 in file 0x%1 points to unused file 0x%4.
0x00006A8D	An index entry of index %2 in file 0x%1 points to unused file 0x%3.	An index entry of index %2 in file 0x%1 points to unused file 0x%3.
0x00006A8E	Unable to obtain the LCN in data attribute for VCN 0x%1 of the MFT.	Unable to obtain the LCN in data attribute for VCN 0x%1 of the MFT.
0x00006A8F	An index entry of index %2 in file 0x%1 points to file 0x%3which is beyond the MFT.	An index entry of index %2 in file 0x%1 points to file 0x%3which is beyond the MFT.
0x00006A90	The segment number 0x%1 in file 0x%2 is incorrect.	The segment number 0x%1 in file 0x%2 is incorrect.
0x00006A91	Internal Info:	Internal Info:
0x00006A92	The mapping pairs offset 0x%1 for attribute of type 0x%2 and instancetag 0x%3 is not quad aligned.	The mapping pairs offset 0x%1 for attribute of type 0x%2 and instancetag 0x%3 is not quad aligned.
0x00006A93	The NTFS file name attribute in file 0x%1 is incorrect.	The NTFS file name attribute in file 0x%1 is incorrect.
0x00006A94	The attribute of type 0x%1 and instance tag 0x%2 has unexpected holes in the extent list.	The attribute of type 0x%1 and instance tag 0x%2 has unexpected holes in the extent list.
0x00006A95	The TxF file name attribute in file 0x%1 is corrupt.	The TxF file name attribute in file 0x%1 is corrupt.
0x00006A96	The $Txf file name attribute in file 0x%1 is a duplicate.	The $Txf file name attribute in file 0x%1 is a duplicate.
0x00006A97	The $Txf file name attribute in file 0x%1 is corrupt.	The $Txf file name attribute in file 0x%1 is corrupt.
0x00006A98	The $STANDARD_INFORMATION attribute was corrupted for a $Txf directory.	The $STANDARD_INFORMATION attribute was corrupted for a $Txf directory.
0x00006A99	The $STANDARD_INFORMATION attribute was corrupted for a RM Root directory.	The $STANDARD_INFORMATION attribute was corrupted for a RM Root directory.
0x00006A9A	The TxF file name attribute in file 0x%1 is a duplicate.	The TxF file name attribute in file 0x%1 is a duplicate.
0x00006A9B	A TxF RM root file reference was corrupt.	A TxF RM root file reference was corrupt.
0x00006A9C	Detected cross linked attribute of type code 0x%1 and instance tag 0x%2for file record 0x%3.	Detected cross linked attribute of type code 0x%1 and instance tag 0x%2for file record 0x%3.
0x00006A9D	File record 0x%1 maps to \"%2\".	File record 0x%1 maps to \"%2\".
0x00006A9E	The index entry %3 in index 0x%2 of file 0x%1 is missing.	The index entry %3 in index 0x%2 of file 0x%1 is missing.
0x00006A9F	The parent 0x%1 of file name attribute %2 in file 0x%3 cannot be found.	The parent 0x%1 of file name attribute %2 in file 0x%3 cannot be found.
0x00006AA0	The file name flags 0x%1 in index entry %2 of parent 0x%3 is inconsistentwith that in file 0x%4.	The file name flags 0x%1 in index entry %2 of parent 0x%3 is inconsistentwith that in file 0x%4.
0x00006AA1	The only attribute in the file 0x%1 is the standard information.	The only attribute in the file 0x%1 is the standard information.
0x01000062	Volume %1 (%2) %3	Volume %1 (%2) %3
0x0100008C	The system failed to flush data to the transaction log. Corruption may occur in 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	Thinly provisioned volume %1 (%2)%nwere not being mapped between clusters %3 and %4.%nIt is now fixed.	Thinly provisioned volume %1 (%2)%nwere not being mapped between clusters %3 and %4.%nIt is now fixed.
0x010000D3	Thinly provisioned volume %1 (%2)%nwere not being mapped between clusters %3 and %4.%nRepair was unsucccessful.%nPossibly out of available slabs.	Thinly provisioned volume %1 (%2)%nwere not being mapped between clusters %3 and %4.%nRepair was unsucccessful.%nPossibly out of available slabs.
0x11000016	Statistics	Statistics
0x11000019	BadClusterHotFix	BadClusterHotFix
0x31000000	Info	Info
0x31000001	Start	Start
0x31000002	Stop	Stop
0x31000007	Resume	Resume
0x31000008	Suspend	Suspend
0x40040024	A user hit their quota threshold on volume %2.	A user hit their quota threshold on volume %2.
0x40040025	A user hit their quota limit on volume %2.	A user hit their quota limit on volume %2.
0x40040026	The system has started rebuilding the user disk quota information ondevice %1 with label \"%2\".	The system has started rebuilding the user disk quota information ondevice %1 with label \"%2\".
0x40040027	The system has successfully rebuilt the user disk quota information ondevice %1 with label \"%2\".	The system has successfully rebuilt the user disk quota information ondevice %1 with label \"%2\".
0x50000002	Error	Error
0x50000003	Warning	Warning
0x50000004	Information	Information
0x80040028	The system has encounted an error rebuilding the user disk quotainformation on device %1 with label \"%2\".	The system has encounted an error rebuilding the user disk quotainformation on device %1 with label \"%2\".
0x80040032	{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.	{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	The transaction resource manager on volume %2 encountered an error during recovery. The resource manager will continue recovery.	The transaction resource manager on volume %2 encountered an error during recovery. The resource manager will continue recovery.
0x80040088	The default transaction resource manager on volume %2 encountered an error while starting and its metadata was reset. The data contains the error code.	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	{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.	{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	{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.	{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	{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.	{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 global corruption action state is now %1.	NTFS global corruption action state is now %1.
0xB100008B	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.	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, Reason: %2	NtfsLogFileFull VolumeId: %1, Reason: %2
0xB10000CA	PeriodicCheckpointStart VolumeId: %1, Reason: %2, Usage: %3%	PeriodicCheckpointStart VolumeId: %1, Reason: %2, Usage: %3%
0xB10000CB	PeriodicCheckpointComplete VolumeId: %1, DirtyMetaDataPages: %2	PeriodicCheckpointComplete VolumeId: %1, DirtyMetaDataPages: %2
0xB10000CC	CleanCheckpointStart VolumeId: %1, Reason: %2, Usage: %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 queued, WorkItem: %1, Reason: %2	WorkItem queued, WorkItem: %1, Reason: %2
0xB10000E7	WorkItem queue failed, WorkItem: %1, Reason: %2, Error: %3	WorkItem queue failed, WorkItem: %1, Reason: %2, Error: %3
0xB10000E8	WorkItem started, WorkItem: %1, Reason: %2	WorkItem started, WorkItem: %1, Reason: %2
0xB10000E9	WorkItem completed, WorkItem: %1, Reason: %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 has sent volume dismount event notification and is waiting for the notifications to complete.	NTFS has sent volume dismount event notification and is waiting for the notifications to complete.
0xB100012E	The volume dismount event notification on the NTFS volume has completed.	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	The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the device %1 with label \"%2\".	The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the device %1 with label \"%2\".
0xC004002A	The user disk quota information is unusable.To ensure accuracy, the file system quota information on the device %1 with label \"%2\" willbe rebuilt.	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	The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the volume %2.	The file system structure on the disk is corrupt and unusable.Please run the chkdsk utility on the volume %2.
0xC0040087	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.	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	The default transaction resource manager on volume %2 encountered a non-retryable error and could not start. The data contains the error code.	The default transaction resource manager on volume %2 encountered a non-retryable error and could not start. The data contains the error code.
0xC004008A	The transaction resource manager at %2%3 encountered a fatal error and was shut down. The data contains the error code.	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.	is healthy. No action is needed.
0xD1000002	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.	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	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.	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	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.	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	Write: NonPaging, NonCached, Async
0xD1000027	Write: NonPaging, NonCached, Sync	Write: NonPaging, NonCached, Sync
0xD1000028	Write: NonPaging, NonCached, Async, Writethrough	Write: NonPaging, NonCached, Async, Writethrough
0xD1000029	Write: NonPaging, NonCached, Sync, Writethrough	Write: NonPaging, NonCached, Sync, Writethrough
0xD100002A	Write: NonPaging, Cached, Async	Write: NonPaging, Cached, Async
0xD100002B	Write: NonPaging, Cached, Sync	Write: NonPaging, Cached, Sync
0xD100002C	Write: NonPaging, Cached, Async, Writethrough	Write: NonPaging, Cached, Async, Writethrough
0xD100002D	Write: NonPaging, Cached, Sync, Writethrough	Write: NonPaging, Cached, Sync, Writethrough
0xD100002E	Write: Paging, NonCached, Async	Write: Paging, NonCached, Async
0xD100002F	Write: Paging, NonCached, Sync	Write: Paging, NonCached, Sync
0xD1000030	Write: Paging, NonCached, Async, Writethrough	Write: Paging, NonCached, Async, Writethrough
0xD1000031	Write: Paging, NonCached, Sync, Writethrough	Write: Paging, NonCached, Sync, Writethrough
0xD1000032	Read: NonPaging, NonCached, Async	Read: NonPaging, NonCached, Async
0xD1000033	Read: NonPaging, NonCached, Sync	Read: NonPaging, NonCached, Sync
0xD1000034	Read: NonPaging, Cached, Async	Read: NonPaging, Cached, Async
0xD1000035	Read: NonPaging, Cached, Sync	Read: NonPaging, Cached, Sync
0xD1000036	Read: Paging, NonCached, Async	Read: Paging, NonCached, Async
0xD1000037	Read: Paging, NonCached, Sync	Read: Paging, NonCached, Sync
0xD1000038	read	read
0xD1000039	write	write

File Name:	ntfs.sys.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-ntfs.resources_31bf3856ad364e35_10.0.15063.0_en-us_f5c615b69703f97c\
File Size:	97 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	98816
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Driver
File Subtype:	7
Language Code:	English (U.S.)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	NT File System Driver
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	ntfs.sys
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	ntfs.sys.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0

ntfs.sys.mui is Multilingual User Interface resource file that contain English (U.S.) language for file ntfs.sys (NT File System Driver).

File Description:	NT File System Driver
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	ntfs.sys
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	ntfs.sys.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x409, 1200