Issue with updating media, Launchbox aborts without recourse

[Rod Wilkins]

When I am updating my media using the wizard, I am given an error prompt (seemingly randomly as it is never on the same file twice) that Launchbox cannot update the media because it is unable to access the destination path. This has worked seamlessly in the past, I have been able to confirm that despite Launchbox’s claim the destination is unreachable, it actually is. I can easily browse to the destination folder and access files within no problem, and copy-paste to and from the destination with windows explorer without error. However, being concerned that perhaps my disk was a problem, I performed a complete surface scan on it and it came up fine with no errors. Below is an example of the error message. I have tried repeatedly to run my updates but it’s always the same result before the wizard can complete, and not always on the same folder/file.

Given I’m sure this is a difficult issue to troubleshoot - is it at least possible that instead of Launchbox simply quitting when this error occurs, that it provides the option to at least RETRY the action? Granted, the disks are connected by USB 3 in an external drive enclosure accessed in my LAN from a mapped network drive, but I have not had other issues accessing data there and they are relatively new 12TB Seagate Ironwolf drives. I noticed this problem since about Launchbox v11.8 however installing an older version and trying again also made no difference.

‌

[Jason Carr]

Interesting, all I can figure is that there are somehow minor network issues that are causing this. I don’t expect that it’s related to any new versions or changes. We generally don’t recommend putting media files over the network, because of performance and other issues like this. We may be able to change this to add a retry button at some point, but since this isn’t a common issue, unfortunately it will probably be a while.

[Rod Wilkins]

Thanks for the update Jason. I’m sure this worked before, which is why it’s frustrating that I see no obvious explanation.

I’ve got a few systems setup sharing the same game files in common, which is why I have it setup on the network in this manner.

I understand that if it’s not a common issue it would be considered lower priority - however even if there no retry button added to this dialog box, perhaps Launchbox can at least make a few attempts on error to automatically retry accessing the file/folder before just giving up, which would be better than nothing. Certainly I don’t understand why Launchbox has to completely close/quit due to this error and not at least just go back to the interface itself.