Thanks for update. However, I am not sure that I understand.
There is no RA session ongoing, so no session to be kicked out from.
When I press "Connect" on the shown screen above, things behave a bit differently on win10 vs win7.
On the win10 Remote I can see that it goes back to Windows login screen, logs in, restart RA and eventually the screen is shared. So maybe this is what you mean when you state that the session is restarted.
But, on my win7 Remote, when I press "Connect", the Remote goes back to Windows login screen and stays there while showing "Waiting for remote instant of Remote Assistant to start" on Host.
This state is never resolved. Finally connection with RA is lost and the following is shown on Host:
If you then, on the Host, try to reconnect, you get the following message:
On the Remote nothing is shown except the win7 login screen.
When logging in on win7 Remote it re-establishes network connection which indicates that this was pulled down when Host tried to establish a RA session.
As a RA user, you previously have always had, and I think, should have, the impressesion that you dive into the current session. All session specific information data and application is kept as is and there is just another Remote user (the Host) controlling the inputs as has been determined by the setup of the configuration of the Remote computer.
I hope this is what you will revert back to. Anything else seems very confusing.
I must also take the opportunity to thank you for a great application. I have been around from start. Performance and feature suite have improved a lot over the builds.
I have tried to give my 5cents of testing and hope you can do something with it.
Kudos and Thanks!