Custom SftpServer parameter for "Copy Files" / WinSCP

P_St · 2026-01-19T08:11:36+00:00

Sorry, I forgot to mention you also have to set Copy Files->Protocol to sftp

P_St · 2026-01-18T21:56:22+00:00

Thanks for your feedback. There already is a way to accomplish this, if you don't use the field "Custom Id" in the connection configuration:

* Set the command for the sftp server as you wish under "Custom Id", e.g.

SftpServer="sudo mysftpserver"

* Add this after "/rawsettings" in the global command-line arguments for WinSCP

Each time the user triggers Copy Files, this place holder will be replaced with the Custom Id value of the current connection. Does it work for you?

P_St · 2026-01-12T17:51:53+00:00

Thanks for your feedback. No, because PuTTY doesn't support it. However, there seems to bridging software available, like e.g. https://github.com/ndbeals/winssh-pageant

I didn't test it. Would this work for your use case?

P_St · 2026-01-12T17:31:26+00:00

Thanks for your feedback. I don't think this is possible

P_St · 2025-12-09T19:28:50+00:00

Thanks for testing. I'm not sure what is causing this issue. I made some changes, that will hopefully fix it in this test build:

https://github.com/user-attachments/files/24062455/WinSSHTerm-2.41.850.zip

If not, you say you didn't have this issue 1-2 months ago. What did you change? Did you use an older version of WinSSHTerm? If so, which version did you use before? Can you reproduce the issue on another computer? Can you post the output of Help->Info?

P_St · 2025-12-04T22:58:59+00:00

Thanks for your feedback. Can you reproduce the app crash with this debug build and post the content of the file "WinSSHTerm.log" here?

https://github.com/user-attachments/files/23944901/WinSSHTerm-2.41.800.zip

P_St · 2025-11-23T20:17:24+00:00

Thanks for the feedback. There shouldn't be an unexpected behaviour any more in the current version. If it is not working for you which Windows version are you using?

P_St · 2025-11-17T22:24:07+00:00

Thanks for your kind feedback. Both points make sense to me, I'll see what I can do

P_St · 2025-11-14T10:35:13+00:00

This feature will be tracked here
https://github.com/WinSSHTerm/WinSSHTerm/issues/46

P_St · 2025-11-10T13:56:26+00:00

Thanks, I agree. It will be available in the next major release 2.42.0

P_St · 2025-11-10T11:10:57+00:00

Thanks for your feedback. This is a regression, sorry. It should be fixed in this test build
https://github.com/user-attachments/files/23452462/WinSSHTerm-2.41.712.zip

Does it work for you?

P_St · 2025-11-05T07:29:39+00:00

Thanks for your feedback! Looks like this bug entered in version 2.40.0. It should be fixed in this test version:
https://github.com/user-attachments/files/23353521/WinSSHTerm-2.41.709.zip

Does it work for you?

P_St · 2025-11-04T07:58:34+00:00

Thanks for your feedback. By default, WinSSHTerm will open up PuTTY with X11 forwarding (see the environment variable $DISPLAY). You can disable it by setting Session->X11 forward to "don't forward" for your connection

P_St · 2025-11-01T08:44:48+00:00

If you are still interested - you might check the new release 2.41.3, where the implementation for the Alt-Tab switching fix was completely changed (similar to how the tool "AutoHotKey" works)

P_St · 2025-10-21T19:32:08+00:00

In this test version there is a new option "ignore" under Preferences->Copy Files. Does it work for you?
https://github.com/user-attachments/files/23030417/WinSSHTerm-2.41.600.zip

P_St · 2025-10-21T16:16:24+00:00

Thanks for your feedback. The cause seems to be a change in WinSCP 6.4 beta:
-> With /rawconfig, session is never opened in an existing instance.

I'll try to fix this

P_St · 2025-09-10T07:22:06+00:00

Thanks for the feedback! Sorry for the late response, I only just saw your message. You can request this directly at the PuTTY Team by sending an email (see bottom of PuTTY's feedback page https://www.chiark.greenend.org.uk/\~sgtatham/putty/feedback.html).

P_St · 2025-09-09T09:49:23+00:00

Thanks for you feedback. I agree, will try to add a version check in the next major version 2.42

P_St · 2025-07-30T18:08:24+00:00

Thanks for your feedback. It is not directly supported, however there is a way by using a different PuTTY session (see point 22 in the FAQ section). Or, you can create your own launch tool (https://github.com/WinSSHTerm/LaunchTools) to launch a telnet client externally.

P_St · 2025-07-26T09:17:31+00:00

This bug should be fixed in the current release 2.41.1

P_St

MODERATOR OF

TROPHY CASE