Multiplicity 3.57 Release Issue Report Thread

Hello, my Send Audio is glitchy. It will randomly cut out and revert back to original PC's speakers. Toggling the 'Send Audio when Primary PC is Online' option in systray worked a few times, then it stopped. Changing the handshake passkey worked a few times, then it stopped. Unloading and reloading Multiplicity worked a few times, then it stopped. Now it takes a full reboot to regain functionality.

Thank you.

Successfully updated karma reason!

I'm having Cap Lock issues when using remote desktop on a secondary machine. Regardless of the cap lock toggled state, the characters displayed are all lower case. I have to hit the shift key while running connected to the remote desktop session.

This does not happen all the time. It appears to happen if I'm connected to a remote desktop session for an extended time and do not use it.

Successfully updated karma reason!

Quoting spammail10,

reply 27

This does not happen all the time. It appears to happen if I'm connected to a remote desktop session for an extended time and do not use it.

That is going to be a challenge to test. Can you confirm it NEVER happens when you don't use RDP?

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

It only happens when I use RDP.

My primary is Win11 Ver 21H2 Build 22000.613

My secondary is Win 10 Ver 21H2 Build 19044.1645

RDP is connecting from on the secondary to Win Server 2016 v1607 Build 14383.3326 and Win Server 2012 R2 v6.3 build 9600. There are likely other versions also but all Win Server.

Successfully updated karma reason!

Quoting spammail10,

reply 29

It only happens when I use RDP.

My primary is Win11 Ver 21H2 Build 22000.613

My secondary is Win 10 Ver 21H2 Build 19044.1645

RDP is connecting from on the secondary to Win Server 2016 v1607 Build 14383.3326 and Win Server 2012 R2 v6.3 build 9600. There are likely other versions also but all Win Server.

Well RDP does keyboard capture as well so I have little doubt it is the reason for the issue. What would surprise me, however, is if it still happens if RDP does not have focus - that when it is minimized and other apps have focus on the Secondary, that it still happens.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

So, during one of my tests, RDP lost focus and it once RDP regained focus, the caps/num lock keys would not work. I signed out, closed RDP and signed back into RDP. The Cap/Num lock keys still do not work correctly.

Successfully updated karma reason!

Quoting spammail10,

reply 31

So, during one of my tests, RDP lost focus and it once RDP regained focus, the caps/num lock keys would not work. I signed out, closed RDP and signed back into RDP. The Cap/Num lock keys still do not work correctly.

Are the keyboard layouts the same on every PC, including the RDP one?

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Yes

Successfully updated karma reason!

If this goes on much more, I want to get it in its own thread....

Are you using the built-in Windows RDP app or the new one from the Microsoft Store?

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

It's built in. We can create a new thread if you like.

Successfully updated karma reason!

I'm currently testing Microsoft RDP installed from the store to see if that resolves the issue. Unfortunately, it appears that both the built in RDP (mstsc.exe) and the Microsoft remote desktop installed from the store exhibit the same problem.

Successfully updated karma reason!

Quoting sarge338,

reply 10

Multiplicity 3.57 significant input lag on remote/secondary machine in KVM mode with VMware Workstation Pro.

Primary Host OS: Windows 10 20H2 (build 19042.985)

Secondary Host OS: Windows 10 20H2 (build 19042.985)

-- Application incompatibility: VMware Workstation Pro 16.1.2 (build 17966106)

When Multiplicity 3.57 is running on the secondary machine, there is a lag of at least 4 seconds when navigating from the primary host to the secondary host (with virtual machines running) and attempting any sort of input... keyboard or mouse. When multiplicity is unloaded, there is no lag on the secondary machine. This was not an issue until 3.57 was installed.

Are there any updates on this issue? I'm experiencing something similar.
Secondary machine is a Win8.1x64 host running VMWare Workstation 16.2.1
Primary machine is W10x64

When I try to access the VMs (guest machines) on the secondary, VMWare goes not responding or is otherwise inaccessible for a variable period of time. As soon as I unload Multiplicity on the secondary, the VMs are immediately accessible.

Additionally, having troubles with clipboard. I can share text from secondary to primary, but when I try to share text from primary to secondary, I get the spinning circle, and the paste from primary to secondary fails.

This was happening with 3.57
I downgraded to 3.55 to see if the behavior would improve. It did not.

Successfully updated karma reason!

Sarge338 and tetonbob,

I have moved your posts to a new thread, we feel that this issue should have it's own focus.

https://forums.stardock.com/513769/input-lag-on-secondary-machine-with-vmware-workstation-pro

Paul Scroggins
Associate Technical Support Analyst

Successfully updated karma reason!

Quoting tetonbob,

reply 37

Quoting sarge338,

reply 10

Multiplicity 3.57 significant input lag on remote/secondary machine in KVM mode with VMware Workstation Pro.

Primary Host OS: Windows 10 20H2 (build 19042.985)

Secondary Host OS: Windows 10 20H2 (build 19042.985)

