I have found the problem. The MPPortFix.bat file you provide is giving the wrong direction for where the programs are located in the firewall rules.
C:\Program Files (x86)\EdgeRunner\Multiplicity\Multipl2.EXE
C:\Program Files (x86)\EdgeRunner\Multiplicity\MPRDP64.EXE
My install on both my machines is in the Stardock directory and not in the EdgeRunner directory.
C:\Program Files (x86)\Stardock\Multiplicity\Multipl2.EXE
C:\Program Files (x86)\Stardock\Multiplicity\MPRDP64.EXE
The Batch file when opened in Notepad++ shows these entries that point to the wrong location for my installs:
ECHO Creating rule "Multiplicity Application (KVM)"...
netsh advfirewall firewall add rule name="Multiplicity Application (Remote screen control)" dir=in action=allow protocol=TCP description="Allow outgoing network traffic from Multiplicity for remote screen" profile=domain,private program="C:\Program Files (x86)\EdgeRunner\Multiplicity\MPRDP64.EXE"
ECHO Creating rule "Multiplicity Application (clipboard)"...
netsh advfirewall firewall add rule name="Multiplicity Application (clipboard)" dir=in action=allow protocol=TCP description="Allow incoming network traffic to Multiplicity for clipboard" profile=domain,private program="C:\Program Files (x86)\EdgeRunner\Multiplicity\Multipl2.EXE"
One further note for those troubleshooting this problem, I noticed I have some older entries for Multiplicity 3 and 4 further down that must have been installed from an older install from over the years
Under Stardock Multiplicity 4 Profile All, Enabled Yes
and a second one, Stardock Multiplicity 4 Profile Private, Public Enabled Yes
C:\program files (x86)\stardock\multiplicity\multipl2_64.exe with Protocol type: UDP All Ports set (Local and Remote)
C:\program files (x86)\stardock\multiplicity\multipl2_64.exe with Protocol type: TCP All Ports set (Local and Remote)
I don't know if these are needed but it's working so I'm not going to mess with it. 