| Previous | Next |
| ERROR_RUNLEVEL_SWITCH_IN_PROGRESS | ERROR_COM_TASK_STOP_PENDING |
ERROR_SERVICES_FAILED_AUTOSTART
The automatic service-start phase contains one or more failed services
This status is an aggregate startup result: at least one service failed during the service-start phase of a run-level transition. It does not identify which service failed or provide the underlying service-specific exit code. SCM startup ordering can involve load-order groups, tag ordering, and service dependencies.
Enumerate or query the services involved in the transition and inspect each service state and Win32/service-specific exit code. Correlate System event log entries from the same startup interval. Start with dependency roots and critical auto-start services, because a single prerequisite failure can prevent several dependents from starting. Do not repeatedly restart all services as one batch before collecting individual results; doing so destroys the ordering and timing evidence needed to identify the first failure.
What to inspect
- Collect individual service states and exit codes for the failed startup interval.
- Walk dependency and load-order relationships to find the earliest prerequisite failure.
- Correlate SCM/System events before retrying the whole startup phase.
References
- Microsoft: Automatically Starting Services
- Microsoft: QueryServiceStatusEx
- Microsoft: Service Control Manager
Looking for a different code? Search another status or error code.