I can also confirm that rolling my Viewer back to 220.127.116.11 restores the expected functionality of correctly passing the Alt-F4 keyboard shortcut to the host when using Full Control and NOT closing the Viewer.
Good morning! I just noticed today that my often used keyboard shortly of Alt-F4 to close a window is not functioning as intended. As of 18.104.22.168, the keystroke is being passed to the remote host AND it is closing the Viewer window. Expected and previous behavior was that they keystroke gets passed to the remote host only.
Hey, Robert! I'll offer a suggestion for you on this one... I don't think the Remote Utilities agent or host would be handling any kind of autologon for you, that would be a function that you would setup in the machine.
If you are talking about the host automatically starting up at boot up, with the installed Host, that SHOULD happen... BUT I have found through personal experience that some older and more sluggish machines (generally anything running XP likely falls under this heading) may need a little extra time at boot up before starting some background services.
If you go into the Services list in your control panel and find the "Remote Utilities - Host" listing, double click on it and change the "Startup type" to "Automatic (Delayed Start)" that may help you. This gives Windows a little extra time to start up some other programs before it tries to start the RU host up.
Hi, group! I searched, but did not see any results in the forum on this one so I thought I would put it out there to see if anyone else has experienced this before and what they did to fix it (if anything).
I was attempting to assist someone using the RU agent. I was able to connect without issue, but after being connected for a few seconds, the screen started blinking on the users end and got very garbled on my end (RU Viewer) before causing a blue screen of death on the agent side. The exact stop code was VIDEO_TDR_FAILURE in igdkmd64.sys.
I noticed that if I reconnected using the RU agent and did file transfer and not full control, it would not crash the computer.
This is running a fully patched Windows 10 and the video driver appears to be up to date (at least according to Microsoft/Windows Update) and we were both using 22.214.171.124 of the Viewer and Agent. The video driver was an Intel® HD Graphics 530, driver date 4/3/2022, driver version 126.96.36.1992..
We ended up using Microsoft Quickassist instead, so I did not find a solution, but thought I would share here in case others have experienced or do experience in the future.