* Not an upgrade problem
* Windows 10 Enterprise LTSC
* Using GUI, Commander style
* Error message:
No such file or directory. Error code: 2 Error message from server (en-US): No such file
WinSCP seems to not handle interactions with a file or folder containing special characters, such as accented characters or japanese characters. This happens on my server, a storagebox from Hetzner, to which I am willing to share restricted access with moderators if need be. Other types of servers don't seem to be affected.
While this looks a lot like a server misconfiguration problem from Hetzner's part, everything works fine on FileZilla and even the SFTP client I use on Android, so WinSCP must be doing something wrong.
Attached is the full log of the session with my username and IP redacted.
I have tried changing the UTF-8 encoding session parameters, reinstalling WinSCP, and using the beta version to no avail.
I have also noticed that I am not the first one to have this problem: https://winscp.net/forum/viewtopic.php?t=26653
Although this topic never went anywhere, the user's hostname also ends in your-storagebox.de, so they probably also used a Hetzner storagebox. As asked of this user, I have also included a log with UTF-8 encoding turned off.