The task is configured to run with the highest privileges and as a specific user account. The command runs fine when I log in as that user account and run the task manually. (The user account is also a domain admin). I have also selected the "Run whether user is logged in or not" option. The "Start in (optional)" field is also set to the WinScp directory (C:\Program Files (x86)\WinSCP).
However, when I select "Run" to trigger the scheduled task to execute, it seems to run indefinitely.
From viewing the Task Manager, I can see the winscp.com and winscp.exe processes start up, but they never end (until I manually end the task or kill the processes).
For sanity's sake, I tried modifying the scheduled task to something simple:
winscp.com /log=foo.log /command "exit"
where the arguments are specified in the "Add arguments (optional)" dialog and even this seems to hang when run as a scheduled task. But this runs fine when I execute it from the Windows command line.
One thing is that the Windows Task Scheduler service is configured to run as the Local System, but I assumed that the specified user account would override that. Also, no log file is generated, but since I am not even connecting to a host, that's somewhat expected.
Again, I apologize in advance if I've missed something obvious, but was wondering if anyone else had run into this. I am running v5.1.4.