Hello,
I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate you feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

thanks for the reply.    No, i didnt do a roll-back.  Thats the first thing I thought of.  (did i do a macrium restore).

only other thing i can think of, is whatever is causing the crashing out of the tray (only happens on that specific secondary) happened after my changing of the password, and thus didnt save properly as it didnt shutdown or exit properly.

I created a new thread with the crash report today - perhaps that can help figure out what on earth is going on.

I will say, i just purged a second time and "maybe" (if it works for a length of time going forward) then i can dial it into the fact that I had my main pc set up as primary, but i had done a swap to secondary and enabled the usual "secondary" to be primary, just for a brief moment so i could get my preferred settings stored on that pc on the unlikely chance that i ever had to switch roles.  (plugfordynamicswitching)

Perhaps it didnt like that.   (yet my main primary pc has setting for both sides of the fence and is fine, so no clue).

dont know what else to add at this point.   would love to get the crashing on the secondary resolved so i can move onto Wake on lan being greyed out/not working. 

if i can resolve both of those, my outlook would be much more positive.   time will tell. 

well, first of all - looks like the problem was related to (unfortunately AND preliminarily) having a secondary set up temporarily as primary as well.

Its early to tell, but so far so good.  I was crashing out of tray and thus losing much of what multiplicity did at a large enough frequency to make it a huge problem.

I did the purge, re installed, re did my settings, toggled the offending secondary to primary and primary to secondary to re-do "those" settings on the "usually secondary" pc.   

Immediately began crashing again.

Did another purge, did not toggle it to primary or attempt to configure it, and so far so good.  Assuming that was the issue, it makes me question A) why that doesnt happen on my main pc (as its been toggled to both sides of the fence) and if it will be looked into as without dynamic switching it is going to be a situation that presents itself from time to time for various reasons.

Only thing i can think of as far as discrepancy between the two pc's goes is the main pc was initially configured as primary then swapped to secondary.  whereas the secondary was configured as such, and later swapped to primary.

Somewhere in there - even after multiple purges, its not working out.

Much less pressing than the wake-on-lan which youve just touched on and youve undoubtedly seen me posting about all over (super important that i get it functioning)

the tray icon, right click wake on lan was grey.  Did nothing.  Of course, it now is not for whatever reason.   Regardless clicking on the populated pc's in the flyout menu does nothing.

I have to ask, is that sending magic packets?  How many? could it be adjusted?  I just cant understand what the issue could be.   Every other app i use handles mac in all capital letters,  whereas multiplicity is setting them lowercase, but i doubt thats related as its evidently working fine for many others. 

I'm at a loss. 

does it not use a magic packet and instead use some other means?  if it does some kinda echo request i believe those are often blocked.

also i do have ipv6 enabled but thats only for external IP and is dual stack regardless (hence multiplicity picking up an internal ipv4 address in the configuration)