I just want to add my 2 cents as I just started having the 'unload/crash' issues as well and have been following this thread.
Some more data points:
1. I've been using Multiplicity 'Seamless' (aka KM mode) via ObjectDock for months now w/out any issue. Just primary with one secondary system.
2. I've just recently upgraded to Multiplicity Pro and continue to use the Seamless/KM mode but also introduced KVM mode (to access remote systems). The upgrade seemed to have gone well, and I was happy. I now had KM for (Primary and Secondary system), plus I had KVM for (Primary and Secondary + a Third remote system)
3. Then the issue started. The issue is, that on occasion when I would move my mouse from primary to secondary computer via Seamless the cursor would make it a few inches into the remote monitor then stop and the mouse on the primary would then be invisible (for the most part). I would then notice as well that the tray icon went 'poof, as you say' when I hover over it - the actual 'service' was still running though. I figured out that if I did a 'net stop multiplicity' followed by a 'net start multiplictiy' that I would get my cursor back on the primary (so I could at least function normally). Now, after the service restart I could usually move my cursor back to the secondary and it would work (for a time). But three days ago I was at a point where every single time I would restart the service and move the cursor back to secondary the issue would occur.
4. Thinking to myself that this only started after upgrading to 'Pro' and thus adding the KVM portion. So I proceeded to restart the service again, then added a THIRD system to the Seamless mode (via a virtual machine). I wanted to just modify the configuration to see if that would change anything. Right away, I could Seamlessly move the cursor from Primary->ThirdSystem; so I tried Primary->Secondary and it worked fine! So far, after adding this Third System to the KM grid, I have not had a reoccurrence of the issue (knock on wood).
5. In addition, in case it may help identify similarities between all of our systems experiencing the issue, here are some unique aspects to note:
a. Primary has 3 monitors attached, one is via a DL-195 adapter.
b. Primary is running "Symantec Endpoint Protection"
c. Secondary is running "BitDefender Total Security"
d. Primary is an HP Elitebook running Windows 10 Enterprise 2015 LTSB (Build 10240)
e. Secondary is a Dell desktop running Windows 10 Pro 1909 (Build 18363.693)
f. Primary is always running the following software:
- VirtualBox (with a single Windows 10 VM) - Side note, this is the VM I installed MP on as the 'ThirdSystem'
- Fences (Secondary runs this as well)
- Outlook and Skype for Business
Anyways, maybe others with this issue can identify a similarity from what I mentioned above. Like I said, after adding the third system to the KM mode grid I have not seen the issue (but time will tell). If I experience the issue again, I'll be sure to post back here.
Cheers,
Russell