#1446 Saved session bug

[David Tweed]

I am having the same problem reported back in 2014. The save session configuration file when selected returns an error message of "Error in TightVNC Viewer: Connection parameters (host, port, socket, gates) is empty. But when I open the file in Notepad, those parameters are indeed present. I am using the 64 bit version, 2.8.11 so am surprised this problem is hanging around. I did not have this problem with the 32 bit version....

[Daniel Liuzzi]

Late to the party, but I encountered this myself today in v.2.8.59. It's caused by a bad registry key. Check https://superuser.com/a/1511286/18964 for a fix.

[Anton]

Hi!
I don't really understand what are the two keys.
The installer creates VncViewer.Config in HKEY_CLASSES_ROOT.vnc
also it becames
HKEY_LOCAL_MACHINE\SOFTWARE\Classes.vnc
And a command line in HKEY_CLASSES_ROOT\Viewer.Config\shell\open\command
and it converts to
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\VncViewer.Config\shell\open\command
What key is missed?

[Daniel Liuzzi]

I see my SU edit is not approved yet so it's not visible. I'll just paste it here:

What solved the problem for me was fixing these registry keys:

• HKEY_CURRENT_USER\SOFTWARE\Classes\Applications\tvnviewer.exe\shell\open\command
• HKEY_CURRENT_USER\SOFTWARE\Classes\vnc_auto_file\shell\open\command

Your path to the viewer may be different. The trick for me was adding the -optionsfile.
It needs to be "C:\Program Files\TightVNC\tvnviewer.exe" "-optionsfile=%1"

[Anton]

could you look to HKCR\.vnc
and
HKCU(HKLM)\SOFTWARE\Classes\.vnc ?

[Daniel Liuzzi]

[HKEY_CLASSES_ROOT\.vnc]
@="vnc_auto_file"

[HKEY_CURRENT_USER\SOFTWARE\Classes\.vnc]
@="vnc_auto_file"

I don't have a HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.vnc key.

[Anton]

TightVNC sets [HKEY_CLASSES_ROOT\.vnc] to "VncViewer.Config"
UltraVNC replaces it with "vnc_auto_file"

[Daniel Liuzzi]

I have "vnc_auto_file" and only have TightVNC in my machine.

I never installed UltraVNC.

[David Tweed]

The changing of the Hkey registry entry to "VncViewer.Config" fixed my problem. I don't know why a reinstall of Tight VNC didn't overwrite that entry.