How do you delete a corrupt AOL file, when it says to run chkdsk utility

-mike

I tried everything in this thread, including Unlocker and GiPo@Utilities, but I still have the corrupted file that prevents CHKDSK from completing and won't allow me to make a backup image of my drive.

Any other suggestions?

Thank you in advance.

Replying to yordan

Thank you. Using "chkdsk g: /F" enabled the deletion of a corrupt file on a flash drive.

Deleting a corrupted file
Deleting A Corrupt File

I am certainly not the most computer savvy person, and I just deleted a corrupt file with the DOS command prompt as specified above. Using the chkdsk feature was so easy. Thanks a lot guys, saved me a lot of frustration. One google search and a little common sense, problem solved.

Thanks again.

Matt

-Matt

Chkdsk in Command Prompt to delete corrupted files
Deleting A Corrupt File

Replying to yordan

Thanks. Chkdsk in command prompt with the F/ option worked like a dream for me.



-Harry



------------------

You're welcome, Harry, Nice to have been helpful.

Yordan

Unlocker just worked on my two corrupted hidden system files.





-Greg

Unlocker worked for me
Deleting A Corrupt File

Yay! unlocker worked for me! I had a file that I coudnt delete and now it did!

Interesting, I think I should keep this in mind because a lot of my files get corrupted throughout time.

xboxrulz

I cant delete a corruppt file, I tried using chkdsk with no results...HELP! Any help would be greatly appreciated

thx, jay

Having just spent two days figuring out how to delete a corrupt file in Windows NTFS, I can tell you more than you want to know about it. This is on Windows 2000 Pro, so your mileage may vary with other OSs.

First, the GUI Checkdisk will not touch it. It will tell you the disk is fine. (I knew it was not, because my backup program quit with a "read error" message.) The defrag program will treat it as untouchable, and defrag everything else around it.

As others have said, there are many warnings against using Linux to alter NTFS filesystems. The folks who are trying to change this are at Linux-NTFS, and think they have fixed it. Specifically, they say: We just have released ntfsprogs 2.0.0 with full read/write support! So if you have this version, it may be able to do the cleanup.

However, back to doing it in Windows. It turns out that Microsoft has a Knowledge Base Article that relates to this issue. One learns there that the DOS version of chkdsk can do things the GUI version cannot. However, the story is not yet over. If you try to run the DOS chkdsk in the Windows partition you are trying to repair, it will tell you Cannot lock current drive .. the volume is in use by another and refuse to run. You must have a multi-boot system with 2 (or more) Windows partitions, and run chkdsk D: /f /r with "D:" replaced by the drive assigned to the partition with the bad file. Actually, it turns out that chkdsk D: /r will repair it, even though it is not supposed to make any changes without the /f switch. I tried omitting the /f switch because I wanted to test some other options, but the bad sector was removed by that operation.

It's amazing to me that the GUI checkdisk gives a disk with read errors a clean bill of health, but don't forget that this software is from Microsoft.