I see WinSCP holds opened handles on local drives even though it never accessed them.
This is the scenario I ran (it was WinSCP first run on this machine by the way):
- Add a new FTP site, configure it fully to transfer files to a directory in the drive "I".
- Save those settings for the site and connect to it.
- Start some transfers from it to the default directory I specified in the drive "I".
Later on I wanted to safely eject an USB memory drive with the letter "E" however Windows didn't allow me to because some application was using it. Since I didn't even use the drive I looked for opened handles and found WinSCP holding one.
After the transfers finished, closing the app freed the handle and allowed me to safely eject the other drive (note, both drives were connected to a hub connected to an USB port on the machine, not directly to it in case that's relevant).
How come WinSCP had a handle for that drive even though I never accessed it through it? Could it be fixed for the next release? Ideally, only keep handles open for the duration they're needed and only when needed.