New Command Line Options for Error Handling in ImgBurn Suggestions Posted March 19, 2014 Procmon is also showing the failure to read from those files, with the result just saying 'Disconnected'. So I can only assume there's some issue with that source drive - i.e. X: or whatever. What you really need to capture is the point at which the file becomes unreadable (so a log entry showing the file was opened successfully, several successful read operations and then the one where it fails) and then try to find out the actual cause of what I assume is a network file, suddenly becoming unavailable. Solve that issue and you won't need ImgBurn to perform these extra retries etc. I know I'd prefer to have a stable system than a bit of software that may or may not be able to work around those system instabilities. True, true, just thought, the extra measure for being unattended would help someone else in events of power issues, far end computer crashes, etc. I 100% agree with you and I am fairly certain this is due to the SATA controller (it's somewhat specialized so driver updates are rare). Thank you for the extra look though. Take care.