This week I installed Windows 11, 24H2 feature update on one of my PCs that is seamlessly connected to the master PC, running Win 11, 23H2. They are connected with Multiplicity 3.6, build 00105. After the 24H2 update, every few minutes, the computers disconnect, and I get a Multiplicity pop-up on the primary that the secondary was not responding quickly enough. After a minute or so, the two reconnect and it works for several minutes, until they disconnect with the 'not responding fast enough' error again.
Obviously the problem is the 24H2 feature update, since I've never seen this before, but I doubt that Microsoft is going to be very interested in fixing the bug on their end. Is there a fix available from the Stardock side?
Are they using a wired or wireless network?
We have not had other reports of this so my gut says it may be coincidence with the 24H2 install.
The message would mean a connection was lost because the other end didn't reply within 6 seconds which typically would mean computer is turned off, extremely busy or connection is unreliable.
It's a wired connection, and I get the error and disconnect while I am actively typing through the primary keyboard onto an app on the secondary computer. There's definitely NOT a 6-second lack of reply... well, there might be a lack of reply from secondary to primary, but the primary to secondary information flow is happening when I get the disconnect.
With a wired connection, I'm not sure what 24H2 would do to make the ethernet connection unreliable.
FYI, I rolled back the 24H2 feature update, and the disconnect problem went away. So it's pretty clear that the 24H2 update is causing the disconnect issue. As 24H2 is rolling out, are there any others finding this problem?
I've just bought Multiplicity v4 pro and I'm getting this issue. I managed to get my desktop connected to my laptop (using WIFI) and everything worked well for an hour or so. But now I'm getting alternating messages on primary: complaining about a "wrong passcode" first, and then the "secondary did not respond in time".
Hello,Sorry to hear you are having issues. Please report your Windows full version and OS Build number. Please use Winver.exe to get this number.
Thank you.Basj,Stardock Community Assistant.
Follow up: restarting the secondary fixed the issue, but it started to happen again (almost) exactly an hour later.
Thanks for getting back.
Primary (Desktop): Windows 11 version: 24H2 (OS Build 26100.2605)
Secondary (Latop): Windows 11 version: 23H2 (OS Build 22631.4602)
Did you try "Flush DNS Cache"?
I'm using currently Muliplicity 3 KVM Pro with 9 Secundaries, 7 of them on Win 11 24H2, 2 on Windows 10. The Primary running on Win 11 24H2. And I have any issues.
Hello,I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.
Basj,Stardock Community Assistant
If you are connecting via hostname, try entering the IPv4 address instead. Example
You are also going to want to ensure you are using 4.0.0.4 on BOTH the Primary and all Secondary PCs.
The best tests are done if all PCs are wired.
If all else fails, burn and reinstall on ALL MP PCs
https://support.stardock.com/space/SHC/1347158073/Multiplicity+purging+and+re-installing
Sean DrohanStardock Product Lifecycle Manager
Sean,
I am using the secondary PC name, not it's IP address. The computers are both wired. I am also using Multiplicity 3.6, Build 00105, I haven't upgraded to 4.0 yet, but it sounds like user stardock 641 above is having the same issue with 4.0 that I'm having with 3.6.
Then you (each) would have something to try.
OK, I installed 24H2 on the secondary PC again (wired connection), and tried using the IP address two ways: First by checking the "always use IP address x.x.x.x" box, and then by deleting the secondary and reinstalling it on the primary PC using it's IP address as the name (after I did this, I did change the 'display name' to the PC name that I use).
Same problem. I'll be moving the cursor or clicking something on the secondary PC, when the cursor freezes, and after a couple of seconds I get the 'secondary computer disconnected because it did not respond in time' pop up on the primary, and after a few more seconds it then reconnects.
Could it be a firewall or anti-virus issue that is blocking the connection?
It would be prudent to install the trial for MP4 (on all PCS, not just the Primary) as that is our main focus of late.
A legit ask and I would throw the possibility of a VPN connection as being a consideration if in use.
No VPN, I have Webroot installed on both PCs for years, so I doubt that's an issue. Dell Command Update is wanting to do a BIOS update and a couple of other drivers. I'll install those and see what happens, then try MP4 on both.
https://forums.stardock.com/486104/multiplicity-support-faq#erraticconnections
The link posted states that webroot can in fact cause issues with multiplicity. Maybe try disabling it temporarily and see if that fixes the problem?
So, on the first day of using Multiplicity 4 Pro I encountered the loop twice. I executed "Flush DNS Cache" and it went away; however, I've been encountering connection problems since:
The weird thing is, dispite all the problems, when I test the connection in the secondary configuration dialog it always returns success even when they won't connect.
@Mad Trix - Thanks for the flush DNS cache tip; however, I think this problem is related to version 4 and/or connections between Win 11 24H2 and 23H3, and not Win 10. I don't think your setup rules anything out here.
Follow up: the machines have now connected; it took around an hour.
I've been able to get connections working reliably now. Every morning, I drag the secondary off the grid, wait 5 seconds, and then drag it back on. It connects almost immediately.
More information.
The problem looks to be associated with primary, as connections reestablish immediately after reboots/shutdowns/suspends to RAM on the secondary. Or to put it another way, I only get connection problems after rebooting/shutting down the primary.
Hi,
This blog has been quiet for a while, so I'm wondering if there's been any discoveries or patches on the Stardock side that relate to this connection instability issue. I have not had the time to play with updating both primary and secondary to 24H2 and seeing what happens, since it's stable with 23H2 (getting in final grades, doing taxes, new semester...).
However! I have another multiplicity-linked computer set, no VPN, wired ethernet, primary running Win 10 Pro 22H2 (not upgradeable) and secondary running Win 11 at 23H2. I was doing a Backblaze backup to the web on the secondary, with the ethernet backup data rate running around 100 Mbps on both the up and down links, when I started getting the secondary disconnect and quick reconnect issue. Over the hours I was using the computer doing this uplink transfer, the connection was stable most of the time and there was no mouse lagging, but then it suddenly surprised me for several minutes of doing the disconnect / reconnect cycle. After a few minutes, it was stable again.
My assumption is that the heavy network traffic was causing the Multiplicity timeouts. Is there a way I can lengthen this timeout period? That might be helpful to try with the 24H2 problem I had.
Can you redownload the trial from your account page, install it on each PC, and try again?
https://store.stardock.com/myaccount/products
Houston, we have a problem....
I upgraded from 3.6 to 4.0, buying the upgrade license for the basic version because I only use the KM function as I work between two computers and two screens. However, I have lost the <Windows Key> <L> log off function (I have to go to each computer to log off, it used to be that a single-logoff did both) with this version, as well as the 'log into the primary, and it then logs into the secondary' function.
I realize that this function had some drawbacks, but would like it back for my setup. How do I get it?
I haven't tried upgrading both computers to 24H2 yet, as I want to make sure that the 4.0 upgrade works.
WinKey + L is not 'log off', rather 'Lock' and it is indeed still included in MP4
Primary:
Secondary:
You will also want to make sure you are using the current beta on each PC:
https://forums.stardock.com/534272/multiplicity-401-beta-feedback-thread
There are many great features available to you once you register, including:
Sign in or Create Account
