WinSCP 5.1.4 crashing at the end of download.

Never had a problem at all until 5.1.4 which seems to be crashing at the end of downloading.

Level Date and Time Source Event ID Task Category
Error 26/03/13 2:52:14 AM Application Error 1000 (100) "Faulting application name: WinSCP.exe, version: 5.1.4.3020, time stamp: 0x00000000
Faulting module name: WinSCP.exe, version: 5.1.4.3020, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0038d34d
Faulting process id: 0xdd0
Faulting application start time: 0x01ce29ea86f4f69e
Faulting application path: C:\Program Files (x86)\WinSCP\WinSCP.exe
Faulting module path: C:\Program Files (x86)\WinSCP\WinSCP.exe
Report Id: b0a78d86-95e1-11e2-bf58-bcaec576ccd2
Faulting package full name:
Faulting package-relative application ID: "

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

Email sent.

Hi. I have a similar issue.
I am using 5.1.3 in our production environment.
Approximately every month WinSCP.exe faults and refuses to work via the .NET library or by running the exe.
When I bring up a new login for the production server (new RDP session) the exe works correctly.
So I have to start our software on a new RDP session which causes unwanted downtime.

Following is the dump from event viewer.
Would really appreciate a fix for this one..


Faulting application name: WinSCP.exe, version: 5.1.3.2881, time stamp: 0x00000000
Faulting module name: WinSCP.exe, version: 5.1.3.2881, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x004ae79a
Faulting process id: 0x1cd0
Faulting application start time: 0x01ce6630f7bee7f0
Faulting application path: D:\Apps\WCFSelfHosted\WinSCP.exe
Faulting module path: D:\Apps\WCFSelfHosted\WinSCP.exe
Report Id: 35a0801d-d224-11e2-a835-005056a3762d

jhirst wrote:

Hi. I have a similar issue.
I am using 5.1.3 in our production environment.
Approximately every month WinSCP.exe faults and refuses to work via the .NET library or by running the exe.
When I bring up a new login for the production server (new RDP session) the exe works correctly.
So I have to start our software on a new RDP session which causes unwanted downtime.

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

Hi Prikryl,
I suspected below issue was similar to what i had experiencing. It happened approx. 20-30 days. Though, my method is different since I didn't use the .NET library but using scripting command by triggering winscp.com via System.Diagnostics.Process; When Winscp.exe faulted, I need to log off the current user login and re-login again or starting new RDP session.

Appreciate if you could also sent another debug version of WinSCP for me to investigate further about the issue.

Great Thanks!

jhirst wrote:

Hi. I have a similar issue.
I am using 5.1.3 in our production environment.
Approximately every month WinSCP.exe faults and refuses to work via the .NET library or by running the exe.
When I bring up a new login for the production server (new RDP session) the exe works correctly.
So I have to start our software on a new RDP session which causes unwanted downtime.

Following is the dump from event viewer.
Would really appreciate a fix for this one..


Faulting application name: WinSCP.exe, version: 5.1.3.2881, time stamp: 0x00000000
Faulting module name: WinSCP.exe, version: 5.1.3.2881, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x004ae79a
Faulting process id: 0x1cd0
Faulting application start time: 0x01ce6630f7bee7f0
Faulting application path: D:\Apps\WCFSelfHosted\WinSCP.exe
Faulting module path: D:\Apps\WCFSelfHosted\WinSCP.exe
Report Id: 35a0801d-d224-11e2-a835-005056a3762d

excalibur wrote:

I suspected below issue was similar to what i had experiencing. It happened approx. 20-30 days. Though, my method is different since I didn't use the .NET library but using scripting command by triggering winscp.com via System.Diagnostics.Process; When Winscp.exe faulted, I need to log off the current user login and re-login again or starting new RDP session.

Appreciate if you could also sent another debug version of WinSCP for me to investigate further about the issue.

Thanks for your report.
I have sent you an email with a dev version of WinSCP to address you have used to register on this forum.

Martin has suggested using a development version and this has fixed the issue. thanks!