Error when using WinSCP with privatekey (when WinSCP is set to Dutch)

Hello, I'm a developer working to incorporate the support of WinSCP with our product, and we've just received a bug report from a user which we've been able to replicate.

Essentially, when WinSCP's language is set to dutch, it returns an error when we're trying launch it through our software (this does not present itself when WinSCP's language is set to English).

We're sending the parameters configured in the required way described, but is it possible that the parameter names are changed with the language of the software?

I have attached a screenshot of the error.

Please attach a full session log file showing the problem (using the latest version of WinSCP).

A log file from English version for comparison might be helpful too.

I've attached both session logs, I've renamed them so that their language is apparent.

Thanks for the logs.

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

I've registered and sent an email with the link.

I downloaded the Debug WinSCIP, it did not have any other language besides English.
So I followed the steps (Starting with the *Get More* button) and downloaded the Dutch language, proceeded to extract it at the same location as the .exe,
and then I could see the Dutch selection. However when I attempted to select it, it gave me an error message, and restarting WinSCP does not fix this.
(To be clear, the language is not changing, so I can’t test my problem).

I've sent an email response with the file requested from the latest Debug WinSCP I was sent. Unfortunately the issue did not replicate with that specific software, but I'm now awaiting response on what we can do next to fix this.

After receiving yet another Debug WinSCP, I was able to replicate the issue this time, and I've sent the file created by the software. I hope this will help!

Again, sent another trace file with the latest version I was provided.

Rinse and repeat! Send another trace from another debug version I received.

I've sent another email but just in case it's better I send it here, from what I understand we seem unsure what is happening still.

I was recommended to look into adding a delay to the sending of command lines (something we had already tested and found ineffective, unfortunately) and that it might be a Firewall issue, something that we've also ruled out.

Considering how the error only happens in german (and likely some other languages, but not english) and we're simply sending command lines that work perfectly in english, I was wondering what the next steps would be, what we could do or try to fix this or whatnot.

Well we eventually got to a fix, so you can consider this closed!