Update:
The server half of this issue is apparently because Windows 10 doesn't provide a mouse cursor if no physical mouse is attached (somehow Remote Desktop is an exception to this though). Turning on the MouseKeys accessibility feature seems to be a workaround.
Still not sure why the client ...
Search found 2 matches
- 2025-04-04 17:12
- Forum: 1.4.3.x
- Topic: No remote or local cursor
- Replies: 1
- Views: 41221
- 2025-03-19 01:00
- Forum: 1.4.3.x
- Topic: No remote or local cursor
- Replies: 1
- Views: 41221
No remote or local cursor
Using UltraVNC 1.4.3.6 server on a headless Windows 10 Pro box, with UltraVNC 1.4.3.6 client on a Windows 11 Home box.
For some reason I only get a dot for a cursor, regardless of which cursor mode I choose in the client.
Any idea what the cause might be?
For some reason I only get a dot for a cursor, regardless of which cursor mode I choose in the client.
Any idea what the cause might be?