I meant to say when I unload instead of disconnect. Sorry for not using the correct technical term.

Thank you.

When I use the unload from remote (secondary) connection on Multiplicity (on primary), it is still active, the cursor still moves on the remote connection from the primary computer and the remote (secondary) connection is very slow even if unloaded from the primary. So I know that it is still active even though I unload from the remote (secondary) connection from the primary computer. I have to exit the Multiplicity program on both the primary and secondary computers to end the connection. This needs to be fixed because when you disconnect and leave Multiplicity up on the remote (secondary) computer, Multiplicity should not be active on the remote (secondary) computer after unloading.

The Multiplicity connection makes the secondary computer slower even when Multiplicity is closed (from the sidebar). Multiplicity stayed in the hidden taskbar when I closed the sidebar window when using KVM mode. So I had to unload Multiplicity using the hidden taskbar. No I do not have a Seamless connection to the same computer. When I unload and then make sure that Multiplicity is not running in the background using Taskmaster, the computer is not slower. What I did is download the newest version of Multiplicity and configured it to come up in KVM mode  and not Seamless. I installed the newest version of Multiplicity on the secondary computer too. I am going to test it again and get back to you.

Glad it worked out for you. 

Sean Drohan
Stardock Support Manager