Forum » Support and Bug Reports »

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.

Options
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)

Options

Topic review

vipeweb

Hello, I managed to create a functional patch that fixed WinSCP 6.7 and got it working again. Although I am a developer, I am not an expert in C or C++, so I sought assistance from "Claude Mythos."

I am sharing the solution I found; perhaps your team can implement a fix so that this issue does not affect other users.

check Attachment
mholmes

@vipeweb which error are you seeing?
martin

@mholmes: Thanks. Please let me know once you have more tests done.

@vipeweb: Thanks. As above, can you please try to find out, what is the latest release that still works?
vipeweb

Wine stopped working

Hello, I’m experiencing the same issue here.

I also tried older versions, such as WinSCP-6.6.3.RC-Portable, but the problem persists.

tried Wine/Soda
with bottles.
mholmes

6.6.1 beta gives me the same problem as the current release: GUI shows up OK, but when I try to connect to a server, it freezes.

6.5.6 gives me the date problem I first encountered with this error on startup:

Invalid argument to time encode [1936:1:1.0]
followed by
Invalid argument to time encode [5032:1:1.0]
That's a different error; subsequent versions do start up, but freeze when trying to connect to a server (and in the debug version, show endless popup error messages, as reported above).

6.3.8 and 6.3.6 both give me:

Invalid argument to date encode [2026-31701-30407]

So it looks like the date problem goes back further than I thought; it's possible I hadn't updated WinSCP for a while. I have to work now, but I'll keep testing when I get a moment.
mholmes

That's certainly true, but the question is why this particular app suddenly started failing when it's been working fine for years. One of the possibilities is that some setting in the underlying Delphi IDE or the compiler changed its default, with no effect on the app from the point of view of Windows, and simply changing it back would enable Wine users to keep using it with no cost to anyone else. But if the change is significant and useful for end-users, then sacrificing the Wine audience may be worth it. I don't know how many Wine users there are, but I bet it's quite a lot, since there will have been a lot of people like me who were once Windows users and migrated over to Linux bringing a few favourite Windows apps with them via Wine. I have a soft spot for WinSCP too because it's a Delphi app -- I recognize lots of VCL controls and layout features in the GUI that remind me of my own Delphi apps -- and I know that Delphi apps have over the years been very robust on Wine, because they tend to have few external dependencies.

But of course there are perfectly good Linux-native alternatives such as FileZilla, and most of the Linux file managers will now happily mount remote drives over ssh and show dual-panel views.
Guest

From your posts, it feels like newer WinSCP hit problems with not yet implemented stuff in Wine. It can take many years for Wine to implement stuff (if ever as there's stuff from the 90s that still doesn't work today) all depending on how it goes.
mholmes

Just tried the debug portable version, and it starts OK, but when I try to log into a server, I get a cascade of endless "Abnormal program termination" messages and have to kill it from the command line. This is the startup CLI: 

wine WinSCP.exe

0024:err:environ:init_peb starting L"Z:\\home\\[user]\\apps\\WinSCP\\WinSCP.exe" in experimental wow64 mode

0024:err:listview:LISTVIEW_WindowProc unknown msg 109d, wp 0, lp 0

0024:err:listview:LISTVIEW_WindowProc unknown msg 10bd, wp 1822e38, lp 12dd94

0024:err:listview:LISTVIEW_WindowProc unknown msg 109d, wp 0, lp 0

0024:err:listview:LISTVIEW_WindowProc unknown msg 10bd, wp 1822e38, lp 12dd94

0024:err:listview:LISTVIEW_WindowProc unknown msg 109d, wp 0, lp 0

0024:err:listview:LISTVIEW_WindowProc unknown msg 10bd, wp 1822e38, lp 12deb4

0024:err:listview:LISTVIEW_WindowProc unknown msg 109d, wp 0, lp 0

0024:err:listview:LISTVIEW_WindowProc unknown msg 10bd, wp 1822e38, lp 12deb4
mholmes

Oh, forgot to mention: I also tried the portable version, but no joy.

I was a Delphi programmer myself, and I still miss it, but moved to Linux many years ago. My own Delphi apps dating back to the 90s and early 2000s still work under Wine, and I can maintain them using ancient VMs -- I last released an update for one of them in 2020, but the audience for them now is almost entirely Linux users, I think, because they're not signed or delivered through the Windows app store.
mholmes

