We are going to release the fix tomorrow, but if you like, you can already test it out. Please, send a message to email@example.com and I'll send you a new Viewer exe. You will just need to replace the existing Viewer exe (rutview.exe) in the Viewer installation folder. Hosts are not affected by this bug.
You are right, it's a different problem. This problem is caused by our migration to another (more modern) key input mechanism.
However, it seems that we should also keep the option to switch to older (previously used) key input/transfer mechanism just for such occasions. Some older applications as in this case may experience problems with accepting key input the new way.
So in the upcoming hotfix we'll add an option to switch to legacy key input so you will be able to enable that option in Viewer connection properties for that specific machine.
So I am wondering, is it possible to run the Agent simultaneously with the Host?
No, the Agent won't be running simultaneously with the Host. However, you don't necessarily have to have the remote user uninstall the Host. They can simply stop Host using the right-click menu ("Stop Host" item). Once the Host has been stopped, they can run the Agent.
Note that the Agent will have different access credentials and other settings than the Host because the two programs keep their settings in registry entries/keys and can co-exist on the same computer.
If no, what would be the recommended best practices for walking a user through granting access through a Host without disturbing the existing configuration (assuming they are already using Single Password)?
If they need to change authorization settings for the installed Host, they must run "Settings for Host" and navigate to Authorization:
There are different ways to access the Host settings:
1. Right click on the running Host icon in the system tray and select "Settings for Host".
2. Windows Start menu -> Remote Utilities Host -> Settings for Host.
Interestingly it appears that downgrading the Viewer is the best workaround for the moment. The 18.104.22.168 Viewer appears to be forward compatible with 22.214.171.124 hosts (at least for basic remote control... I have not tested other functionality such as file transfer, chat, voice and video, etc).
It is. Deep inside these two versions are much closer to each other than to 126.96.36.199.
Thank you for the report. Yes, it's a known bug which was reported yesterday. We will release a quick fix (188.8.131.52) in a couple of days. Meanwhile, we'll be testing your reported key combinations as well.
This error means that the Host cannot connect to the intermediary relay server. There should be other errors in addition to that one. Could you please send us the complete log at firstname.lastname@example.org.