Identify the failure mode
Run Get-Service and Get-WinEvent against the affected service. Note the exact error code and whether the service starts manually, after reboot or under a different account.
Check dependencies
Use sc.exe qc ServiceName and Get-Service -Name ServiceName -RequiredServices. A dependency that is stopped or misconfigured can prevent the target service from starting.
Validate the service account
Check password expiration, logon rights, account lockout and access to required folders, certificates, registry keys and network resources. Avoid changing the service account simply to make the error disappear.
Review Event Viewer
Focus on System, Application and the product-specific event log around the failure timestamp. Match the service start failure to DLL, authentication, permission or dependency errors.
Check ports and resources
Use Get-NetTCPConnection and netstat -ano to identify port conflicts. Also check disk space, memory and file permissions.
Recovery validation
After fixing the root cause, start the service and verify dependent applications. Reboot only when required by the product or configuration.
Explore more TechRunbook guides
Browse practical troubleshooting guides, PowerShell scripts, checklists and infrastructure resources for your environment.
Browse all articles →