Encryption key and passcode always garbled on secondary

from Stardock Forums

Hi,

I recently got my company notebook and wanted to setup Multiplicity there (and hopefully get audio transfer to work, so I don't need a second headset etc. as I already have one on the desktop).

 

But I cannot get a connection working because for some reason on the secondary (Windows 10 Enterprise, Build 20H2) the encryption key and passcode is always shown as some garbled characters, even when I enter TEST1234 for any of them, when changing again or clicking on "show passcode" it's always some garbled crap. So for me it looks like there is a problem while saving the encryption key at least (which I guess would also lead to problem on passcode).

 

It may very well be that some policy settings are set by company and user is a domain user (cached credentials usually) BUT local administrator.

 

Another thing I noticed, when I want to set audio transmitting it asks because there is no speakers/microphone defined without a headset plugged in (but there is a realtek chip on the board) and Multiplicity asks if I should ignore that, I click on yes and it wants to reboot > ok ... but after reboot it asks the same again when going to that tab ...

multiplicity
2,588 views 1 replies
Reply #1 from Stardock Forums Top

Nevermind ... it seems it is already solved.

It was either that the windows installation was not yet activated, that I used cached credentials and domain controller was not available (if Multiplicity encryption somehow depends on NTLM/Kerberos auth?) OR that I configured multiplicity on the secondary using windows remote desktop. Anyway, now it seems to work.