Stardock Forums
With the Multiplicity 4.01 release, we are creating this thread so that users can report any observed issues.
Thank you for your interest and any time you put into making Multiplicity a better product.
Sean Drohan
Stardock Support Manager
Same issue. This worked flawlessly before I upgraded from the initial release of 4.x to 4.01.
We appreciate your perspective and it is well received. That said, we have to work with what exists and what has worked for us and our clients to this point. If there is a particular issue you would like to focus on, please create a thread for it and I would be happy to continue to work with you on it.
Sean Drohan
Stardock Product Lifecycle Manager
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
Same issue. This worked flawlessly before I upgraded from the initial release of 4.x to 4.01.
This was addressed with the 4.0.1.1 beta
https://forums.stardock.com/534990/multiplicity-4011-beta-feedback
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)
Additionally, make sure the following executables are whitelisted in your firewall:
does not seem to be enough.
I would really like to buy this product, but obviously it mist work first.
I am getting a popup to upgrade, but the changelog is empty. What changed? It also doesn't list the version number it wants to update to.
https://www.stardock.com/products/multiplicity/history
Hello,
Sorry to hear you are having issues. Try this one.
Thank you,
Basj,
Stardock Community Assistant
For any firewall work on the remote PC, you are going to want to be at it, janz...
You are going to want to review this in full
https://support.stardock.com/space/SHC/1287946260/Multiplicity+Connection+issues+101
Sean Drohan
Stardock Product Lifecycle Manager
JFYI, this is the same problem that I reported, and it was never resolved.
Until yesterday, I have been using the KVM feature, and it worked fine. The only thing that changed is that my master desktop was updated to Win 24H2 -- and now the KVM window shows fine, but no input goes through: neither mouse nor keyboard interaction.
Related: Multiplicity provides three ways to connect:
FWIW, I very much like this combination of features, so I really wanted it to work. But clearly, I'm now at a point where the whole thing is pretty much useless.
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.
Sean Drohan
Stardock Product Lifecycle Manager
As I said, using the KVM feature is already so minimally useful that I don't see much point in fighting my firewall or whatever to keep that working.
If it is a firewall problem, then there is certainly a problem with the app: how many apps would you install if they require you to fiddle with your firewall after random OS updates? Just imagine that, for example, steam would have stopped working after my update -- would that be a considered a bug?
That was the problem part. The design issue part is your intended audience. I'm not expecting something that is as simple as the Windows Quick Assist feature which is designed to be as grandparent-proof as possible, but MP is placing itself at a point where even proper power users would doubt the time-investment vs utility ratio.
But again, this is all a side-comment.
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:
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
Hello, I am a graduate student at a university. Every day when I use Multiplicity 4, I use a desktop computer and a laptop. Recently, I found a software bug. When I use a desktop mouse as a laptop, if there is a network fluctuation or other disconnection between the two computers, my mouse will not work with either computer. Even after reconnecting the two computers, the problem still cannot be solved. The only solution is to restart your desktop computer. I would like to ask how to resolve this situation. Is it a software design flaw? Is it possible to design keyboard shortcuts in the future to allow the mouse to detach from the controlled computer and return directly to the desktop computer?
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 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.)
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.
Sean Drohan
Stardock Product Lifecycle Manager
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.
If you have a 3rd party AV app, as a test, shut it down and rely only on Windows Defender for the test.
Sean Drohan
Stardock Product Lifecycle Manager
Again, I have never seen it not be a firewall issue. If you totally disable Windows firewall (domain, private, public) on any \ all MP PCs, does it work?
Something else you will want to ensure in the firewall:
Sean Drohan
Stardock Product Lifecycle Manager
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.
On each PC, please try
https://support.stardock.com/space/SHC/1347158073/Multiplicity+purging+and+re-installing
Sean Drohan
Stardock Product Lifecycle Manager
Pleased to read it worked for you.
Sean Drohan
Stardock Product Lifecycle Manager
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.
Welcome Guest! Please take the time to register with us.