Same issue.  This worked flawlessly before I upgraded from the initial release of 4.x to 4.01.

All,

Multiplicity 4.0.1.1 Beta has been released.  For details, please see:

https://forums.stardock.com/534990/multiplicity-4011-beta-feedback

As always, thank you for your time, feedback, and support.

Sean Drohan
Stardock Product Lifecycle Manager

Where can I download the beta preview. I'd like to test it. It can't work worse than the current version.

Here is my feedback on the current stable release.

Let me begin with the end. After I finally got it working, I noticed that sessions won't last longer than minutes before my connection drops. I have both computers in the same 1GB switch and selected medium compression. But after about a minute, if I move the mouse, the video connection will drop.

About setting up: I would expect the Test button to test every connection needed. It doesn't. I had to disable the firewall on the secondary to get it working. I wanted to configure proper firewall rules, but my sessions don't last long enough.

This (information courtesy of Co-Pilot)

• Multiplicity Service: TCP port 30564
• Multiplicity Clipboard: TCP port 30565
• Multiplicity Audio Service: TCP port 30567
• Multiplicity Remote Screen Service: TCP port 30569

Additionally, make sure the following executables are whitelisted in your firewall:

• MPRDP64.EXE
• Multipl2.EXE
• multi2_64
• multisrv64
• multiplv64
   

does not seem to be enough.

I would really like to buy this product, but obviously it mist work first.

Hello,
Sorry to hear you are having issues. Try this one.

https://stardock.atlassian.net/wiki/spaces/SHC/pages/2285469740/Multiplicity+4.01+Release+Changelog+Released+02+26+2025

Thank you,

Basj,
Stardock Community Assistant

JFYI, this is the same problem that I reported, and it was never resolved.

So that app did not change, your OS did...

I know you honestly believe it to be a problem \ design issue with the app, however, in my 13 years at Stardock, it's never not been related to a firewall issue, 100% of the time.

https://support.stardock.com/space/SHC/1288044590/I+can+move+my+mouse+to+the+Secondary+but+cant+interact+with+the+desktop

Sean Drohan
Stardock Product Lifecycle Manager

I don't believe your statement here, that OS updates do not frequently cause apps that were working before to have issues after, is a commonly shared belief. I found this one particularly amusing as it was with one of their own products (Remote Desktop, which operates in the same space as MP)

https://www.msn.com/en-us/news/technology/oh-cool-microsoft-melts-bug-that-froze-server-2025-remote-desktop-sessions/ar-AA1DD9fC?ocid=BingNewsVerp

But the release has been plagued with issues since its rollout started:

https://www.bing.com/news/search?q=windows+update+problems&qs=n&form=QBNT&sp=-1&lq=0&pq=windows+update+problems&sc=10-23&sk=&cvid=686D3CC2FC4A475F8A3EE7EAD837CD3E

Thats certainly your perogative but the batch file I wrote that's there will almost certainly fix it.  Give it a shot (on both PCs).  If it does not work, we can keep working on it with you.

Sean Drohan
Stardock Product Lifecycle Manager

I didn't say anything about frequency of breakages.  What I said is that it would be better if the app deals with that itself instead of doing these runarounds.  (Which at least sounds relatively easy since you're using TCP, and it's a simple issue of maintaining a few FW rules.)

Quoting sdRohan,

reply 41

Ill do you one better, MS update caused it to flag Chrome itself. 

You are saying we should fix what MS breaks.  We have built an entire software division around that

Let me know the result of running the bat file when you can, please. 
 

The question is whether you can do something about it.  In the case of just resetting the firewall, it would be much better to just include that batch file and have a menu entry that runs it.  Even better would be to say something about that menu entry if it suspects a misconfigured firewall.  Further better could be to do that silently after actually inspecting the FW rules and when the connection doesn't work (possibly asking nicely first).

In any case...  I never intended to suggest that the script won't work: I actually fully expected it to work.  The main thing that bothered me was the need to do something manual.

But because you asked, and I actually had a few minutes, I finally tried it.  I first ran it step-by-step to see for each rule whether there were any changes.  Several rule names were already present (I can list them if it'd help).  Resetting them one-by-one (on the main desktop) didn't make it work.  I then tried running the whole script, and still broken.  Finally, I ran it on the controlled laptop, and the KVM connection stopped working (ie, I couldn't connect at all, and MP said so).  Next, I rebooted the laptop, and things got back to the same place: the KVM feature connects, but no mouse/keyboard input.

The only thing I did not do is reboot the desktop (the primary machine).  I can try that if you really think it can make a difference, but I'd rather avoid rebooting this machine.

(Disclaimer: my MP registration code should be invalid now, but the KVM does seem to still work. I don't know if that could make any difference, though it's basically the same as it was all week.)

Sidepoint: it's confusing that the echo-ed labels are different from the rule names in some cases.  That was the main reason I just re-ran the thing completely after trying them one-by-one, to be sure that I didn't make any mistakes.

I don't, and never had.

After updating my laptop from Windows 10 to Windows 11, Multiplicity will not connect. I uninstalled and reinstalled Multiplicity on both the primary and the laptop secondary; I copied the Multiplicity4_setup_sd.exe file used to reinstall on the primary to the laptop to ensure the same install version. It still fails to connect with the same error message: "The computer appears to be running a different version of Multiplicity."

"About" on the primary shows "Version 4.01 Pro" while the laptop (and other secondaries to which I can connect) shows "Version 4.01". The other secondaries run Windows 10. The laptop was the first of my machines to get Windows 11.

That worked. Why doesn't standard uninstall/reinstall work?

About three days ago, when I was using Multiplicity 4.01, the mouse cursor would most likely trigger keyboard F-zone keys such as F2 and F8 on the main computer when shuttling between different computers. We need to restart Multiplicity 4.01 to resolve the issue, but it will reappear later. I reinstalled the software and reset the network, but still cannot solve the problem.