Start a new topic

[Putty] Existing Saved Sessions Support

Hi Stefan,

Thank you for your great product.

RoyalTS already has the support of custom Putty executable. That is awesome because RoyalTS users can use latest versions of Putty as soon as possible.

RoyalTS generates custom Putty session (TEMP_SESSION_*) and runs Putty with it:

putty.exe -load "TEMP_SESSION_67613" -pw "lystor"

But the problem is that the RoyalTS does not support all options of Putty. Also Putty adds new options with new releases or changes existing.

Please add to RoyalTS the possibility to input the name of existing saved Putty session in properties of "Terminal Connection". RoyalTS should set it in Putty args with ssh hostname and username.


putty.exe -load SESSION_NAME -ssh localhost -l lystor -pw lystor

This will give users RoyalTS the ability to use all the functionality of Putty and existing Putty sessions with tons of tweaks.

Thank you



Hi Stefan,


I am not able to reproduce the bug in VM with clean Windows 10 (version 1903).

It exists on my primary PC with Windows 10 Enterprise LTSC (version 1809).

Sorry, I can't create the video on that PC but I can send you any additional required information (process list for example, etc).

That's strange. What happens if you go back to the latest 5.0 release ( Do you then still see the issue? Can you test this with the built in PUTTY and external PUTTY?

I'm trying to figure out if this is something unique to your machine or if this is related to the beta version.




The issue exists only in connection type "Existing Putty Session" with both versions of Putty (built-in 0.71 and external 0.72).

The session "profile1" were created with built-in Putty 0.71 and has default settings.


Connection type "SSH connection" doesn't have this bug (both versions of Putty works fine).


Command lines:    

"C:\Users\nikolay.ul\AppData\Local\Temp\Royal TS V5\Plugins\107df0a3-eab8-40ee-87f2-cc8a310f9269\RoyalTS_PuTTY64.exe"

-load "profile1" -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk" 


"C:\Users\nikolay.ul\AppData\Local\Temp\Royal TS V5\Plugins\107df0a3-eab8-40ee-87f2-cc8a310f9269\RoyalTS_PuTTY64.exe"

-load "TEMP_SESSION_45482" -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk"


"C:\Program Files\Putty\PUTTY.EXE" 

-load "profile1" -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk"


"C:\Program Files\Putty\PUTTY.EXE" 

-load "TEMP_SESSION_69167" -l root -i "D:\perforce\deploy\ansible\roles\openssh\key-private\files\id_rsa_root.ppk"


It seems like RoyalTS uses invalid regexp to search for Putty process if "Existing Putty Session" used.

EDIT: built-in Putty version is also 0.72, not 0.71

Can you post a screenshot of the session window?

I have attached screenshots and HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\profile1

(14.7 KB)
(24.9 KB)
(31.6 KB)
(51.8 KB)


I imported your reg file, setup the connection the way you did and also tried with the 0.71, 0.72, 0.73 and it's working fine on 3 different machines.

I can see that the text " - PuTTY" (without the double-quotes) is not in the window. In the latest beta (build 11010) there's a Plugin Option to specify a custom window title match. The problem I see in your screenshot is that the window title is basically the username/prompt which may be different. You can set the Window Title in PuTTY (in the registry WinTitle). Maybe setting that to " - PuTTY" fixes the issue.

I really have no idea why the window title is different in your case.

NoRemoteWinTitle: 0 (default) -> 1 fixes the issue with "Existing Putty Session" connection type.

It is set to 1 in "SSH connection" type.

May be it is better to validate the value of NoRemoteWinTitle and display a warning to user before connection?

Login or Signup to post a comment