So Zachary gave me the suggestion : My guess would be the first Windows host stopped communicating because the Launcher process stopped running. Did you install it as a service or just start it from the command line? Is it also possible you restarted the Fleet server with a different certificate? It's possible this would have caused the certificate verification error to start occurring on that first host in addition to the new host.