Service management (Get/Start/Stop-Service) in PowerShell - Step-by-Step Execution

Concept Flow - Service management (Get/Start/Stop-Service)

Start

↓

Get-Service

↓

Check service status

↓

Start-Service if stopped

↓

Stop-Service if running

↓

Confirm status

↓

End

This flow shows how to get a service, check its status, then start or stop it accordingly.

Execution Sample

PowerShell

$serviceStatus = (Get-Service -Name "wuauserv").Status
if ($serviceStatus -eq 'Stopped') {
  Start-Service -Name "wuauserv"
} else {
  Stop-Service -Name "wuauserv"
}
Get-Service -Name "wuauserv"

This script checks the Windows Update service status and starts it if stopped, otherwise stops it.

Execution Table

Step	Action	Service Status	Condition	Command Executed	Output
1	$serviceStatus = (Get-Service -Name 'wuauserv').Status	Running	N/A	Get-Service	Status: Running
2	Check if status is 'Stopped'	Running	False	Condition check	Skip Start-Service
3	Else branch: Stop-Service 'wuauserv'	Running	N/A	Stop-Service	Service stopping...
4	Confirm service status	Stopped	N/A	Get-Service	Status: Stopped

💡 Service status changed to Stopped, script ends.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
serviceStatus	N/A	Running	Running	Running	Stopped

Key Moments - 2 Insights

Why does the script check the service status twice?

The first check (Step 1) gets the current status. The second check (Step 4) confirms the status after starting or stopping the service, ensuring the command worked.

What happens if the service is already running?

At Step 2, the condition is false, so the script runs Stop-Service (Step 3) to stop it, as shown in the execution_table.

Visual Quiz - 3 Questions

Look at the execution table, what is the service status after Step 1?

A Stopped

B Paused

C Running

D Starting

💡 Hint

Check the 'Service Status' column in row for Step 1.

At which step does the script decide to stop the service?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Command Executed' column to find where Stop-Service runs.

If the service was initially stopped, which command would run?

A Start-Service

B Stop-Service

C Get-Service only

D No command

💡 Hint

Refer to the condition in Step 2 and the script logic in execution_sample.

Concept Snapshot

Get-Service retrieves service info.
Check service status property.
Start-Service starts a stopped service.
Stop-Service stops a running service.
Use conditions to decide which command to run.

Full Transcript

This example shows how to manage Windows services using PowerShell commands Get-Service, Start-Service, and Stop-Service. First, the script gets the status of the 'wuauserv' service. If the service is stopped, it starts it. Otherwise, it stops the service. The execution table traces each step, showing the service status and commands run. The variable tracker follows the service status change from running to stopped. Key moments clarify why the status is checked twice and what happens if the service is running. The quiz tests understanding of the service status at each step and the commands executed based on conditions.

Practice

1. What does the PowerShell command Get-Service do?

easy

A. It shows the status of services on the computer.

B. It starts a stopped service.

C. It stops a running service.

D. It deletes a service from the system.

Solution

1. Step 1: Understand the purpose of Get-Service

   The Get-Service command lists services and their current status (running or stopped).

2. Step 2: Compare with other commands

   Start-Service and Stop-Service change service states, but Get-Service only shows status.

3. Final Answer:

   It shows the status of services on the computer. -> Option A

4. Quick Check:

   Get-Service = Show service status [OK]

Hint: Get-Service always lists service status, not start or stop [OK]

Common Mistakes:

• Confusing Get-Service with Start-Service
• Thinking Get-Service stops services
• Assuming Get-Service deletes services

2. Which of the following is the correct syntax to start a service named 'Spooler' in PowerShell?

easy

A. Start-Service -Name Spooler

B. Get-Service -Start Spooler

C. Stop-Service -Name Spooler

D. Start-Service Spooler -Force

Solution

1. Step 1: Identify the correct cmdlet for starting a service

   Start-Service is used to start services, and it accepts the -Name parameter to specify the service.

