Easily reproduced and a great way to lost complete control of the system you are controlling remotely, Requiring user interaction on the physical device.
Almost defeats remote support, especially for join and hold sessions.
~Logon to a screenconnect session without service mode
~Do anything that requires UAC
~Get Stuck FOREVER
(Hopefully your user is around, because there is nothing the HOST can do to get beyond this point)
This is extremely annoying. We do multiple remote sessions and forget at times to launch as service.
A user should not be able to break the software, even if the workaround for "Service Mode" functions, nothing I do as a host should cause me to lose connection to the machine.
Please, add a feature to back out of these or send a ESCAPE from the users keyboard to close the UAC prompt and allow to run in service mode.
Customer support service by UserEcho