If there are no WinSCP processes left behind, there can hardly be any WinSCP leak.

The operating system takes care of releasing all resources when a process closes, no matter if there are any bugs/leaks are in the process software. (Though obviously Windows 2008 is old itself)

There's only one know exception, which resulted in resource leak in very old version of WinSCP:
https://winscp.net/tracker/996

martin wrote:

Do you see orphan WinSCP processes on the machine?

No. But if I run the process every minute - by the end of the day, my SQL Server applications start getting various connection errors.

Do you see orphan WinSCP processes on the machine?

I have a Win 2008 R2 server that runs winscp by command line every minute to xfer over any files it finds. The issue is that by the end of the day, other programs start exhibiting connection failures. It only happens since I created the winscp script.

1. Is there any way to diagnose if winscp has a connection leak?

2. Is there a better way of "monitoring" an FTP folder for files and copy them over as they come in?