Article ID: 873437
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Advanced Server
SYMPTOMS
When you use the chkdsk command to fix hard-disk errors on your Microsoft Windows 2000-based computer, the chkdsk command may incorrectly identify problems with the security descriptors for particular files or folders.
Note These files or folders reside on volumes that are formatted with the NTFS file system.
In this scenario, you experience the following symptoms:
- The chkdsk command line or the chkdsk /f command line reports that the security descriptors are not valid, even though the security descriptors actually are valid.
- The chkdsk /f command line replaces the security descriptors that it detects as not valid with the default security descriptors. Therefore, permissions that you previously configured on particular files and folders are reset to use the default settings.
The following is an example of output that you may receive when you run the chkdsk command with the /f switch:
CHKDSK is verifying security descriptors (stage 3 of 3)... Repairing the security file record segment. Deleting an index entry with Id 261 from index $SII of file 9. Deleting an index entry with Id 262 from index $SII of file 9. Deleting an index entry with Id 263 from index $SII of file 9. Deleting an index entry with Id 264 from index $SII of file 9. Deleting an index entry with Id 265 from index $SII of file 9. Deleting an index entry with Id 266 from index $SII of file 9. Deleting an index entry with Id 265 from index $SDH of file 9. Deleting an index entry with Id 261 from index $SDH of file 9. Deleting an index entry with Id 263 from index $SDH of file 9. Deleting an index entry with Id 266 from index $SDH of file 9. Deleting an index entry with Id 264 from index $SDH of file 9. Deleting an index entry with Id 262 from index $SDH of file 9. Replacing invalid security id with default security id for file 29. Replacing invalid security id with default security id for file 30. Replacing invalid security id with default security id for file 35. Replacing invalid security id with default security id for file 36. Cleaning up 1 unused index entries from index $SII of file 9. Cleaning up 1 unused index entries from index $SDH of file 9. Cleaning up 1 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. Windows has made corrections to the file system.
CAUSE
This problem occurs if the following conditions are true:
- The file's security descriptor contains an access control entry (ACE).
- This ACE uses an ACE type that the version of the chkdsk command in Windows 2000 does not fully recognize.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
This hotfix requires Windows 2000 Service Pack 4 (SP4).
When you install this hotfix, make sure that you also install the hotfix that is documented in the following article in the Microsoft Knowledge Base:
831375 The CHKDSK utility incorrectly identifies and deletes in-use security descriptors in Windows 2000
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name --------------------------------------------------------- 19-Jun-2003 21:05 5.0.2195.6605 576,272 Autochk.exe 17-Jul-2004 02:23 5.0.2195.6960 66,832 Ifsutil.dll 19-Jun-2003 21:05 5.0.2195.6605 17,680 Fmifs.dll 19-Jun-2003 21:05 5.0.2195.6625 261,392 Ulib.dll 19-Jun-2003 21:05 5.0.2195.6660 321,296 Untfs.dll 19-Jun-2003 21:05 5.0.2195.6605 83,216 Ufat.dll 19-Jun-2003 21:05 5.0.2195.6625 13,584 Chkdsk.exe 05-Jun-2004 00:13 5.0.2195.6935 5,887,488 Sp3res.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
This hotfix is included in the list of recommended hotfixes to be proactively applied to Windows 2000 server clusters. Click the following article number to view the article that contains this list in the Microsoft Knowledge Base:
895090 Recommended hotfixes for Windows 2000 Service Pack 4-based server clusters
This hotfix should be evaluated and applied proactively to all server clusters that are prone to be negatively affected by the problem that is described in this article.
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbbug kbfix kbwin2000presp5fix kbhotfixserver kbqfe KB873437
