Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
File Corruption Occurs on an NTFS Volume with More Than 4 Million Files
Article ID: 229607 - View products that this article applies to.
This article was previously published under Q229607
When you create and delete files on an NTFS volume that holds more than 4 million files, you see file corruption that may show up in one of the following ways:
This problem occurs when the Master File Table (MFT) has grown larger than 4 GB, which may happen when you have more than 4 million files on your computer. When you delete a file whose MFT entry is beyond the 4 GB point under these conditions, an error in calculations causes the wrong entry to be marked as available. If this entry contains information for another file, and new files are added to the volume shortly after the deletion occurs, the entry could be re-used causing the file it actually referenced to be lost.
Windows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.
Information on all files in an NTFS volume is stored in the MFT. The MFT contains one or more an entries for all files on the system. In addition, the MFT maintains empty or unused entries which can be used for newly created files. When a file is deleted, it's entry is marked as being unused so that when a new file is created, the file system can re-use the entry.
Article ID: 229607 - Last Review: June 11, 2012 - Revision: 3.0