Thursday, August 20, 2020

new version 2.12.0 released

Please note:

  • There is now a 64-bit version available. You'll need the 64-bit version if you want to use the 64-bit version of PuTTY. If you want to use KiTTY (or 32-bit PuTTY) then you must use the 32-bit version of WinSSHTerm, as there is no 64-bit version of KiTTY available.
  • When setting or changing a master password, a new key file will now be created and all encrypted data in connections.xml and preferences.xml will be reencrypted with the new key. If you use a master password and are upgrading from an older version, it is recommended to change your master password after upgrading to version 2.12.0


  • Now 64-bit builds available
  • Master Password: Security improvements
  • Master Password: New drop down button in connection password fields to show password in plain text
  • Improved detection of read-only instances
  • Improvements to the Help->Info dialog
  • Improvements detecting running processes like Pageant when running on a multi-user system
  • Added global option to set the X11 Display Location (File->Preferences->Terminal)
  • New PuTTY/KiTTY session "WinSSHTerm_ScriptRunner", which is used exclusively by the Script Runner
  • Bug Fix: unhandled exception in the DockPanel Suite
  • Bug fix: Quick-Connect throws an error when upgrading from older version
  • Bug fix: Password field for Jump Server in Quick-Connect dialog was shown in plain text



  1. There should be big bold warning about Kitty and 64-bit. I have just reset all my color schemas with Putty and almost everything went to hell.

    Bad. Next time, please emphasize that this is pretty major upgrade!

    1. You're the only one who reported such problems when upgrading until now. This might be the case if you used the portable version of KiTTY, which is not supported.
      I agree with the warning, I'm working on it

  2. Hi.

    Thanks for your work.

    The new behavior added in version 2.10.0: "Cluster Mode: Tabs don't close so that the session can be reconnected"
    Could be optional?
    I used to end commands with "&& exit", so correct executions close the tab, but failed ones remaing the tab open.


    1. Hi, there will be an option to restore the old behaviour in the next release

  3. Hi!
    Can I create dynamic port forwarding, e.g. -D?
    FAQ says only about -L and -R...
    Thank you!

    1. I will answer by myself: yes, at least with putty winsshterm support -D key.

  4. Hi! Great work!
    But is not possibile to start a new ssh connection from command line?
    I mean something like >WinSSHTerm.exe -ssh user@host?