need help with i/o error, how to skip the problem file? in ImgBurn Support Posted November 13, 2021 hello i'm here after ruining several disks/dvd i'm getting this random error about a random file for example: "W 03:45:52 Failed to read from file: 'C:\.......1.jpg' but upon try to write that file again on another disk the error is gone the error says "cannot read file ... due to an i/o device error" the options are always "retry" and "cancel" retry will return same error after a while, for same file while the device seems stuck on it cancel will ask me if it can close session and regardless what i choose in that regard will stop burning so i have some disks ruined with only 400mb good on them and others more luckier with more data and as i said upon retry to burn again the remaining files i may or may not get same error but not for same file is there a way to skip such file and keep on burning the rest hopefully properly ? i believe the main culprit here is ms with their crappy x64 implementations for win 7 sp1 and win 10 because i rarely had any errors when i was using x32 systems and likely no sp, lol anyway a quick help could save my current disk wich is stuck at 44% right now... if not lucky to get fast answer at least the future disks may be saved so i'm still hopeful thank you for any help Peki
need help with i/o error, how to skip the problem file?
in ImgBurn Support
Posted
hello
i'm here after ruining several disks/dvd i'm getting this random error about a random file for example:
"W 03:45:52 Failed to read from file: 'C:\.......1.jpg' but upon try to write that file again on another disk the error is gone
the error says "cannot read file ... due to an i/o device error"
the options are always "retry" and "cancel"
retry will return same error after a while, for same file while the device seems stuck on it
cancel will ask me if it can close session and regardless what i choose in that regard will stop burning
so i have some disks ruined with only 400mb good on them and others more luckier with more data
and as i said upon retry to burn again the remaining files i may or may not get same error but not for same file
is there a way to skip such file and keep on burning the rest hopefully properly ?
i believe the main culprit here is ms with their crappy x64 implementations for win 7 sp1 and win 10
because i rarely had any errors when i was using x32 systems and likely no sp, lol
anyway a quick help could save my current disk wich is stuck at 44% right now...
if not lucky to get fast answer at least the future disks may be saved
so i'm still hopeful
thank you for any help
Peki