VNC Personal Edition 4.2 - known bugs and features
The following are known bugs, features and omissions in version 4.2. You may also wish to check the known bugs, features and omissions in VNC Personal Edition 4.1.
| Date | ID | Platform / Program | Description | Workaround | Status |
|---|---|---|---|---|---|
| 1 Sep 2004 | 9 | Windows server | The Control and Alt keys can become "stuck" when the Send Ctrl-Alt-Del command is used remotely. | Press and release each key a couple of times from a new viewer session, to cause the server to reset the keys' states. | Under consideration |
| 1 Sep 2004 | 10 | Windows viewer | When Fullscreen mode is selected via the F8 menu, the Windows taskbar can remain on top of the VNC viewer window. | Use the system menu (accessible via the icon at the top left
of the VNC viewer window) to enter Fullscreen mode - the bar will
then dissappear after a short delay. or Click on the taskbar, then back on the VNC viewer window - the bar will dissappear. |
Under consideration |
| 19 Apr 2006 | 56 | Windows server and viewer | Sometimes when a file is copied to the clipboard on one end of the VNC connection, it is not available for paste at the other end. | Copy the file to the clipboard again. | Under consideration |
| 26 Apr 2006 | 57 | Windows server | Connection fails with "Connection closed unexpectedly" or "Connection reset by peer", and application event log contains messages of the form "Connections: closed: 192.168.0.1:1047 (state(): ...)". | Enable Terminal Services support on the server computer | Fixed in 4.2.1 |
| 26 Apr 2006 | 58 | Java viewer | Viewer hangs when running in full-colour mode on JREs prior to version 5.0/1.5. | Disable the auto-select and full-colour options before connecting | Fixed in 4.2.1 |
| 27 Apr 2006 | 59 | Windows viewer | Viewer crashes when performing a copy-through operation, i.e. when copying a file from a server, via a viewer & server on an intermediate system, to another viewer. Affects Windows 95/98/Me & NT4 systems. | Copy the file to the intermediate system, then re-copy from there to the destination. | Fixed in 4.2.1 |
| 27 Apr 2006 | 60 | Windows viewer | Copy-through operations fail, i.e. copying a file from a server, via a viewer & server on an intermediate system, to another viewer does not work. | Copy the file to the intermediate system, then re-copy from there to the destination. | Under consideration |
| 12 May 2006 | 61 | Windows server | A security vulnerability was discovered. | Upgrade to fixed version | Fixed in 4.2.3 |
| 12 May 2006 | 63 | Windows server | VNC Server leaks memory rapidly while in use when running on Windows 2000 systems that do not have Terminal Services installed. | Enable Terminal Services support on the server computer | Fixed in 4.2.5 |
| 27 July 2006 | 64 | Windows server | VNC Server leaks memory rapidly while in use when running on Windows XP/2003 systems that do not have the Terminal Services Service running. | Start the Terminal Services Service on the server computer | Fixed in 4.2.6 |
| 27 July 2006 | 65 | Windows server | VNC Server repeatedly logs the error message "unable to switch desktop" in the Application Event Log when running under Windows NT 4. | No workaround | Fixed in 4.2.6 |
| 27 July 2006 | 66 | Windows server | VNC Server may shutdown without warning if certain kinds of screen capture error occur unexpectedly. | No workaround | Fixed in 4.2.6 |
| 27 July 2006 | 67 | Windows viewer | VNC Viewer can hang when used interactively immediately after a large file transfer has been initiated. | Avoid using VNC Viewer while file transfer is in progress | Fixed in 4.2.6 |
| 27 July 2006 | 69 | Java viewer | VNC Viewer reports the session encryption level incorrectly when using the RA2ne security type. | No workaround | Fixed in 4.2.6 |
| 27 July 2006 | 70 | Java viewer | VNC Viewer reports identity hashes that differ from those reported by native VNC Viewers. | No workaround | Fixed in 4.2.6 |
| 27 July 2006 | 71 | VNC servers | VNC Server may crash when handling large, rapidly-changing XOR'd cursors. | Use static or non-XOR'd cursors | Fixed in 4.2.6 |
| 27 July 2006 | 72 | VNC servers | Session disconnection is not logged when sessions fail in certain rare cases. | No workaround | Fixed in 4.2.6 |
| 6 October 2006 | 73 | Windows Server and Viewer | Files are sometimes transferred as zero length. | Transfer the files again | Fixed in 4.2.7 |
| 6 October 2006 | 74 | All file transfer implementations | Single file transfers taking longer than 5 minutes cause the connection to be dropped. | No workaround | Fixed in 4.2.7 |
| 6 October 2006 | 76 | Windows viewer | VNC Viewer does not save the hostname when saving a .vnc file from the Connection Details dialog. | Wait until the connection is established and then save the
.vnc file. or Open the .vnc file in a text editor and change the line that begins Host= as appropriate. |
Fixed in 4.2.7 |
| 6 October 2006 | 77 | All servers | Connections that have data waiting to be sent are not correctly cleaned up. | No workaround. | Fixed in 4.2.7 |
| 4 January 2007 | 79 | Windows server | VNC Service-Mode Server may exit unexpectedly when logging out or switching users under Windows Vista. | No workaround. | Fixed in 4.2.8 |
| 4 January 2007 | 80 | Windows server | VNC Service-Mode Server configuration cannot be accessed under Windows Vista, even by members of the Administrators group. | Right-click on the "Configure VNC Service" menu item and select "Run as administrator". | Fixed in 4.2.8 |
| 4 January 2007 | 81 | Windows viewer | For languages which use Input Method Editors (IME)s for input, the IME switching key-sequence is handled by VNC Viewer, preventing keyboard input from being correctly passed to the server-side IME. | Use the server-side IME interface to activate the desired IME at the server, without affecting the viewer's IME status. | Fixed in 4.2.8 |
| 26 Jul 2007 | 82 | Windows viewer | Changing the encryption for a new connection does not affect that connection. | Disconnect and reconnect. | Fixed in 4.3 |
If you encounter a bug with VNC Personal Edition, please first make sure you are running the latest release. If the bug still exists, please report it via the appropriate support channel.