The version where the problem first surfaced for me was 6.5.7, 2026-09-09. When I installed that version, the app would fail to start with a mysterious date-parsing error of some kind. I waited for the next release, hoping that would fix it, and then I got a much more detailed error message (I was going to put that in my post, but the forum software said I shouldn't). I then updated my Wine to the latest stable 11.0, but that didn't solve the problem; then I updated my Ubuntu OS from 24.04 to 26.04, which bumped Wine back down to version 10.0, but it still didn't work. So I can confirm that the 6.5.7 failed on Ubuntu 24.04 with Wine 9.0 and 11.0, and the latest one fails on Ubuntu 24.04 with Wine 11.0 and on 26.04 with Wine 10.0.

I'll try the debug version and report back...
martin

Re: Linux/Wine suddenly stopped working

I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
mholmes

Definitely not a Wine problem

This is definitely not caused by changes in Wine; the app was working fine, I did an update to WinSCP (with no change to Wine), and it stopped working. Other Wine apps continue to work. I presume an older version could be installed and would work, but given the current security climate I'm not comfortable installing older versions of Windows apps.

If WinSCP development has taken a turn that makes it incompatible with Wine, but there enough benefits that losing the Wine user base is worth it, then I'm fine with that; I'll just move to FileZilla and the command line. If, on the other hand, some random Delphi update has changed a background setting that has no bearing on the functionality of the app but happens to break Wine compatibility, I think there are probably lost of long-time users like me who would appreciate getting it back!

Cheers,
Martin
Guest

Does an older WinSCP version still work? I don't see this directly specified. You only stated since the August update. Can't infer that means was tested.

The thing about Wine, and I say this although you used it 12 years with WinSCP, its a beast and newer software changes can find problems in Wine with either stubs not done or just stuff that doesn't yet exist in Wine. This is the downside to Wine, always has been, always will be for as long as Wine has to keep changing to newer Windows/software changes.

Wine also has another problem where the OS, driver, updates pulled etc can cause it to break. This is something many people don't get. The software to use with it can look broken but not be.

At the same time, I don't know if the log snippet you posted is a red herring or not. Wine errors can extremely be red herrings as logs are complicated and really require vast log and Wine debug knowledge.

Ideally, I would say that if an older WinSCP version works, use that. If its no longer working then you have a Wine running problem, not a WinSCP one.
mholmes

Linux/Wine suddenly stopped working

I've been using WinSCP under Wine on Linux for maybe 12 years now -- I used it back when I used to be a Windows user and I've always liked it. But since the August update it's completely stopped working. I just installed the latest version, and when I start it, I get the errors below. Does anyone know what changed, and whether there might be a workaround for this? 

Unhandled exception: 0x0eedfade in wow64 32-bit code (0x7b662597).

Register dump:

 CS:0023 SS:002b DS:002b ES:002b FS:006b GS:0063

 EIP:7b662597 ESP:0191f354 EBP:0191f3a8 EFLAGS:00200246(   - --  I  Z- -P- )

 EAX:0191f354 EBX:00000000 ECX:00000018 EDX:0191f3e0

 ESI:011f862c EDI:0191f9ec

Stack dump:

0x0191f354:  0eedfade 00000001 00000000 7b662597

0x0191f364:  00000007 00000000 0399a120 00000000

0x0191f374:  00000000 00000000 00000000 00000000

0x0191f384:  009ea84c 038ee070 0191f3bc 0056f6f2

0x0191f394:  0191f3f8 0056f70d 0191f3bc 00000002

0x0191f3a4:  0191f9ec 0191f518 01063da2 0eedfade

Backtrace:

=>0 0x7b662597 RaiseException+0x42(code=<is not available>, flags=<is not available>, count=<is not available>, args=<is not available>) [/usr/src/wine-9.0~repack-4build3/dlls/kernelbase/debug.c:378] in kernelbase (0x0191f3a8)

  1 0x01063da2 in winscp (+0xc63da2) (0x0191f518)

0x7b662597 RaiseException+0x42 [/usr/src/wine-9.0~repack-4build3/dlls/kernelbase/debug.c:378] in kernelbase: mov -0x04(%ebp), %ebx

Unable to access file '/usr/src/wine-9.0~repack-4build3/dlls/kernelbase/debug.c'

Modules:

Module  Address                 Debug info      Name (127 modules)

PE        400000- 1811000       Export          winscp

ELF     5683e000-56843000       Deferred        <wine-loader>

PE-Wine 76670000-7667f000       Deferred        psapi

PE-Wine 76690000-766b8000       Deferred        wtsapi32

PE-Wine 766d0000-767bc000       Deferred        msctf

PE-Wine 767d0000-76850000       Deferred        netapi32

PE-Wine 76860000-7689b000       Deferred        msv1_0

PE-Wine 768b0000-768d9000       Deferred        kerberos

PE-Wine 768f0000-7690e000       Deferred        nsi


All help appreciated,
Martin

Documentation

Support

Associations

Follow Us