launcher missing shutdown logs on Windows

[RebeccaMahany]

Oftentimes on Windows we miss all of launcher's shutdown logs -- e.g. going right from regular launcher logs to a gap of a couple seconds, then launching service and windows service starting. There's nothing illuminating in the event logs, either. This makes it really tough to figure out why launcher is shutting down unexpectedly.

We should get logs about rungroups shutting down, or goroutines panicking, or the service shutting down. It is not clear to me why these logs are missing.

[James-Pickett]

To add on to this, we've seen some errors like this

{
  "time": "2025-01-18T02:34:00.256122Z",
  "level": "INFO",
  "msg": "runLauncher exited",
  "err": "run service: execute panicked: runtime error: index out of range [0] with length 0",
  "stack_trace": "run service: execute panicked: runtime error: index out of range [0] with length 0\nmain.(*winSvc).Execute.func1\n\tD:/a/launcher/launcher/cmd/launcher/svc_windows.go:189\ngithub.com/kolide/launcher/ee/gowrapper.Go.func1\n\tD:/a/launcher/launcher/ee/gowrapper/goroutine.go:33\nruntime.goexit\n\tC:/hostedtoolcache/windows/go/1.22.9/x64/src/runtime/asm_amd64.s:1695"
}

where the stack trace only goes back to svc_windows.go:189 but doesn't tell us what line or what service actually panicked

edit:

this log came from windows event log, so perhaps it's less relevant