2. Step 2: Check the syntax correctness

   Start-Service -Name Spooler is the correct syntax. Get-Service -Start Spooler uses wrong cmdlet and parameter, Stop-Service -Name Spooler stops service, and Start-Service Spooler -Force uses an invalid parameter -Force.

3. Final Answer:

   Start-Service -Name Spooler -> Option A

4. Quick Check:

   Start-Service -Name ServiceName = Start service [OK]

Hint: Use Start-Service with -Name to start a service [OK]

Common Mistakes:

• Using Get-Service to start a service
• Using Stop-Service instead of Start-Service
• Adding invalid parameters like -Force

3. What will be the output of this PowerShell command?

Get-Service -Name W32Time | Select-Object -Property Status

medium

A. Starts the W32Time service.

B. Displays the status (Running or Stopped) of the W32Time service.

C. Stops the W32Time service.

D. Shows an error because Select-Object cannot be used here.

Solution

1. Step 1: Understand Get-Service with Select-Object

   Get-Service -Name W32Time fetches the service object, and piping it to Select-Object -Property Status extracts only the status property.

2. Step 2: Determine the output

   The output will be a simple display showing the status of the W32Time service, such as Running or Stopped.

3. Final Answer:

   Displays the status (Running or Stopped) of the W32Time service. -> Option B

4. Quick Check:

   Get-Service + Select-Object = Show service status [OK]

Hint: Get-Service piped to Select-Object shows specific properties [OK]

Common Mistakes:

• Thinking it starts or stops the service
• Believing Select-Object causes an error here
• Confusing service name with command parameters

4. You run this command to stop the 'Spooler' service:

Stop-Service Spooler

But it fails with an error. What is the likely cause?

medium

A. You need to specify the parameter name: -Name before the service name.

B. The service is already stopped, so Stop-Service cannot run.

C. Stop-Service cannot stop the Spooler service.

D. You must run PowerShell as Administrator to stop services.

Solution

1. Step 1: Check command syntax

   Stop-Service Spooler is valid because the parameter -Name is positional and can be omitted.

2. Step 2: Consider permissions

   Stopping services usually requires administrator rights. Without running PowerShell as admin, the command fails with an error.

3. Final Answer:

   You must run PowerShell as Administrator to stop services. -> Option D

4. Quick Check:

   Stopping services needs admin rights [OK]

Hint: Run PowerShell as admin to stop services [OK]

Common Mistakes:

• Thinking -Name parameter is mandatory
• Assuming service must be running to stop
• Believing Spooler service cannot be stopped

5. You want to write a script that checks if the 'W32Time' service is stopped, and if so, starts it. Which script snippet correctly does this?

hard

A. Start-Service -Name W32Time -IfStopped

B. if (Get-Service W32Time -Status 'Stopped') { Start-Service W32Time }

C. $svc = Get-Service -Name W32Time
if ($svc.Status -eq 'Stopped') { Start-Service -Name W32Time }

D. $svc = Get-Service W32Time
if ($svc.Status = 'Stopped') { Start-Service W32Time }

Solution

1. Step 1: Retrieve the service object and check status

   Using $svc = Get-Service -Name W32Time stores the service object. Then $svc.Status -eq 'Stopped' correctly compares the status.

2. Step 2: Start the service if stopped

   If the status is 'Stopped', Start-Service -Name W32Time starts the service.

3. Final Answer:

   $svc = Get-Service -Name W32Time if ($svc.Status -eq 'Stopped') { Start-Service -Name W32Time } -> Option C

4. Quick Check:

   Check status with -eq, then start service [OK]

Hint: Use -eq to compare status, then Start-Service if stopped [OK]

Common Mistakes:

• Using single = instead of -eq for comparison
• Assuming Start-Service has -IfStopped parameter
• Trying to filter Get-Service with -Status parameter