Multiplicity 4 – Primary computer locked / Activation required
Windows Insider 26200.x (helpers fail to execute)
Multiplicity 4 – 4.07
Windows Version
PRIMARY PC: Windows 11 PRO build 10.0.26200
SECONDARY fresh installation PC: Windows 11 PRO build 10.0.26200
Summary of the Issue
Just bought a version 4, and upgraded from 3 . Cleaned everything, rebooted, reinstalled, and nothing helps . On my main PC running Windows 10.0.26200, Multiplicity 4 installs successfully but cannot be set as a Primary computer.
-
“Primary computer” is locked with Activation required
-
Finish button is disabled
-
Only “Secondary computer” can be selected
-
No visible activation or sign-in option is available in the UI
The same installation works perfectly on a second PC
Key Finding (Root Cause)
Multiplicity 4 relies on small helper executables (elevation / activation helpers).
On Windows Primary these helpers exist on disk but cannot be executed by Windows.
Example helper:
Observed behavior
-
File exists (visible in Explorer)
-
Running it from CMD or PowerShell fails with:
This happens even when:
-
Path is correct
-
PowerShell syntax is correct (
.\DeElevate64.exe) -
File is present and readable
This indicates a Windows loader / execution failure, not a missing file or PATH issue.
What Was Tested
✔ Confirmed
-
Full manual purge (files, services, registry, firewall rules)
-
Clean reinstall using latest installer
-
Running installers and apps as Administrator
-
Disabling Defender / Smart App Control / Controlled Folder Access
-
Network checks (no VPN / no proxy)
-
Correct PowerShell execution syntax
❌ Still fails
-
Helper executables (
DeElevate64.exe, etc.) cannot execute -
Activation never starts, so never completes
-
Primary computer remains locked
Why this only affects one PC?
-
Main PC: Windows pro 10.0.26200 → fails
-
Second PC: Stable Windows pro 10.0.26200 → works perfectly
Conclusion
This issue is not caused by user configuration, corrupted install, or licensing misuse.
It appears to be:
-
A compatibility issue between current Stardock service/helper binaries and this Windows build?
-
Possibly related to service installation, execution, or Windows loader behavior?
-
Specifically related to helper executable execution / elevation?
I’m happy to provide:
-
Full logs
-
File hashes
-
Defender history
-
ProcMon traces if needed
Thanks for looking into this.