3.55 Cannot Unlock Secondary Computers

from Stardock Forums

Using KVM mode, not seamless.

Since upgrading all machines involved to 3.55 Build 00101, the program has lost the capability to deliver a Ctrl+Alt+Del or anything else to all secondary computers.   The primary can connect to the secondaries and, if there is an image on the secondary's screen, show it.  However, that's all it can do.  If the secondary machine is locked, the program cannot deliver a Ctrl+Alt+Del.  If the secondary machine is unlocked, it cannot deliver any keystrokes or mouse clicks.

In short, the program is effectively in view-only mode.

All computers are Windows 20H2 and updated through November 2020.

multiplicity
5,090 views 5 replies
Reply #1 from Stardock Forums 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 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.


Using KVM mode, not seamless.

Since upgrading all machines involved to 3.55 Build 00101, the program has lost the capability to deliver a Ctrl+Alt+Del or anything else to all secondary computers.   The primary can connect to the secondaries and, if there is an image on the secondary's screen, show it.  However, that's all it can do.  If the secondary machine is locked, the program cannot deliver a Ctrl+Alt+Del.  If the secondary machine is unlocked, it cannot deliver any keystrokes or mouse clicks.

In short, the program is effectively in view-only mode.

All computers are Windows 20H2 and updated through November 2020.
End of quote

Please see:

https://forums.stardock.com/486104/multiplicity-support-faq#movemousesecondary

Sean Drohan
Stardock Support Manager

 

Sins of a Solar Empire II
Reply #3 from Stardock Forums Top

Quoting sdRohan, reply 2

Hello,

Sorry to hear you are having trouble.


Quoting ,
quoting post

Using KVM mode, not seamless.

Since upgrading all machines involved to 3.55 Build 00101, the program has lost the capability to deliver a Ctrl+Alt+Del or anything else to all secondary computers.   The primary can connect to the secondaries and, if there is an image on the secondary's screen, show it.  However, that's all it can do.  If the secondary machine is locked, the program cannot deliver a Ctrl+Alt+Del.  If the secondary machine is unlocked, it cannot deliver any keystrokes or mouse clicks.

In short, the program is effectively in view-only mode.

All computers are Windows 20H2 and updated through November 2020.



Please see:

https://forums.stardock.com/486104/multiplicity-support-faq#movemousesecondary

Sean Drohan
Stardock Support Manager

 

End of sdRohan's quote

 

For the record, none of that helps. Something completely borked KVM input functionality in 3.55.

Reply #4 from Stardock Forums Top

Quoting fuzzylkd, reply 3


Quoting sdRohan,
reply 2

Hello,

Sorry to hear you are having trouble.






Quoting ,

quoting post


Using KVM mode, not seamless.

Since upgrading all machines involved to 3.55 Build 00101, the program has lost the capability to deliver a Ctrl+Alt+Del or anything else to all secondary computers.   The primary can connect to the secondaries and, if there is an image on the secondary's screen, show it.  However, that's all it can do.  If the secondary machine is locked, the program cannot deliver a Ctrl+Alt+Del.  If the secondary machine is unlocked, it cannot deliver any keystrokes or mouse clicks.

In short, the program is effectively in view-only mode.

All computers are Windows 20H2 and updated through November 2020.



Please see:

https://forums.stardock.com/486104/multiplicity-support-faq#movemousesecondary

Sean Drohan
Stardock Support Manager

 



 

For the record, none of that helps. Something completely borked KVM input functionality in 3.55.

End of fuzzylkd's quote

Can you uninstall Multiplicity on the primary, REBOOT (very important), and then reinstall 3.55.

Does it work then?

I am suspecting a file wasn't replaced correctly.

Reply #5 from Stardock Forums Top

Closing this thread and continuing here:

https://forums.stardock.com/503866

Sean Drohan
Stardock Support Manager