-- Application incompatibility: VMware Workstation Pro 16.1.2 (build 17966106)

When Multiplicity 3.57 is running on the secondary machine, there is a lag of at least 4 seconds when navigating from the primary host to the secondary host (with virtual machines running) and attempting any sort of input... keyboard or mouse. When multiplicity is unloaded, there is no lag on the secondary machine. This was not an issue until 3.57 was installed.

Are there any updates on this issue? I'm experiencing something similar.
Secondary machine is a Win8.1x64 host running VMWare Workstation 16.2.1
Primary machine is W10x64

When I try to access the VMs (guest machines) on the secondary, VMWare goes not responding or is otherwise inaccessible for a variable period of time. As soon as I unload Multiplicity on the secondary, the VMs are immediately accessible.

Additionally, having troubles with clipboard. I can share text from secondary to primary, but when I try to share text from primary to secondary, I get the spinning circle, and the paste from primary to secondary fails.

This was happening with 3.57
I downgraded to 3.55 to see if the behavior would improve. It did not.

A spinning circle like that and failure to copy from primary to secondary means your primary computer firewall is stopping the connection for clipboard from working.

Successfully updated karma reason!

Multiplicity stopped connecting to my secondary computer. When I look at the passcode on the primary, it’s a bunch of random characters like “GÄh«‘&éÆÐ)’¹” which of course aren’t correct (see screenshot). If I change the passcode to the correct one and test, it confirms it can connect successfully to the secondary computer but the passcode is incorrect. If I save and go back in, the passcode is a new bunch of garbage characters.

I rebooted both computers.
I updated the secondary to the latest version.
I reinstalled Multiplicity on the primary computer.
I uninstalled and reinstalled on the primary computer.
I uninstalled and deleted settings, and reinstalled on the primary computer.
I started a support ticket and was asked to uninstall and reinstall on both computers, with AV disabled. Did that, still the same issue persists; just waiting for next steps from support.
Support asked if I was a local admin on the machine, and of course yes (can't uninstall or reinstall without being admin).
I found and deleted the Stardock section of the registry (HKLM\Software\Stardock) and deleted it after uninstalling, rebooted and installed again.

The issue still persists. I’m running Windows 11 (21H2 OS Build 22000.856) on both computers, both are up to date. Any ideas?

I've used Multiplicity for years, and for many months on these computers. I did upgrade to Windows 11 recently on the primary computer, but Multiplicity has been working for weeks just fine.

I also just noticed that if I go to the Settings, Setup encryption key, it's also a bunch of garbage characters, but only on the primary computer. I enter the encryption key, save it, then go to open it again and it's back to more random characters.

I'm using the latest version of Multiplicity at this time (3.57 Build 00103.kvm).

Successfully updated karma reason!

Quoting lowellp,

reply 40

Multiplicity stopped connecting to my secondary computer. When I look at the passcode on the primary, it’s a bunch of random characters like “GÄh«‘&éÆÐ)’¹” which of course aren’t correct (see screenshot). If I change the passcode to the correct one and test, it confirms it can connect successfully to the secondary computer but the passcode is incorrect. If I save and go back in, the passcode is a new bunch of garbage characters.

This issue is not unique to the version. Should the issue persist past this fix attempt, please create a new thread for it.

If this is a non-admin account, try under one that is. Should that fail or not be the case, please attempt a purge and reinstall:

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

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

The issue only showed up in this version, so that's why I posted here. I have started a new thread as the purge and reinstall didn't fix the issue, but I don't see it show up. I'll check back later today to see if it does.

