Server component is no longer registered as a service
Remote control program TightVNC has been updated to version 2.6.4, which brings to the table only repairs and improvements.The fresh release fixes a problem with the installer for Windows that caused the TightVNC Server component to be registered as a service although the command was disabled through the MSI property “SERVER_REGISTER_AS_SERVICE”.
The developer integrated a number of unspecified improvements touching on the full-screen mode and eliminated the issue with the viewer hanging or even crashing after disconnection. On the same note, some errors in the Tight decoder have been removed.
TightVNC 2.6.4 features an updated Java Viewer (version 2.6.2), which comes with two configurations, one that includes SSH tunneling and one that doesn’t. Furthermore, it includes the possibility to clear history (the function is available in the “Connection” dialog).