TightVNC full changelog

Server for Windows: Fixed connection issues in Windows XP that were introduced by the previous version.

Server for Windows: Support for the third-party ExtendedDesktopSize pseudo-encoding has been removed due to incompatibility issues, complexity, and error-proneness. It has been replaced with a similar TightVNC-specific protocol extension, the new DesktopConfiguration pseudo-encoding, which allows users to choose a specific monitor in the viewer when a remote host has multiple monitors connected. Multi-monitor handling will be implemented in next versions of MightyViewer and Remote Ripple.
Server for Windows: Fixed an issue with disabled file transfers in RDP connections.

Server for Windows: Fixed remote desktop updating problems with -sharedisplay and -sharerect options. If the shared area was changed but its size remained the same, update did not happen.
Server and Viewer for Windows: Details in EXE and DLL file properties have been updated. This does not affect functionality in any way (sf bug #1539).

Server and Viewer for Windows: Added support for Unicode clipboard transfers (UTF-8). The latest public version of the standard RFB protocol (3.8) does not support Unicode text, so we implemented this via a new TightVNC protocol extension. This feature will work when supported at both ends of the connection.
Server for Windows: Added support for Echo messages to let viewer software check responsiveness of a server. This may be used for detecting network failures faster when there is no other traffic between Server and Viewer, and will work only with viewers that support and use this new protocol extension. Echo messages will be supported in our latest SDKs but normal TightVNC Viewer does not use them yet.
Server for Windows: Protection against brute-force attacks has been improved. Previously, the server allowed no more than 10 authentication failures per 30 seconds from the same IP address.