Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


WinSCP crashing on launch.

I have a virtual machine that we upgraded the vmware components on recently. After the upgrade WinSCP is not working.
I uninstalled v5.17.7.10640 and installed the latest version v5.17.10.11087.
I upgraded to the RC version v5.18.3.11229 and that did not help; Event Viewer produces the same error. The only thing that changes is the fault offset
v5.17.7.10640 fault offset is 0x00df0353
v5.17.10.11087 fault offset is 0x00e7032b or 0x00e9032b
v5.18.3.11229 fault offset is 0x009a032b

I have a copy of the machine before the vmware components were upgraded and the application runs fine there. I cannot use that old image and must upgrade the vmware components to address other bugs in the very near future.
This VM is a base image used to create clones used in a virtual desktop setting.

I found other references to the exception code but did not see a resolution. Often a debug version of the application was provided.

Faulting application name: WinSCP.exe, version:, time stamp: 0x00000000

Faulting module name: unknown, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00e9032b
Faulting process id: 0x119c
Faulting application start time: 0x01d72c8b9dac4651
Faulting application path: C:\Program Files (x86)\WinSCP\WinSCP.exe
Faulting module path: unknown
Report Id: 986178e7-368d-4b86-a163-0de452b34dc7
Faulting package full name:
Faulting package-relative application ID: