Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a corrupted folder on my win 2003 server which is occupying a lot of hd space, unfortunately there's no way deleting it - when showing its properties it shows several GB of occupied space but when viewing the content itself it doesn't show anything .. any ideas how to fix it?

share|improve this question
What is the folder called? It might be a system folder you shouldn't be messing with. For example, if it's System Volume Information or WinSxS... leave well alone! – Ben Pilbrow May 21 '11 at 18:24
How do you know it's corrupted? – Jim B May 21 '11 at 18:43
Make a backup before you start playing around w/ it. – Evan Anderson May 22 '11 at 6:42

Without some more information, it could be a couple things. It could be that what's in the folder are protected OS files that you wouldn't be able to view by default. You need to go into folder options and check the "view protected operating system files" to see those. I wouldn't necessarily recommend deleting those right off the bat, however, as usually that causes Bad Things to happen.

Alternatively, if it is folder corruption, you should run chkdsk to verify this. You can run it with /p first to verify, then run it with /f to try and fix the errors if any are found.

share|improve this answer

If the points identified by Holocryptic has been satisfied and the problem/situation persists, then you might also consider mounting that file volume under a 'nix distro which has NTFS support to see if it offers more control towards resolving it.

share|improve this answer
Just in case, mounting a corrupted NTFS volume under many of the unix distros often makes the volume unrecoverable by any tool. I would only try that as a last resort. – Jim B May 21 '11 at 18:42
To be fair and accurate, your mileage may vary - use at your own risk, but it is a viable option in same cases and more so with the recent 'nix implementations. – user48838 May 22 '11 at 1:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.