Fail to launch when last drive used is no longer connected

Select a network drive in the left pane. Close WinSCP. Disconnect the network drive. Launch WinSCP – it appears to fail to launch – actually probably waiting "a long time" to poke the now non-existent network drive.

Would be cool to see a much faster timeout applied here.

So does it fail to launch? Or does it wait too long?

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.