Deleting Corrupted Files on Windows

Question

Deleting corrupted files seems to be a real pain. All the suggestions out there recommend either formatting the drive or using Linux. What to do when both of these are not an option?

Note, that using robocopy, remdir, and del in the terminal, or remove-item in powershell are all returning the same error - "the file is corrupted or unreadable". Even echo 'hello' > <filename> is giving the same error.

Has anyone come across a simple and quick - windows only - working solution, that does not require third party tools?

EDIT: My question specifically asks for a simple - no linux - and, quick - no full disk scans - solution. My question does not relate to locked files, rather corrupted ones, and therefore, I do not see it as a duplicate to this post.

Maybe you need to use the native Windows error correction tool first. — , Mar 25 '19 at 11:07
@GabrielaGarcia - If your refering to chkdisk, I've seen it suggested. But I'm specifically looking for a "simple" answer. I should've been more clear. "Simple" here, means "Quick". Thanks for the tip though. — sh7411usa, Mar 25 '19 at 11:26
Yes, that one in CLI or what is basically the same tool in a graphical interface. Right-click the drive, properties and you'll find the tools tab. It can't be easier than that. — , Mar 25 '19 at 11:30
Possible duplicate of How to force the deletion of a locked file that has no locking handle on Windows? — Run5k, Mar 25 '19 at 12:48
@sh7411usa Yes, it is... but the underlying goal is essentially the same, and it should still work. — Run5k, Mar 26 '19 at 12:46
running chkdsk is the quickest way to fix. If disk metadata has been corrupted, obviously nothing can't be read or written without fixing the metadata. By the time you finish typing this answer, chkdsk may have already finished its job — phuclv, Mar 26 '19 at 12:48

score 1 · Accepted Answer · answered Mar 26 '19 at 12:38

1

If your filesystem is inconsistent, deleting corrupted files probably won't fix it. File corruption is a symptom, not the core issue. The correct next step is to run chkdsk /f. Easier solutions are insufficient solutions.

answered Mar 26 '19 at 12:38

gronostaj

57,004

Deleting Corrupted Files on Windows

1 Answers1