Closed svennp closed 2 years ago
That's... interesting. That implies that the file exists, but doesn't have a valid "LastWriteTime". I didn't think that was possible. I can add an extra catch there, but I'd suggest running a chkdsk to verify your filesystem indexes.
v1.0.15 is available which will handle the exception, and tell you which file it had problems with, which may help you decide which drive to scan for errors.
I just testet v1.0.15 and it now works.
The erroring files were some old avi files that do not have a modified timestamp in windows but the created timestamp still exist. The files are playable and it seems all that had happened were the lost modified timestamp on the files.
I'm getting this error when running it now. It scanned a bunch of episodes at first, then it just stopped. now i get this error when starting the program.
running on windows server 2019