Can't reproduce on linux.
The bug originally happened on Windows when the file to be loaded was located on a drive that was no longer available (external HDD).
*** Bug 1235 has been marked as a duplicate of this bug. ***
I can't reproduce this on Win10 anymore - no matter whether I rename the file in question, unplug the drive or delete the file.