Multiplicity KVM

sticky keyboard buttons issue

Hello,

I am using Stardock multiplicity KVM for a long time,

From time to time (can be 2-3 times a day) I have an issue that looks like the WINKEY is stuck like pushed and the only way to release it is to lock the computer and log in again. 

The issue observed only on the Master computer which other joins. 

I fed to the teeth about this issue and want to resolve it. 

I've checked already the keyboard and it is not the issue. 

18,305 views 6 replies
Reply #1 Top

Hello,
I have forward 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

Hello,

Sorry to hear you are having trouble.

The issue, while rare, seems to happen when you are transitioning while using Ctrl or Alt in a quick fashion.

When this happens, with the Primary having focus, use the Ctrl + Alt keys a few times and it should go away.

Sean Drohan
Stardock Support Manager

Reply #3 Top

Hi, is it a permanent solution? It's coming and going without any reason just in the middle of the work. I don't have any shortcuts or anything like this just using the Multiplicity to control both computers, lock, unlock and drag and drop.

Reply #4 Top

By the way, I am not using any key combination to move to another screen. Only with the mouse movement.

Reply #5 Top

Just try to avoid using any keys the instant you transition from one PC to another is all.

Sean Drohan
Stardock Support Manager

Reply #6 Top

Hello sdRohan, again, I am not using any key combination. It can happen even with the second PC locked but connected. When I am surfing the net or using WORD or whatever. I am typing like I am typing here and when hitting the key that included in combinations like WIN-D to minimize windows or WIN-L to lock the computer. The interesting point is that this happens only with keys, like WIN, CTRL or CAPS.... most of the time with WIN key. I found last days that this happens even when the Multiplicity loaded but the SLAVE pc not configured. Only when I am unloading the Multiplicity on the master PC I am not getting this issue.