Title says it all, but I cannot deactivate a product key for multiplicity on a machine that is no longer in service, and multiplicity is not allowing me to activate the key on the new machine.
jforr
Ctrl-Alt-Backspace did not originally work, but switching the kvm to a different monitor and then doing a ctrl-alt-backspace did work to get me into the machine. Not sure what's special about doing it that method, but it worked and the problem hasn't come back since. I do know that the latest windows update reset a lot of settings for people, mostly around microphones, but other settings as well. I'm wondering if something in that update also affected multiplicity.
Connection is already via ethernet and rock solid via rdp. Only multiplicity has the problem.
Video drivers have been updated, but that doesn't appear to have solved the issue. I rebooted the secondary, but when I connected via multiplicity I still got the black screen. After logging in with RDP and connecting to the machine with multiplicity while RDP was still open, I would get to the login screen and multiplicity would work as expected. After idling with multiplicity for a while, multiplicity gave me a message about having lost it's connection. I could s
The monitor shows a normal desktop, but KVM is still black.
I am using KVM mode and when I connect to a secondary machine I get a black screen and no response. ctrl-alt-del and ctrl-alt-backspace don't work. If I have a monitor hooked up directly to the secondary, everything appears fine there and the machine is not in a locked state. I've checked the firewalls, and it is turned off. This had been working fine before and the black screen issue only appeared after a Windows 10 update from this week, but I can't