How to Use Windows PowerShell ‘Get-Service’ and ‘Restart-Service’ for System Management

The Slow GUI Workflow

Background services are the heart of the Windows operating system. They handle everything from the Print Spooler (which manages your printers) to the Windows Update engine.

When a printer stops working, the standard IT response is to press Win + R, type services.msc, scroll down a massive alphabetical list to find “Print Spooler,” right-click it, and select “Restart.”

This graphical workflow is slow, and more importantly, it cannot be automated. If a specific database service crashes every night at 2:00 AM, you cannot script services.msc to fix it.

To programmatically monitor and control background services, Windows administrators use the PowerShell cmdlets: Get-Service, Start-Service, Stop-Service, and Restart-Service.

1. Auditing Services (Get-Service)

To see the exact state of a specific service, open PowerShell and type:

Get-Service -Name Spooler

This returns a clean object showing the Status (Running, Stopped, or Paused), the internal Name (Spooler), and the human-readable DisplayName (Print Spooler).

Filtering by Status

If a server is behaving erratically, you might want to see a list of every service that is currently stopped, but is supposed to be running automatically.

Get-Service | Where-Object {$_.Status -eq "Stopped" -and $_.StartType -eq "Automatic"}

This single line of code instantly filters out hundreds of irrelevant services and highlights exactly which critical system components have crashed.

2. Restarting a Service

If the Print Spooler is frozen, you don’t need to open the GUI. You simply pipe the service object directly into the Restart-Service cmdlet.

(Note: Starting or stopping system services requires Administrator privileges. Ensure your PowerShell window is running as Admin).

Restart-Service -Name Spooler -Force

The -Force flag tells Windows to aggressively kill the service and restart it, even if other minor services depend on it.

3. Managing Services on Remote Computers

This is where PowerShell truly outclasses the graphical interface. If a user on the third floor calls the helpdesk because their software updater crashed, you don’t need to walk to their desk or initiate a remote desktop session.

You can manage their services remotely from your own terminal (assuming your enterprise environment has PSRemoting enabled).

Get-Service -Name wuauserv -ComputerName "HR-DESKTOP-04" | Restart-Service

This command queries the Windows Update service (wuauserv) on the remote computer and instantly restarts it over the network.

4. Automating Crash Recovery

If a legacy application has a memory leak and its background service crashes frequently, you can write a simple PowerShell script to act as a watchdog.

$service = Get-Service -Name "LegacyAppService"

if ($service.Status -ne "Running") {
    Start-Service -Name "LegacyAppService"
    Write-EventLog -LogName Application -Source "WatchdogScript" -EventId 1001 -Message "LegacyAppService was found stopped and was restarted."
}

If you attach this script to the Windows Task Scheduler and set it to run every 5 minutes, it will automatically heal the broken application and log the failure without any human intervention.

Conclusion

The Get-Service suite of cmdlets allows administrators to discard the slow, manual services.msc utility. By treating background services as queryable, scriptable objects, IT professionals can build resilient servers that monitor themselves, automatically restart crashed dependencies, and report their health status in real-time.