Multiplicity 4 fails clipboard and file copy on Win 11

from Stardock Forums

Multiplicity 4.07 Pro — Intermittent File Copy and Clipboard Failures; RADAR Memory Leak on Secondary

Environment

  • Multiplicity 4.07 Pro on all machines
  • 3x Windows 11 24H2, fully updated
  • One primary, two secondaries
  • Secondaries are freshly unboxed, clean installs
  • Primary is well-maintained, clean system
  • All machines running Windows Defender only — no third-party AV or firewall
  • All machines on the same private network with standard Windows network settings

Observed behavior

Operation Result
File copy: Secondary → Secondary Works correctly in both directions
File copy: Primary → Secondary Intermittent — sometimes works, sometimes fails
File copy: Secondary → Primary Fails — no progress, no error, silent
Clipboard: Secondary → Primary Intermittent — sometimes works
Clipboard: Primary → Secondary Fails — silent, no error message
Clipboard: Secondary → Secondary Fails — silent, no error message

Diagnostic finding

Event Name:  RADAR_PRE_LEAK_64

P1:          MultiPLV64.EXE

Bucket:      1988996491034500250, type 5

 

RADAR_PRE_LEAK_64 is Windows' resource leak diagnostic firing against Multiplicity's live preview component on the secondary, indicating virtual memory or handle accumulation.

 

 

Stardock Software Multiplicity
57 views 2 replies
Reply #1 from Stardock Forums Top

Hello,

Sorry to hear you are having issues. 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. Thank you.

Basj,

Stardock Community  Assistant

Reply #2 from Stardock Forums Top

This would typically be a firewall issue.

When copying data from machine B to machine A, a connection is made from A to B.  This is typically the reverse of mouse/keyboard data so a firewall blocking can cause this to fail.

Another possibility is you have a tool on the secondary which is blocking Multiplicity from being able to determine what machine to contact.  Tailscale is known to break this even when not in use.  We are planning to tweak how we send data for that to try and address that in an update but it requires a protocol change..

Do either of these explain the problem?

We will look into the leak.

Ashes of the Singularity II