Latest Windows 10 Spring Update - breaks Multiplicity

Only way to get it working is to turn off remote firewall!

from Stardock Forums

My second desktop computer this morning was updated with the spring creators update and immediately I lost multiplicity functionality. I could not get multiplicity on the primary PC to recognize the remote PC. I first uninstalled and then reinstalled multiplicity on the remote which did not help. Then, following some advice from Stardock, I disabled the Windows defender firewall on the remote PC and that worked. Then thinking everything was fine since primary was recognizing the remote, I turned the remote firewall back on and then again lost multiplicity functionality.

Is this an issue with the spring creators update and if so does multiplicity need to be updated?

multiplicity
9,904 views 6 replies
Reply #1 from Stardock Forums Top

One other note, I also have a third PC working with multiplicity. When I look into the advanced firewall information, both entries for StarDock multiplicity show the profile as "Public" and the Windows defender firewall is on. The profile of both entries on the remote desktop PC mentioned in my above post shows "Private". Why would that be?

Fences - Organize your desktop icons today!
Reply #3 from Stardock Forums Top

Multiplicity will setup the firewall entries on first install.  The ports are only open for a network that is considered private for security reasons.

Microsoft have a frustrating ability to set a network to be considered public after a new Windows install in which case your firewall would block all the Multiplicity connections as it will be seen to be a non trusted network.  In that case setting the network correctly back to home/office would resolve the issue.

Reply #4 from Stardock Forums Top

Wow! Thanks.  It worked perfectly.  

Reply #5 from Stardock Forums Top

Quoting billmcl, reply 4

Wow! Thanks.  It worked perfectly.  
End of billmcl's quote

The port fix or what Neil said?  Its for bragging rights B)  

He is right about the Public vs Private, however. What he mentioned is part of this:
https://forums.stardock.com/486104/multiplicity-support-faq#connectionissues

But its rather long to follow and I took a shot that it was just the ports that were hosed.