Seriosa

Seriosa

Joined Last seen Member # 7614763
0 Posts 0 Replies 75 Reputation

Thank you very much for the clue! After extensive debugging, My friend and i found the issue. It was NOT related to: Windows builds .NET Framework corruption Activation/license problems User profile issues The actual cause: IObit Advanced SystemCare IObit Advanced SystemCare had registered malicious entries in the Windows Image File Execution Options (IFEO) registry, hijacking Stardock executab

13 Replies 4,592 Views

Hi Sean, Thank you for the clarification. I’ll keep this brief. On my Primary machine, I’m unable to complete setup or switch it to the Primary role, so I never reach an activation window. Because of that, no activation attempt would have reached your servers from that system. I’ve confirmed this is specific to that machine.

13 Replies 4,592 Views

[quote who="basj" reply="3" id="3985781"] Just a though, did you installed the secondary first before the primary, and did you activated multiplicity on your "Secondary"? From what I understand, you don't need to activate Multiplicity on the secondary, just select it as a secondary. If you did activate the secondary, please try deactivate the secondary activation first. Than try the activation on the Primary again. Thank you, Basj, Stardock Community Assistant<

13 Replies 4,592 Views