Community

Afternoon,

It seems from reading this thread  I am experiencing the same issues whereby a reboot of host following Windows Updates (not limited to a specific one in particular)  or any reboot in particular laur on Windows Server 2019 the Host fails to start requires a Start>>Remote Utilities Host >> Start Host to get things up and running again. (I have also followed Host service won't start

The Host file doesn't lend any clues on failures just successful connections.

However in Windows Event Log



Seems to be the same errors Peter Gray identified in this separate topic which he refers to in this post Peter Grays Post

Pleased to see a fix has been identified.

The timeout error is interesting.
If the host is trying to start, and there is some dependency service that is not yet running, I guess that is a possible source for the issue, but in my case, I have previously tried setting the service recovery options to Restart the Service for 1st, 2nd and subsequent failures, but this was not effective in resolving the problem. Only a manual start request seemed to ever work.

Matthew

Matthew Cooper wrote:

The timeout error is interesting.
If the host is trying to start, and there is some dependency service that is not yet running, I guess that is a possible source for the issue, but in my case, I have previously tried setting the service recovery options to Restart the Service for 1st, 2nd and subsequent failures, but this was not effective in resolving the problem. Only a manual start request seemed to ever work.

Matthew

Hi Matthew. Yup only a manual start will get it going again

Same here it had to be a manual start, that’s why this fix were using in the task scheduler is working so well..

There is another issue that accompanies this for us, I am unsure if it is part of the same problem, and it is less common than the startup problem.

We notice it on hosts that run for long periods of time without reboots, sometimes the host will go offline in the viewer, and the icon on the host machine will turn grey. Attached are screenshots from 1 such host currently. In this case, the RU service is running. If I manually restart the service, the host will come back online, and is then I can connect. But it will not recover on its own. We do not have logging enabled on the host machines so I do not have any information to accompany this.

This occured again when we updated our computers with windows update the update number was KB5011831
It was pretty big and after doing the update the host on all the machines failed to start up again, Luckaly we used the fix thats re-started the host every hour if not running..
Just a heads up which update did it this time.. It was for windows 10 machines..