Considering the amount of inputs to EnumServicesStatusEx and the number of properties that it returns (see SERVICE_STATUS_PROCESS), I'm afraid that it makes no sense for windows/svc/mgr to provide specific helpers for each combination of inputs and outputs. For example, why returning the status but not the service type?

You can already get what you want with a few lines of code, and it could be customized further if your requirements change, e.g. you want to filter out some service types.

nit: you could simplify a bit the last part of your code sample by changing it to:

services := unsafe.Slice((*windows.ENUM_SERVICE_STATUS_PROCESS)(unsafe.Pointer(&buf[0])), int(servicesReturned))
var n []nameAndState
for _, s := range services {
	name := windows.UTF16PtrToString(s.ServiceName)
	n = append(n, nameAndState{name: name, state: int(s.ServiceStatusProcess.CurrentState)})
}

@golang/windows

Thanks for the response @qmuntal and for the more readable code.
I agree that it makes no sense to provide helpers for each combination of fields - would you view the proposal more favourably if the suggestion was to keep the existing ListServices function as it is, and just have one more function that returns everything from SERVICE_STATUS_PROCESS? It would be up to the end user which fields they want to use then. The range on "services" should already have access to this data.