Hi Martin,
I've attached a screenshot of the last log we have from WINSCP at 4:34AM MT on February 17th. It was a normal "All channels closed" message. The next time our internal job ran and called WINSCP there is no WINSCP log and there is no Windows level log showing anything related to WINSCP (error code or otherwise). Our internal job did not have any enhanced logging either so it responded as if WINSCP ran but found no files to move (we know that is not true because there was a pileup of files found 4 days later and they had not been moved).
As for adding the command and getting you logs we are not sure how that will help as the issue is not currently occurring and we are not able to reproduce the issue.
I'm guessing you have never seen this type of behavior from WINSCP.

@rprince: I do not think that the Program file can cause any problems with WinSCP.
Do you check WinSCP exit code in your internal application? What is it? Do you check Windows error code when starting WinSCP?
Try adding /applog=C:\some\path\winscp.log to WinSCP command-line (in addition to /log). And post the logs.

Hi Martin, I work with @dranaware, who opened this case, and wanted to try and help provide more context on the issue we saw. WinSCP is being used by an internal application programmatically. Our exe calls WinSCP and tells it to move files from one location to another on a regular cadence. This was setup in November 2024 and was working just fine until February 17th. On February 17th at 4:34AM MT the logs from WinSCP just stopped. It seems it ran successfully and would/should have been ready to run the next time it was called. However for the next 4 days (until it was noticed) WinSCP never ran when called, never logged any details, and never showed any error message. The support team finally noticed it had not been running and, as a workaround, set it up to run from the server D drive rather than the C drive where it had previously been running. This worked and WinSCP has been running just fine ever since. What we are trying to understand, and find the root cause of, is why WinSCP just stopped responding/running on February 17th until it was noticed and required manual intervention to get it going again. Another thing that was noticed, 12 minutes after the last log entry from WinSCP, on that same server, a file simply called Program with no extension, was created in the C drive. This caused the server itself to complain as many applications require the C:\Program Files\... location to be available and having something called C:\Program could disturb those processes. We have dealt with the rogue file and removed it. We also experimented in our non-production environment trying to reproduce that scenario to see if a file named Program sitting in C:\ would cause an issue for WinSCP. In the non-prod environment there was no issue, WinSCP was called and ran as expected and moved our files. So it appears this Program file is just a red-herring but wanted to mention it as that is the only other strange thing we see occurring at or around the same time that WinSCP stopped responding. Our internal server team has analyzed the server, we have had Microsoft do a full diagnostic, we had the DB2 DBAs and their vendor do an analysis (the Program file had details related to DB2 stats inside it), we had our DNS team investigate any possible DNS issues and all have turned up empty in terms of a root cause. You are our last resort. Have you ever heard of or seen anything like this with WinSCP?

WINSCP tool on Feb-17 to Feb -21, 2025 not downloading files from Blob location and before that date it's working as expected. We have no log details found in the WINSCP logs.

What do you mean by "showing as not working"? Does WinSCP window hang somehow?

Hi Team,
We are using WinSCP tool to download files from blob location to server but after some days it's showing as not working. We have no logs details found once stop the WinSCP. Due to that we have facing major issues in our application.
We are using WinSCP 6.3.5 version on our system.
Please provide us some findings from your end for this kind of issues.