Suggesting Automatic (Delayed Start) for MeshAgent Service to Prevent Startup Issues After Reboot

[blown5]

Dear MeshCentral Development Team,

First of all, thank you for your continued efforts in maintaining and improving this excellent project.

We have encountered a recurring issue on multiple Windows systems where the MeshCentral Agent service sometimes fails to start automatically after a system reboot. This has been observed across different versions of Windows and hardware configurations.

After some investigation and testing, we found that changing the service startup type from "Automatic" to "Automatic (Delayed Start)" resolves the issue consistently. This adjustment allows the service to start reliably after other essential system services have initialized, preventing timing-related startup failures.

As a temporary workaround, we have manually applied this change to our deployments. However, we believe this adjustment could benefit the wider community if implemented directly in the agent installation or service configuration code.

Would it be possible to consider modifying the agent installer or service registration code to use "Automatic (Delayed Start)" as the default startup type for the MeshAgent service on Windows systems?

Thank you for your time and consideration.

[si458]

i have moved this to the correct repo as the service startup type is part of the meshagent source code and not meshcentral