Services & startup troubleshooting
Service startup failures, dependencies, background conflicts, app/service crashes and boot-time evidence.
Identify the exact service name, current state, startup type, dependency chain and matching Service Control Manager event before changing service configuration.
Use clean boot, app/service crash evidence or vendor support only after you know whether the failure is a dependency, executable/configuration problem, crash or third-party startup conflict.
Preserve the service name, display name and the feature/app that depends on it.
Check whether it is stopped, disabled, delayed, or failing during a start attempt.
A dependent service can fail even when the visible service is not the original fault.
Match the Service Control Manager event, error text and timestamp to the failed start.
If the service starts then terminates, correlate Application Error/WER records rather than changing startup type.
Use a clean boot for suspected third-party conflicts, then restore normal startup when testing is complete.
Windows service won’t start: identify state, dependency and Service Control Manager evidence first
Troubleshoot a Windows service that refuses to start without blindly changing startup types or registry service entries.
Use a clean boot to isolate a background service or startup-app conflict in Windows 11
A controlled clean boot can prove whether a non-Microsoft service or startup app is involved without turning permanent service changes into the diagnosis.
Windows 11 starts slowly: build a startup evidence timeline before disabling services
Separate boot delay, sign-in delay and post-desktop startup load, then correlate recent changes and startup items before broad service changes.
Error records in this system
Service Control Manager: a service failed to start
Use the named service and complete error text to determine whether the failure is timeout, configuration, binary, permission or another service-specific cause.
Open error record →Windows clientEvent ID 7001Service Control Manager: dependency service failed to start
A higher-level service can fail because one of its required services failed first; trace the dependency chain instead of repairing only the visible service.
Open error record →Commands used in this system
Get-Service
Get-ServiceList Windows service objects and their current status; specific service names can be queried and required/dependent services can also be inspected.
Low riskSC Query
sc.exe query <ServiceName>Display status and service-control information for a named Windows service or driver service.
Low riskGet-WinEvent — Service Control Manager
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Service Control Manager'; StartTime=(Get-Date).AddHours(-24)}Read recent Service Control Manager events efficiently from the System log so service-start/dependency/crash timing can be correlated.
Medium riskSystem Configuration (MSConfig)
msconfigOpen System Configuration, including the service/startup controls Microsoft uses in its clean-boot troubleshooting procedure.