Multiplicity Only Starts in Secondary Mode

Multiplicity stuck in secondary mode.

from Stardock Forums

I've been using Multiplicity 3.6 Build 00105 for a few weeks now with no issues. The ancient SSD on my primary PC finally took a dump a couple days ago and I've been forced to reinstall my apps. This is when everything went south.

 

I downloaded Multiplicity from my account dashboard, installed, and the program launched with the familiar prompt asking me if wanted to make that the primary or secondary computer. I chose primary and then received a prompt: "Revert to secondary mode? Do you want to make this computer act as a secondary instead?"

 

NO. I don't. I just want to install what should be a simple app and I want it to work. That's all.

 

When I click "No" the prompt disappears and nothing happens. So then I open "Configure Multiplicity" from the taskbar and get that same bullshit message again. If I want to do ANYTHING at all, I have to choose YES. I choose YES and now I see the configuration screen for a SECONDARY GODDAMN PC. WTF? Ok, let's click the broken SECONDARY toggle button in the top right corner of this config window and see what happens.

"Switch to be primary? Are you sure you want to switch this computer to be a primary rather than being controlled by other computers?"

YEAH. That's what I've wanted from the beginning, but that appears to be to difficult for this craptastic installer. So let's roll the dice and click "Yes".

Boom, NOTHING happens AGAIN. NOTHING. NOTHING CHANGES, NOTHING HAPPENS. So, now I'm stuck in a loop and what should be the PRIMARY PC is stuck being a SECONDARY PC. Absolute bullshit. Ok, let's try restarting the Multiplicity processes? NOPE. Same crap.

So then I uninstalled this awesome software on what should be my primary PC and uninstalled it on what should be the secondary PC. After both PCs reboot, I run the purge batch file to clean up any leftover crap (this program leaves shit all over the place in the registry and on the drive), reboot both again, do a fresh install on the secondary PC and choose the SECONDARY PC option, and then I did a fresh install on the PC I want as my PRIMARY. SAME. DAMN. SHIT.

 

So yeah, this software is now useless and it looks like this forum is the only support option available (great). So what gives? Why doesn't this software allow my PRIMARY PC to be a PRIMARY PC?

 

Both computers are running Windows 10 22H2. Both computers are on the same PRIVATE network. Both computers have MAC reserved IP addresses. Both computers can do everything else they need to do EXCEPT run this damn software. If you guys can't provide a solution to what should be a relatively simple app install and config, I need a refund.

 

 

multiplicity
13,738 views 5 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.

Thanks
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

It sounds like the software is unable to start the activation system which is why it is failing to enable primary mode.

Two possible reasons are a problem with the .net framework that is used by that (v3.5) or a lack of the recent root certificates used for digital signature checking.

I would suspect the second issue as this is a brand new install of Windows which will only check once a week for cert updates and it has been known to be a little slow about this on brand new installs.

https://woshub.com/updating-trusted-root-certificates-in-windows-10/#:~:text=Windows%20updates%20a%20trusted%20root,to%20update%20the%20root%20certificates.

The above seems to have instructions on how to force Windows to update them.

SoundPackager - Customize the Windows sound scheme
Reply #3 from Stardock Forums Top

Same Problem. Absolute garbage software. Why do we as normal users have to read up on how to update random certificates... why can't sh1t just work normally?

Reply #4 from Stardock Forums Top

Quoting th2pun1sh3r, reply 3

Same Problem. Absolute garbage software. Why do we as normal users have to read up on how to update random certificates... why can't sh1t just work normally?
End of th2pun1sh3r's quote

Unfortunately the blame for that rests with Microsoft.  We cannot force their root certs to update ourselves.

Reply #5 from Stardock Forums Top

I just installed input director... worked in 2 minutes instantly. No certificates, No BS, and its free... open source...