We are seeing an issue with Multiplicity (version 3.44) on Windows 10. Both the primary and secondary have Windows 10 installed. Both machines are on the same subnet on a private domain. The set up was working fine before upgrade the primary machine from Windows 7 to Windows 10. We deactivated the license on the old machine and activated it on the new. Now the application is crashing when you move from the primary to the secondary. The mouse makes it about an inch into the monitor on the secondary, then the app crashes on the primary. The cursor then disappears on the primary, and you can't bring it back without locking the primary and unlocking it. The event viewer shows the following during these events:
Faulting application name: Multipl2.exe, version: 3.0.0.0, time stamp: 0x52af40db
Faulting module name: ntdll.dll, version: 10.0.17134.471, time stamp: 0xfe852bc4
Exception code: 0xc0000374
Fault offset: 0x000d8499
Faulting process id: 0x2880
Faulting application start time: 0x01d4c2f6ba1f5bba
Faulting application path: C:\Program Files (x86)\Stardock\Multiplicity\Multipl2.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 32ddf2fd-7a7b-421b-8ff3-729686a1c23c
Faulting package full name:
Faulting package-relative application ID:
I have tried uninstalling and reinstalling multiplicity on both machines. I tried connecting directly to the IP of the secondary as opposed to the hostname. I confirmed that the multiplicity ports were open on both machines. Does anyone else have any thoughts on this? Typically, if Multiplicity stops worked, restarting the services makes it work again, but that is not happening in this case.
Thanks,
Max