Further info: Just updated another XP Host. This time I had not already connected to it with the Viewer before doing the update, and no user was logged onto it. I still got the error popup, but the thing with three Host icons did not happen. Just the one there after I had connected and logged in as a user.
On all the machines where I have updated the Host to v 22.214.171.124 from 126.96.36.199 or 188.8.131.52, using remote install with Remote Utilities security, the host pops up an error message However, the update seems to complete, and I can connect to the host afterwards. In the icon tray I then find two red and one blue host icons. The blue and one red one disappear if I mouse over them, the second red is the active connection. So it looks as if the error was not really fatal, and the remote install had a second try. In all the cases I have checked, the file was present after the update. All the hosts were on Windows 7 except one which was on XP This error did not happen when I updated a 6.10. beta 4 host to 184.108.40.206.
Thar reminds me:on my XP Viewer machine at v 220.127.116.11, if I right click anywhere in either of the explorer panes in the file transfer window, the entire screen goes white. Rather scary the first time it happened, but hitting escape key gets back to normal display. I can't remember what happened in v 18.104.22.168, and don't know what is supposed to happen.
Both machines where Host didn't autostart have Avast free antivirus, as do all my other personal machines. I have sometimes (but by no means often) had a false positive fr om it on downloading or installing or first time running new versions of Host and Viewer, but it has always let me create an exception. In any case, I don't think it's an antivirus issue, since I can stsrt the Host manually on both machines.
I do have a rather old version of Spybot Search and Destroy on those machines, which uses a lot of CPU during startup. Maybe that is causing the Host service to take too long responding to its start request. I could try disabling it and see what happens. The third machine I tried does not have Spybot S & D, and the host autostarted OK.
Other machines that I support have Avast Business AV, but that also lets me create exceptions if I get a false positive. However, some of those machines are also slow to start for various reasons, which makes me nervous about doing a remote machine restart. I have sometimes had to go in person to start the Host after a machine restart, or use an alternative remote access tool wh ere one is already installed.
I had noticed earlier this afternoon that the host was not running on the machine that I mostly use as viewer (which I re-started two days ago), so having then seen Karsten's post, I started up a couple of other local machines which had been shut down. In both cases the host did not start automatically, even though the service state in host properties was set to auto start. They worked fine after I manually started them. One is 32 bit XP, the other 64 bit W7.
Looking at the host logs, the host had been started immediately after upgrading to version 22.214.171.124.
Auto start was working OK on the recent 126.96.36.199 beta 4, though I recall that one of the recent betas fixed a problem with that. Has that fix been carried over correctly into 188.8.131.52?
On the other hand, I've just turned on another local machine, and its host *did* start automatically. Perhaps the problem is machine dependant, or doesn not happen every time. Does starting the host depend on any other services being already running, which might be slow starting?
I am also getting these errors. The host is version 184.108.40.206 on Windows 7 32 bit. The errors happen even with a direct connection. The host has both wired and WiFi connections in my local network. Problem still occurs if I disable WiFi. Problenn still occurs if I switch to Internet ID connection mode. Happens with 2 different viewers, one at version 220.127.116.11, the other still at beta 4. I am fairly sure this did not happen before upgrading the host to v 7 [cofirmed, problem started immediately after upgrading host to V 18.104.22.168, did not happen while host was at beta 4]
One behavioural difference: these errors happen about once a minute, but the viewer automatically re-connects to the host.