[EDIT: My post never showed up after a number of hours. I re-did it and re-posted and it showed up immediately. https://forums.stardock.com/514037/fails-to-connect---garbage-characters-in-passcode ]

Successfully updated karma reason!

Hello!

I have an issue about the Multiplicity KVM sidebar.

The options to enable "Auto hide mode" is doing nothing, and because of that, the sidebar is always on top and visible regardless of my mouse position.

I am on Windows 11 Pro 22H2 build 22621.608

I am using Multiplicity ver: 3.57 Build 00103.kvm with both seamless mode and KVM mode including just one extra machine that has two monitors attached to it.

The option to always show control bar if there is space on screen is disabled.

Successfully updated karma reason!

Hi, I love multiplicity but I'm trying to KVM into a pc ("secondary pc") that shares a monitor with another pc next to it ("primary pc"). When the secondary PC's monitor is on, everything works fine. But after I use the secondary monitor's OSD to switch the hdmi input to the primary pc's hdmi plug (which extends the display of the primary pc, and effectively "shuts down" the secondary pc's monitor connection) my KVM session becomes non-responsive. I can see everything on the screen still, but nothing responds to clicks or keyboard input. If I then use the OSD and switch the hdmi input BACK to the secondary monitor, the KVM session starts working again. Is this just how Windows 10 works? I'm not sure if this is a bug, but ideally my secondary pc would be "headless" and not require a monitor connection at all.

My goal is to extend my primary desktop across 2 monitors, then have a windowed KVM open to the second monitor.

Thanks!

Edit: Another issue that just cropped up today is that copy/paste synch and drag/drop between seamless pc's seemed to stop working all of a sudden. I did install TeamViewer to test out some stuff yesterday, so maybe they hijacked copy/paste. Anyhow, I have it checked in the Multiplicity Settings, is there any way to force re-enable it?

Successfully updated karma reason!

Hello,

Sorry to hear you are having trouble.

Quoting garybtru,

reply 44

Hi, I love multiplicity but I'm trying to KVM into a pc ("secondary pc") that shares a monitor with another pc next to it ("primary pc"). When the secondary PC's monitor is on, everything works fine. But after I use the secondary monitor's OSD to switch the hdmi input to the primary pc's hdmi plug (which extends the display of the primary pc, and effectively "shuts down" the secondary pc's monitor connection) my KVM session becomes non-responsive. I can see everything on the screen still, but nothing responds to clicks or keyboard input. If I then use the OSD and switch the hdmi input BACK to the secondary monitor, the KVM session starts working again. Is this just how Windows 10 works? I'm not sure if this is a bug, but ideally my secondary pc would be "headless" and not require a monitor connection at all.

My goal is to extend my primary desktop across 2 monitors, then have a windowed KVM open to the second monitor.

Thanks!

Monitor sharing with other PCs is just not something we can support.

Quoting garybtru,

reply 44

Edit: Another issue that just cropped up today is that copy/paste synch and drag/drop between seamless pc's seemed to stop working all of a sudden. I did install TeamViewer to test out some stuff yesterday, so maybe they hijacked copy/paste. Anyhow, I have it checked in the Multiplicity Settings, is there any way to force re-enable it?

If that last past a reboot, this is what you are going to want to review:

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

This is not a specific 3.57 issue so if it persists past this reply, please create a new thread for it.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

If you enable "Prevent computer switching via mouse movements: unless shift is held down"

From a computer, swap to another, then swap back. It is not automatically releasing the held down shift button, causing typing to be all in caps.

I believe once Multiplicity knows you are controlling another computer, it should automatically release the held down Shift button on a computer.

Successfully updated karma reason!

This is (probably) not a bug, but a minor feature/UI request.

A couple of times now I've had a red multiplicity systray icon on the primary machine, and the mouse not moving over to the secondary machine. The secondary machine is connected in the "Seamless" configuration, and validating the passcode succeeds with a message saying that the primary was able to connect to the secondary.

I'm guessing it's either: some sort of option that' I've turned on accidentally that locks the mouse on the primary machine (my scroll lock is not on however), or the red systray icon is an indication of some error other than not being able to connect (which shows a light grey systray icon with a tooltop that says "Multiplicity (Disconnected)") ...

... however ...

There is not a hint of a clue anywhere (and I tried the user manual) as to what the red systray icon means. There's nothing in any of the tabs of the multiplicity config dialog to say "XXX option turned on, seamless disabled" (if it's something I've enabled by accident), or - if it's an error that has occurred somewhere after/above connection, there's nothing anywhere to say what the error is: the red systray icon's tooltip is simply "Multiplicity".

FYI for anyone faced with this same situation, rebooting the primary machine fixed it both times.

Please can there be more information about the status of things in either/both of, the systray icon tooltip, and (preferably) the config UI.

If adding to the config UI, I would think that some sort of status panel with each secondary machine and it's connection state/error on connect might be nice. And, if there are "gotcha options" that can be accidentally turned on, which stop mouse and keyboard transferring between machines, then some highly visible alerts in that panel (e.g. "Scroll Lock on: Mouse/Keyboard restricted to XXX machine). I've tripped myself up once or twice with the scroll lock key years in the past.

I know the seamless config tab provides a visible indication of whether the primary is connected to each secondary, but when there is a problem, there's no information about the error there - you're left to poke at the "configure computer" dialog and figure out if it's a firewall rule blocking things, or an encryption key that doesn't match, or a passcode problem. Putting that error information somewhere relatively clear/prominent in the config dialog would be nice

Cheers!

Daniel

Successfully updated karma reason!

Next time, right-click the MP icon in the systray and restart the service - on both PC if possible - see if that fixes it.

~SD

Successfully updated karma reason!

Hi sdRohan,

I tried "Restart Multiplicity Processes" on both the primary and secodary machines - but the only fix for the red systray icon seemed to be restarting the primary machine (prior to that, I restarted the secondary machine, but that didn't fix the issue).

Cheers

Daniel

Successfully updated karma reason!

Quoting TheSchmuck,

reply 49

Hi sdRohan,

I tried "Restart Multiplicity Processes" on both the primary and secodary machines - but the only fix for the red systray icon seemed to be restarting the primary machine (prior to that, I restarted the secondary machine, but that didn't fix the issue).

Cheers

Daniel

If the issue persists past a purge \ reinstall on both PC:

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

Please create a new thread with all the details you provided along with any screenshots \ video of the issue.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!