Acer Aspire E1-731 How can manually I delete chkdsk logs from the D: drive?

Traceyad2032

Acer Aspire E1-731 Windows 7

Windows normally boots from C: (which has no errors), but it is the D: drive has the issue:

Booting from a USB B:\drive (then running chkdsk /v/f D:), chkdsk shows the errors but will NOT fix them and I am unable to manually delete chkdsk log files from (D:\System Volume Information\chkdsk) as an Admin using the CMD prompt or Windows Explorer
Every time I run [chkdsk /v/f D:] these errors appear:
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file Chkdsk20240520105220.log (60213) into directory file 17.
...
Recovering orphaned file Chkdsk20240624151105.log (70383) into directory file 17.
10 unindexed files scanned.
Recovering orphaned file Chkdsk20240627104049.log (70384) into directory file 17.
0 unindexed files recovered.

[Edited the thread to add model name to the title]

sri369

Backup any data you have on D drive and format the drive; this should get rid of getting chkdsk issues. You should be able to do this from within windows too.

Traceyad2032

I was hoping to avoid that.

Thanks, Anyway

Traceyad2032

Out of desperation, and none of the suggestions from internet posts worked, I tried:

del /f /s <drive>:\chdsk2024*.log

and it worked (and I do NOT know why)!!!

I specified only the logs that would NOT clear using a USB boot drive.

Please pass this along to anyone that has the same issue.

Thanks, Tracey

sri369

https://community.acer.com/en/discussion/comment/1330096#Comment_1330096

It worked because you used /f - this turns on the "force" mode to delete read only files also. Adding /s made it recursive delete deleting all files within the folder and within all the sub-directories.

But glad you found a way that worked for you.

Traceyad2032

DEL did NOT work until I added the /s switch (why, I do NOT know).

I tried [del /f chkdsk2024*.log] both within the chkdsk directory and using the absolute path which either one should have worked, but they did NOT.

Just FYI, Tracey

sri369

https://community.acer.com/en/discussion/comment/1330697#Comment_1330697

It could be the case the it failed cos it wasn't able to delete nested directories failing the whole operation.