There are repeated discussions verging on arguments every day on here about chkdsk damaging and corrupting files if you do a /r because while it's ok at finding bad sectors, it does a lousy job at recovering data off them before it sets them aside forever, and so the affected files, folders, perhaps even the file allocation table (although the filesystem keeps two of those for redundancy) end up with ZEROS in them, corrupt by the failure to recover bad sectors that was written there. That's a BIG difference and could be a MISTAKE if not handled properly. Same for scandisk (right click tools) with the tickbox checked for bad sectoring (same thing) I guess if I took an image and tried restoring it that would fail also / I couldn't format new partition.įirst of all, /R is to repair BAD SECTORS, completely different from /F to FIX filesystem integrity. Is there any way I can resolve this problem?

Windows cannot run disk checking on this volume because it is write protected.' I've also tried this from win7 CD but get the same errorafter all suggestions on that page: I can still reboot windows and login however and errors continue. 'Setup did not find any hard disk drivers installed in your computer' When booting WinXP recovery console form CD we get error:

If I enable chkdsk from either C: drive properties > tools > check now, or opening cmd prompt chkdsk, then reboot it doesnt even attempt to run chkdsk and boots windows normally.

We a computer with a mixture of problems incl $MFT errors and ballons saying xxx program file or directory xxxxxx is corrupt and unreadable.