After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080

Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031

Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078

Development: UltraVNC development is always here... Any help is welcome.

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

No remote or local cursor

Post Reply
HunterZ
Posts: 3
Joined: 2009-05-15 15:56

No remote or local cursor

Post by HunterZ »

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?
HunterZ
Posts: 3
Joined: 2009-05-15 15:56

Re: No remote or local cursor

Post by HunterZ »

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 only shows a dot in all modes.
Post Reply