Bird
Raised Fist0
PowerShellscripting~5 mins

Process management (Get/Stop-Process) in PowerShell

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction

Process management helps you see and control programs running on your computer. You can find and stop programs easily.

You want to check if a program is running before starting it again.
You need to stop a program that is frozen or not responding.
You want to see all running programs to understand what your computer is doing.
You want to stop a background task that is using too much memory.
You want to automate closing certain programs at a specific time.
Syntax
PowerShell
Get-Process [-Name <string[]>] [-Id <int[]>]
Stop-Process [-Name <string[]>] [-Id <int[]>] [-Force]

Get-Process shows running programs by name or ID.

Stop-Process stops a program by name or ID. Use -Force to stop it immediately.

Examples
Shows all running processes on your computer.
PowerShell
Get-Process
Shows only the Notepad program if it is running.
PowerShell
Get-Process -Name notepad
Stops the Notepad program safely.
PowerShell
Stop-Process -Name notepad
Forces the process with ID 1234 to stop immediately.
PowerShell
Stop-Process -Id 1234 -Force
Sample Program

This script shows all running Notepad processes, stops them, then tries to show them again to confirm they stopped.

PowerShell
Write-Host "List of running Notepad processes:"
Get-Process -Name notepad

Write-Host "Stopping all Notepad processes..."
Stop-Process -Name notepad

Write-Host "Notepad processes after stopping:"
Get-Process -Name notepad -ErrorAction SilentlyContinue
OutputSuccess
Important Notes

If you try to stop a process that is not running, PowerShell shows an error unless you use -ErrorAction SilentlyContinue.

Use Get-Process to find the exact name or ID of the process before stopping it.

Stopping system processes can cause your computer to crash. Only stop processes you know.

Summary

Get-Process shows running programs by name or ID.

Stop-Process stops programs safely or forcefully.

Use these commands to control programs running on your computer easily.

Practice

(1/5)
1. What does the PowerShell command Get-Process do?
easy
A. Lists all running processes on the computer
B. Stops a running process immediately
C. Starts a new process
D. Deletes a file from the system

Solution

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

    The command Get-Process is used to display information about processes currently running on the computer.
  2. Step 2: Compare options with command function

    Only Lists all running processes on the computer correctly describes listing running processes. Other options describe different actions not related to Get-Process.
  3. Final Answer:

    Lists all running processes on the computer -> Option A
  4. Quick Check:

    Get-Process lists processes = A [OK]
Hint: Get-Process always shows running programs, not stopping them [OK]
Common Mistakes:
  • Confusing Get-Process with Stop-Process
  • Thinking Get-Process starts or deletes processes
  • Assuming it modifies processes instead of listing
2. Which of the following is the correct syntax to stop a process named 'notepad' in PowerShell?
easy
A. Stop-Process notepad -Force
B. Get-Process -Stop notepad
C. Kill-Process -Name notepad
D. Stop-Process -Name notepad

Solution

  1. Step 1: Identify correct cmdlet and parameter

    The cmdlet to stop a process is Stop-Process. The parameter to specify process by name is -Name.
  2. Step 2: Validate syntax correctness

    Stop-Process -Name notepad uses correct cmdlet and parameter: Stop-Process -Name notepad. Get-Process -Stop notepad uses wrong cmdlet and parameter. Stop-Process notepad -Force misses the parameter name before 'notepad'. Kill-Process -Name notepad uses a non-existent cmdlet.
  3. Final Answer:

    Stop-Process -Name notepad -> Option D
  4. Quick Check:

    Stop-Process with -Name is correct syntax = C [OK]
Hint: Use Stop-Process with -Name to stop by process name [OK]
Common Mistakes:
  • Omitting the -Name parameter
  • Using incorrect cmdlet names like Kill-Process
  • Placing process name without parameter name
3. What will be the output of this PowerShell command?
Get-Process -Name powershell | Stop-Process -PassThru
medium
A. Lists all running PowerShell processes without stopping them
B. Stops the PowerShell process and outputs the stopped process details
C. Throws an error because Stop-Process cannot be piped
D. Starts a new PowerShell process

Solution

  1. Step 1: Understand the pipeline usage

    The command gets the process named 'powershell' and pipes it to Stop-Process. The -PassThru parameter makes Stop-Process output the stopped process object.
  2. Step 2: Predict command behavior

    The process will be stopped, and its details will be shown as output. No error occurs because piping is supported.
  3. Final Answer:

    Stops the PowerShell process and outputs the stopped process details -> Option B
  4. Quick Check:

    Get-Process piped to Stop-Process with -PassThru stops and outputs = B [OK]
Hint: Stop-Process supports pipeline input and -PassThru outputs stopped process [OK]
Common Mistakes:
  • Thinking Stop-Process cannot accept pipeline input
  • Assuming it only lists processes without stopping
  • Confusing -PassThru as a force stop
4. You run this command but get an error:
Stop-Process -Name

What is the problem and how to fix it?
medium
A. The command should be Get-Process -Name instead
B. Stop-Process does not use -Name; use -Id instead
C. Missing process name after -Name; add the process name
D. Stop-Process requires -Force parameter always

Solution

  1. Step 1: Identify the error cause

    The command uses -Name parameter but does not specify the process name, causing a syntax error.
  2. Step 2: Correct the command

    To fix, provide the process name after -Name, for example: Stop-Process -Name notepad.
  3. Final Answer:

    Missing process name after -Name; add the process name -> Option C
  4. Quick Check:

    Parameter -Name needs a value = D [OK]
Hint: Always provide a value after -Name parameter [OK]
Common Mistakes:
  • Leaving -Name without a value
  • Assuming -Force is always required
  • Confusing Stop-Process with Get-Process
5. You want to stop all running instances of 'chrome' safely but only if they use more than 100 MB of memory. Which PowerShell command achieves this?
hard
A. Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100000000 } | Stop-Process
B. Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100MB } | Stop-Process
C. Stop-Process -Name chrome -MemoryLimit 100MB
D. Get-Process chrome | Stop-Process -MemoryUsage 100MB

Solution

  1. Step 1: Understand memory property and filtering

    The WorkingSet property shows memory usage in bytes. 100 MB equals 100,000,000 bytes approximately.
  2. Step 2: Filter processes by memory and stop them

    Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100000000 } | Stop-Process correctly filters chrome processes with memory usage greater than 100,000,000 bytes and pipes them to Stop-Process. Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100MB } | Stop-Process uses '100MB' which is invalid syntax. Options C and D use non-existent parameters.
  3. Final Answer:

    Get-Process -Name chrome | Where-Object { $_.WorkingSet -gt 100000000 } | Stop-Process -> Option A
  4. Quick Check:

    Memory in bytes filter with Where-Object = A [OK]
Hint: Memory is in bytes; use numeric value, not '100MB' string [OK]
Common Mistakes:
  • Using '100MB' as a value instead of bytes
  • Trying to use Stop-Process parameters that don't exist
  • Not filtering processes before stopping