[W2K3] CHKDSK reset all file permissions

Last friday I rebooted one of our servers. When it came up, it ran checkdisk, but then chkdsk said "Replacing invalid security id with default security" and it did just that: on one of the disks it replaced ALL file permissions with default permissions (so only Administrators and system had access to the files). We had to reset the file permissions by hand.

Searching for a reason for this I found http://support.microsoft.com/default.aspx?scid=kb;en-us;831374 (The CHKDSK utility incorrectly identifies and deletes in-use security descriptors), which describes that this can happen when a volume contains over 4,194,303 files, and/or the Master File Table on the volume is over 4 GB in size. However, if I understand it correctly, it would only reset permissions for the files after 4,194,303, so the first 4,194,303 file permissions would remain intact. Same for the MFT: only files whose entry is "after" 4 GB in the MFT would be reset, the rest of the permissions should remain intact. However, in my situation, the permissions on all files were changed. The disk contains some 900.000 files.

Another article I found describes my problem better: http://support.microsoft.com/?kbid=873437. Here a bug in chkdsk is described where permissions on all files on a volume would be reset to default permissions, however, this article applies to Windows 2000 Server only and I'm running Windows Server 2003. The problem has been fixed in servicepack 4 so I guess it should be solved in Windows Server 2003 as well. I haven't been able to find a 2003-version of this article.

I'm wondering, since none of these articles accurately describe my problem, if one of 'm could apply to my situation, or if anyone knows another reason why checkdisk reset all permissions?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Why you ask?  I think it's a simple answer really...  Microsoft.

Fixed in Service Pack 4?  That may mean it will be fixed in Server 2003 when they come out with Service Pack 4.   Just a possiblity.  :)

As to a fix?  Can you restore a previous backup of the drive?  NTFS file permissions should be restored as well...   I forget the exceptions at the moment...  

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.