Yes, absolutely. Note that you may not notice such small breaks when you use a web browser because a web browser essentially just downloads a web page onto your computer and then you view this page offline (perhaps this explanation is simplified a bit but still applies to modern browsers).
Things are different with remote controls though. They need a relatively stable connection to "stream" remote image and keep the connection alive. The fact that some competitor products may seem "more stable" doesn't mean they are. It only means that they found a way to trick you into believing that what you are seeing on your screen is a real time image (whereas there might be a complex algorithm in effect to "smooth out" little network disturbances).
Hard to say what might be causing this, but there is a good chance (judging by the browser response) that DNS resolution somehow breaks down on the Win 10 PC.
I *think* that it happened once without RU being open at all. I don't think that RU is the cause of the problem here, BUT it increases the frequency of the problem from days to minutes!
I think that Viewer cannot connect because of a DNS issue on that computer, and not vice versa :) Note, that Viewer and Host also require DNS resolution to work properly if you use the Internet-ID connection type.
In other words you should figure out why DNS resolution fails after some time on that computer. Even if running a Viewer somehow triggers that process, there must be a root cause for that. If you use your ISP's (default) DNS servers you can change them to Google's , or any other publicly available and proven DNS servers.
When running RU Viewer, I regularly get a complete loss of internet on my machine. I cannot access the internet from ANY program/app (browsers, RU Viewer etc). I am still connected to the WiFi, but it's as if there is no connection to the outside world. The timing varies, but on average RU will work perfectly for about 10 mins before the whole thing cuts out!
Is it only if you run the Viewer (the app) or actually log in/connect to a remote computer with it?
For now I can recommend that you reset the DNS resolver cache on the Win 10 computer and see if it fixes the issue. Hit Win + R and type the following command:
How can I configure the system so that after the Host is re-booted it will re-connect to the Viewer?
I'm afraid there is a contradiction. You mentioned that you needed unattended support and yet you set the Host service to start manually. With that setting on the Host won't start after the reboot unless someone on the remote side starts it (Windows Start menu -> Start Remote Utilities Host).
Perhaps, what you are really looking for is the Ask User Permission option. When this option is enabled the remote user's explicit consent is required to actually start a remote session even if the Host service starts automatically with Windows (which is the default option).
In the Viewer interface you can set scaling (see options on the toolbar - Normal, Stretch etc.) that is you can shrink the remote image to fit the bounds of your Viewer monitor. However, if you want to change the very resolution of the remote screen you will have to do that on the remote desktop itself, that is by accessing the Windows "Display settings" menu.
In the future though we might add an option to change the remote screen resolution from within the Viewer.