Windows Server: Restart a Service Safely (or Server Not Responding)
By OdooBot
· Published 02/07/2026
· 2 views
Windows Server: Restart a Service Safely (or Server Not Responding)
Category: Windows Server · Audience: Technicians · Est. time: 5–20 min
Summary
Restarting a stuck Windows service often fixes an app outage without rebooting the whole server. This covers doing it safely and what to try when the server itself is unresponsive.
⚠️ Confirm with BBN before restarting production services/servers in business hours. Know what depends on the service (e.g. restarting SQL drops app connections).
Restart a service
- Open services.msc. Find the service (e.g. Print Spooler, World Wide Web Publishing, SQL Server (INSTANCE), a line‑of‑business service).
- Note its Startup type should be Automatic. Right‑click → Restart (or Stop then Start).
- If it won't stop ("stopping" forever), find its PID: Task Manager → Services tab → right‑click → Go to details, then end the process only if safe.
- Check Event Viewer → Application/System for why it failed — a crashing service that keeps stopping needs root‑cause, not just a restart.
PowerShell (optional)
Get-Service -Name W3SVC | Restart-Service
Restart-Service -Name "MSSQL$INSTANCE" -Force # be careful: drops connections
Server not responding at all
- Can you reach it?
ping <server>and try RDP. No RDP but ping works → a service/session issue, not fully down. - Console access: use iDRAC/iLO/IPMI (Dell/HPE out‑of‑band), the hypervisor console (Hyper‑V/VMware), or on‑site keyboard/monitor.
- High load: if you can get in, check Task Manager for a runaway process pinning CPU/RAM; end it if safe.
- Last resort — reboot: only after confirming there's no in‑progress job (backup, update, DB operation) and BBN/the customer is aware. Prefer a graceful restart over a hard power cycle.
If that doesn't work
- Repeated service crashes → capture the Event ID and error; check disk space and pending updates.
- Escalate to BBN Support with the server name, the service, and the event log detail.
Prevention
- Set critical services to Automatic (Delayed Start) where appropriate; monitor them so a stop alerts BBN before users notice.
Didn't find what you were looking for?
Submit a Ticket