How do I inspect and restart one Windows server service?
Use the exact service name, inspect its state and dependencies, and restart only when the interruption is authorised. A service reporting Running does not by itself prove that its application is healthy.
Before you start
- Administrative rights and approval for interruption of the exact service.
Instructions
1. Inspect the intended service
Replace ExampleAppService with the approved actual service name, not a broad wildcard.
Get-Service -Name 'ExampleAppService' | Select-Object Name, Status, ServicesDependedOn, DependentServicesReview dependencies and the current state before scheduling a restart.
2. Preview and then run the authorised restart
The preview does not stop the service. Run the second command only within the approved change scope.
Restart-Service -Name 'ExampleAppService' -WhatIf
Restart-Service -Name 'ExampleAppService'The real command stops and starts only the named service. It deliberately omits -Force so dependency conflicts need explicit review.
3. Verify service and application behaviour
Check both Windows service state and the application’s own health endpoint or normal transaction.
Get-Service -Name 'ExampleAppService'If it does not remain Running, inspect relevant event and application logs rather than repeatedly restarting it.
Check the result
- The exact target service reaches its expected stable state.
- Its application-level check succeeds and dependent functionality remains available.
Troubleshooting
- A dependency prevents restart
- Review the dependency chain and service owner’s procedure; do not add -Force blindly.
- The service stops again
- Inspect event logs and application errors for the actual cause before another restart.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.