Cannot change a computer to primary version 3.44

We recently lost are primary computer running Multiplicity Version 3.44.

 

We built a new machine and tried installing the software again as a primary machine. We just keep getting a message that says "Do you want to make this machine act as a secondary instead". The software will install but will not allow a change to primary. Windows version is Windows 10 21H2 we also cannot make the switch on our other setups running the same software version. 

 

Has anyone seen this behaviour?

 

Thanks!

 

 

5,100 views 10 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. First have you change you current primary to secondary first and check this step.

Thanks
Basj,
Stardock Community Assistant.

Reply #2 Top

I deactivated the software in my account for the dead computer that was the primary. Trying to toggle the new software install from secondary to primary does nothing. It will not ask for an activation, nothing happens. During install it will also not allow you to install as a primary. It just reverts to a secondary. I have another installation of this software and I also cannot change the secondarys to a primary. 

 

I toggle to secondary, a prompt comes up asking if I want to switch to primary, I click yes, curser spins for a few seconds, the slid goes back to secondary. No option to put a key in happens.

Reply #3 Top

Hello,
I have forward 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

Reply #4 Top

Here are the Windows event logs generated when I try to switch to primary.

Application: SdDisplay.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.IO.FileLoadException 

Faulting application name: SdDisplay.exe, version: 1.9.2.2351, time stamp: 0x5edf9cda

Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x1e5c8604

Exception code: 0xe0434352

Fault offset: 0x0012e292

Faulting process id: 0x204

Faulting application start time: 0x01d92c18fb8b290c

Faulting application path: C:\Program Files (x86)\Stardock\Multiplicity\SdDisplay.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 06395e8f-836e-4667-b474-a3ba0a0f0532

Faulting package full name:

Faulting package-relative application ID: 

Fault bucket 1975897428228589104, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0 

Problem signature:

P1: SdDisplay.exe

P2: 1.9.2.2351

P3: 5edf9cda

P4: KERNELBASE.dll

P5: 10.0.19041.2364

P6: 1e5c8604

P7: e0434352

P8: 0012e292

P9:

P10: 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBC.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER11B.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER12B.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER139.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER159.tmp.txt 

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SdDisplay.exe_ddac4ce921d7f7718c37859b7589231ae32a82a2_caf4240e_2446ada7-87a9-4055-a193-b2056569c0b7 

Analysis symbol:

Rechecking for solution: 0

Report Id: 06395e8f-836e-4667-b474-a3ba0a0f0532

Report Status: 268435456

Hashed bucket: 11d2de416329991c0b6bcc3e022c4630

Cab Guid: 0

Reply #5 Top

Hello,

Sorry to hear you are having trouble.

We built a new machine and tried installing the software again as a primary machine. We just keep getting a message that says "Do you want to make this machine act as a secondary instead". The software will install but will not allow a change to primary. Windows version is Windows 10 21H2 we also cannot make the switch on our other setups running the same software version. 
End of quote

Immediately after install, the app should prompt for activation.  If you uninstall the app, reboot, and reinstall, does it do that - prompt for activation?

We built a new machine and tried installing the software again as a primary machine.
End of quote

'we' would indicate this is in a corporate environment, yes?

If so, I suspect related to this issue (a more drastic example to be sure):

https://support.stardock.com/space/SHC/1345486875/Activation+window+buttons+do+not+respond+to+clicks

There are two possible solutions there: editing the security options and activating via a command prompt.

Let us know which one works for you.

If both fail, have you done every and all updates to this newly minted OS install?

Sean Drohan
Stardock Product Lifecycle Manager

 

Reply #6 Top

The app does prompt for activation right after install, however if you select primary it will hesitate for a moment and then a pop up says do you want to revert to a secondary. You simply cannot select primary.

 

This is in a corporate network. 

 

All current updates are done on this computer.

 

We never see the activation box.

 

Thanks

 

 

Reply #7 Top

Quoting calvertc, reply 6

The app does prompt for activation right after installation, however, if you select primary it will hesitate for a moment and then a pop up says do you want to revert to a secondary.
End of calvertc's quote

Quoting calvertc, reply 6

We never see the activation box.
End of calvertc's quote

Those statements contradict each other. In the 1st, did you mean to say 'it prompts to be a primary or secondary, then you can tell its trying to prompt for activation but it fails'..?

Did you try the command line activation?  If it works, you will have a License.sig file in \ProgramData\Stardock\Multiplicity 

(note: that is ProgramData, not ProgramFiles).

Sean Drohan
Stardock Product Lifecycle Manager

Reply #8 Top

My apologies, it prompts to be primary or secondary but fails *to present the activation menu. Noted in a prior post is the SdDisplay.exe crash.

The command line activation *attempt appeared to create a folder in that location but no license file.

*edited by admin for missing context

Reply #9 Top

Sean, I figured out I was using the wrong license file. I worked on it today and was able to get the machine to register as a primary using the command line activation.

 

Thanks!

Reply #10 Top

Quoting calvertc, reply 9

Sean, I figured out I was using the wrong license file. I worked on it today and was able to get the machine to register as a primary using the command line activation.

Thanks!
End of calvertc's quote

Excellent, pleased to hear it.

Sean Drohan
Stardock Product Lifecycle Manager