Cannot Activate Multiplicity on new Primary Computer

Upgraded PC, re-installed windows, multiplicity cannot de-activate primary on old Windows

Good day, 

I recently upgraded my PC and succently re-installed Windows. Multiplicity was activated as primary on the old Windows install.

Trying to activate primary on the new Windows install tries to de-activate primary on the old Windows install but fails (since this no longer exists).

How do I go about resetting the primary so that I can activate it on the new Windows install. It has been about a month since the old primary was active. Does it time out after a given period?

8,024 views 15 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Please use this guide to deactivate old activation : https://forums.stardock.com/486311/accounts-and-activation-support-faq#deactivateproduct. Try those and report back if you still need our assistance.

Thanks
Basj,
Stardock Community Assistant.

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


Trying to activate primary on the new Windows install tries to de-activate primary on the old Windows install but fails (since this no longer exists).
End of quote

The existence of the old PC does not matter.  The 'continue' button should do so as stated in the message you have there:

Are you staying that is not working?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #5 Top

Pressing continue brings up the same dialogue again. Repeating this about 10 times eventually produces the same dialogue as pressing cancel.

Reply #6 Top

[/quote]

Quoting Dohn, reply 2

Hi thanks for the info, however, I have a version purchased through Steam and therefore does not show up on https://store.stardock.com/myaccount/products and since I don't have access to the original Windows I am unable to deactivate the product within the software itself.
End of Dohn's quote

Quoting Dohn, reply 5

Pressing continue brings up the same dialogue again. Repeating this about 10 times eventually produces the same dialogue as pressing cancel.

End of Dohn's quote

It is vital that the Steam client is installed and running - is that the case?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #7 Top

Steam is open and running. Pressing continue simply loops to the same message.

Additionally, I have uninstalled Multiplicity, re-installed Multiplicity and rebooted the computer multiple times in the last month to no avail.

Reply #8 Top

Quoting Dohn, reply 7

Steam is open and running. Pressing continue simply loops to the same message.



Additionally, I have uninstalled Multiplicity, re-installed Multiplicity and rebooted the computer multiple times in the last month to no avail.
End of Dohn's quote

PM me your Steam ID:

https://steamid.pro/

Also, did you ever link your Steam account to Stardock - so that you could log into Stardock.com with your Steam credentials?

Sean Drohan
Stardock Product Lifecycle Manager

 

Reply #9 Top

PM Sent.

Yes, my Steam account is linked to my Stardock account. I believe that is the only way I can log into Stardock.

Thanks.

Reply #10 Top

Quoting Dohn, reply 9

I believe that is the only way I can log into Stardock.
End of Dohn's quote

It's not but does it work now?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #11 Top

It now works. I am able to now activate primary.

Thank you very much for the prompt assistance!

Reply #12 Top

I am having the same issue. Is there a general fix now in place, or is this still a manual support line fix?

Reply #13 Top

Quoting Stirvanous, reply 12

I am having the same issue. Is there a general fix now in place, or is this still a manual support line fix?
End of Stirvanous's quote

I need your Steam64 ID, please.:

https://www.steamidfinder.com/

Sean Drohan
Stardock Product Lifecycle Manager

Reply #15 Top

Quoting Stirvanous, reply 14

Sent via pm
End of Stirvanous's quote

I have reset it, please try again.

Sean Drohan
Stardock Product Lifecycle Manager