KVM connection to one Windows 10 machine has greatly offset mouse cursors

I'm using 3.6 kvmpro, on a Windows 10 base machine, controlling several client machines on my LAN. One of these clients, when connected via KVM, has a very badly offset mouse cursor. When I navigate the screen, the place where my mouse shows is a few inches down and to the right of the place where the KVM believes my mouse to be. Unfortunately since the remote cursor is invisible, this makes it impossible to use the remote machine.

I have two clients connected via seamless as well, those are working fine. Two other windows 10 machines are also working fine when connected via KVM. Seems to be only this one machine with the offset issue. The machine in question is a Dell XPS 15 7590 on Windows 10, running an up to date Multiplicity client.

3,937 views 5 replies
Reply #1 Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 Top

As a test, if the PC in question has a mouse plugged into it, unplug it.  If it does not, plug one in. 

Then test.

If that fails, experiment with screen resolution \ scale changes on the remote. 

Sean Drohan
Stardock Product Lifecycle Manager

Reply #3 Top

Alas, no luck, there's no mouse connected and resolution changes make no noteworthy difference.

Reply #4 Top

I have two clients connected via seamless as well, those are working fine. Two other windows 10 machines are also working fine when connected via KVM. Seems to be only this one machine with the offset issue.
End of quote

What else is unique about it? Was it ever working fine but now, all of a sudden, is not?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #5 Top

It worked before just fine. After further testing, seems the offset occurs when the laptop is connected to an external monitor. Without an external monitor, the kvm controls are fine. With a second monitor attached, the issue is actually two-fold:

  1. KVM control of the main screen has significantly offset mouse clicks, and
  2. Switching to the second monitor on the KVM connection shows only a black screen, no interaction.