Multiplicity 2 - No KB on Secondary PC while VMWare Workstation is running on Primary PC

from Stardock Forums

Multiplicity 2 is installed on both the Primary and Secondary PC.  

When VMware Workstation v8.0.4 is running a VM on the primary, all keyboard input is sent to the VM instead of the Secondary PC even though the mouse is on the Secondary PC.  Mouse works, but not the Keyboard.

I've used the previous version of Multiplicy for years with no problems at all.

I've pre-purchased Multiplicity 2. If this issue will not be fixed in the production version, I'll have to go back to Multiplicity version 1.

Thanks,

Matthew

 

multiplicity
3,510 views 6 replies
Reply #1 from Stardock Forums Top

I've escalated this to the QA team.  Thanks for reporting it.

Reply #2 from Stardock Forums Top

I've had similar problem with VNC and RDP. I run RDP and VNC clients on all my machines to connect to servers. I've noticed that I'll often get stuck in a situation where the KB is going to the wrong machine. 

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #3 from Stardock Forums Top

That's weird.  I use VMWare Workstation 8.0.4 as well and do not have this problem.  Did you try to press CTRL-ALT to free the keyboard from the VM?  If your VM isn't running the latest VMWare tools, I can see the keyboard not being released when the mouse is moved out.

 

Reply #4 from Stardock Forums Top

I'm using the same VM I've always used with Multiplicity version 1 without issue.  The only change is Multiplicity version 2. 

Reply #5 from Stardock Forums Top

I have the same issue with HyperV running on Windows Server 2008 SR2. I use a Remote Desktop Connection to login to the VM and if it is the active window then the keyboard sends to the VM instead of the monitor the mouse is on. To work around the problem I need to click on the background on the VM's host before I can type in secondary monitor. I did not have this problem with Multiplicity 1.

Reply #6 from Stardock Forums Top

We have reproduced the problem with VMWare in fullscreen mode and it should be resolved for the next update.