Every failed `sc.exe start` was reported with "a service that exits immediately
usually cannot read its config", which for the one error code that actually
occurs is the wrong place to look. 1053 is the SCM giving up after 30 seconds
waiting for the process to identify itself; the process started fine and is
very likely serving traffic. A reader who follows the old sentence goes and
stares at a config file that is correct.
Replace it with windows_start_failure(), which names the real cause per code:
- 1053: a handshake failure, almost always a sidecar older than v1.2.0 (the
first release that speaks the SCM protocol). Says how to check the version,
and how to prove the binary is healthy by running it in the foreground.
- 1069: the virtual service account was refused, which is local policy rather
than a bad credential, and points at INSTALL.md Appendix A4.
- anything else: does not guess, and hands over the event log, `sc query` for
the service's own exit code, and the foreground command.
Pure and tested on both platforms, like windows_bin_path above it, so the text
is covered on the Linux CI runner that never sees an SCM.
Co-Authored-By: Claude <noreply@anthropic.com>
