Hello,
Yes this occurs on all 30 boxes that we have metricbeat installed on.
Again it is just when windows starts up that it occurs. If I start the
service manually it works. Also as a work around I created a task
scheduler job with 'on startup' as criteria that calls a batch script with
just 'net start metricbeat'. I added a 1 minute delay on when to run.
This will start up the metricbeat service successfully on reboot.