I know that the behaviour you describe definitely existed many years ago but nowadays you should get an error message like this when a file cannot be found: "Unable to open "<filename>": file does not exist."

Without any further information how you managed to trigger this situation in the current OpenMPT release I cannot do anything about it.

Try loading a file from recent, that was on a USB stick you no longer have plugged in. No error messages result in this specific case.

Thanks, that was the missing information. Unfortunately there seems to be an inconsistency deep inside MFC regarding non-existing files depending on whether they are located on an existing or non-existing drive. I think we should be able to work around that, though.

Fixed in r9351. Due to the size of the workaround (moving around stuff), this will most probably not be backported to OpenMPT 1.27 but instead be fixed in the upcoming OpenMPT 1.28.