Menu
▾
▴
1 Attachments
#1426 Cursor issues on Windows 10
I experienced problem on server with Windows 10 Pro x64. In certain places of OS mouse doesn't scroll ie.: in Start Menu, Metro Settings but works in other places like: Windows Explorer, Edge, Control Panel etc.
Additionally mouse cursor doesn't change when moving on border of window (to resize) (screenshot in attachment).
Problem doesn't occur when connecting to server hosted on Windows 7 or Windows XP.
I connect to server from Windows 7 x86.
TightVNC Version Server: 2.7.10 x64
TightVNC Version Client: 2.7.10 x86
Unfortunetly screenshot doesn't show cursor :(
Ignore it instead
Later test confirmed that problem occurs when on server isn't plugged mouse but problem still applies to Windows 10.
Last edit: Bartosz Golemba 2017-09-13
I've got this problem Win10 (x64 pro and home) systems using:
and
Occurred across all windows versions from 1909 to 20H2.
Problem only occurs when VNC Server has the windows mouse cursor set to "invert mode", where the cursor colour changes on a pixel by pixel basis based on the background colour. Doesn't occur with any of the other three cursor modes. To get to this setting:
Settings / Devices / Mouse / Adjust mouse & cursor size / Change pointer colour /
1st, 2nd and 4th cursors don't cause the problem. Third cursor does cause the problem. The attached image shows the problem.
So, disabling the inverted cursor mode stops the problem, but it would be nice if this mode worked, as it tends to make the cursor more noticeable. Win 10 must be dealing with this cursor differently than other cursors, it would need to invert pixels to form the cursor versus overlaying pixels in the non-inverting pixel mode.
Long time TightVNC user, it's a very good app! My appreciation and thanks to all the people involved with this project.
Hi!
Please test 2.8.59 version.
It does not show type 3 cursor correctly but at least it looks like arrow.
See https://sourceforge.net/p/vnc-tight/bugs/1554/ for an update on a similar issue with the VNC cursor display. This one is related to an update to the graphics driver used by the remote Windows PC involved in a Remote Desktop connection. As such, that problem is specific to Remote Desktop connections to the Windows box running the VNC client.