Version 3.6 Build 00105.kvm

ok did the steps and installed the version on my accounts page nothing, installed the latest one still nothing. Still the same issue it wont open the configuration window

OK i followed everything and still nothing. I even went further and installed a fresh copy of windows 10 (updated and all), But still the same issue the  configuration window will not open, but the application is on the task bar.

Thanks for the quick reply

I assume 'refresh' means a format \ reinstall of Windows 10, yes? -- YES

Going to the installation directory on said Secondary, what are the results of opening the MultiplicityConfig.exe manually? - Nothing opens up

When you 'did the updates', did you do them manually (download them individually yourself and install them)?  Meaning, this PC is Internet isolated (no direct Internet access)? - Windows update checker

MultiplicityConfig.exe - ran on admin mode nothing, ran normally nothing.. application wont open at all

Log Name:      Application

Source:        Application Error

Date:          11/12/2024 4:30:20 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-ABI8GFM

Description:

Faulting application name: MultiplicityConfig.exe, version: 3.0.105.0, time stamp: 0x6488cf03

Faulting module name: amdxx32.dll, version: 32.0.12019.1028, time stamp: 0x670646ef

Exception code: 0xc0000005

Fault offset: 0x0059c134

Faulting process id: 0x71c

Faulting application start time: 0x01db3552749e2e59

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

Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0408380.inf_amd64_a2a50bd2d2429936\B408421\amdxx32.dll

Report Id: db40de2c-9a1b-4fc3-9046-c075ea07cb22

Faulting package full name: 

Faulting package-relative application ID: 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>100</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2024-11-12T22:30:20.0526380Z" />

    <EventRecordID>1281</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>DESKTOP-ABI8GFM</Computer>

    <Security />

  </System>

  <EventData>

    <Data>MultiplicityConfig.exe</Data>

    <Data>3.0.105.0</Data>

    <Data>6488cf03</Data>

    <Data>amdxx32.dll</Data>

    <Data>32.0.12019.1028</Data>

    <Data>670646ef</Data>

    <Data>c0000005</Data>

    <Data>0059c134</Data>

    <Data>71c</Data>

    <Data>01db3552749e2e59</Data>

    <Data>C:\Program Files (x86)\Stardock\Multiplicity\MultiplicityConfig.exe</Data>

    <Data>C:\WINDOWS\System32\DriverStore\FileRepository\u0408380.inf_amd64_a2a50bd2d2429936\B408421\amdxx32.dll</Data>

    <Data>db40de2c-9a1b-4fc3-9046-c075ea07cb22</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Figured it out.. Had a friend share his amdxx32.dll from a Win 10 pc. A little permission changes and poof.. Multiplicity is running flawlessly...