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

Concept Flow - Process management (Get/Stop-Process)

Start

↓

Get-Process

↓

Filter process by name or ID

↓

Decide: Stop process?

↓

Stop-Process

↓

Confirm process stopped

↓

End

This flow shows how to get running processes, optionally stop one, and confirm the action.

Execution Sample

PowerShell

Get-Process -Name notepad
Stop-Process -Name notepad

This code gets the Notepad process and then stops it.

Execution Table

Step	Command	Action	Result	Output
1	Get-Process -Name notepad	Retrieve process info	Process found	Handles: 50, Id: 1234, Name: notepad
2	Stop-Process -Name notepad	Stop the process	Process stopped	No output (process terminated)
3	Get-Process -Name notepad	Check if process exists	Process not found	Error: Cannot find a process with the name 'notepad'.

💡 Process 'notepad' stopped, so subsequent Get-Process fails to find it.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
ProcessExists	Unknown	True	False	False

Key Moments - 2 Insights

Why does Get-Process fail after Stop-Process?

Because Stop-Process terminates the process, so it no longer exists. See execution_table step 3 where Get-Process cannot find 'notepad'.

Can Stop-Process be used without Get-Process first?

Yes, but using Get-Process first helps confirm the process is running before stopping it, as shown in step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the output of step 1?

A Process info with Id and Name

B No output

C Error: Process not found

D Process stopped confirmation

💡 Hint

Check the Output column in execution_table row 1.

At which step does the process stop existing?

A Step 1

B Step 2

C Step 3

D Process never stops

💡 Hint

Look at the Action and Result columns in execution_table step 2.

If you skip Stop-Process, what would step 3 output be?

A Error: Process not found

B No output

C Process info with Id and Name

D Process stopped confirmation

💡 Hint

Refer to variable_tracker showing ProcessExists remains True if not stopped.

Concept Snapshot

Get-Process retrieves running processes by name or ID.
Stop-Process terminates a running process.
Use Get-Process first to confirm process exists.
After stopping, Get-Process will fail to find it.
Commands require appropriate permissions.
Always confirm process before stopping to avoid errors.

Full Transcript

This lesson shows how to manage processes in PowerShell using Get-Process and Stop-Process. First, Get-Process finds running processes by name, showing details like process ID. Then, Stop-Process can terminate a process by name or ID. After stopping, the process no longer exists, so Get-Process will fail to find it. This helps safely manage running programs. The execution table traces these steps with outputs. Variable tracking shows the process existence changing from true to false after stopping. Key moments clarify why Get-Process fails after stopping and the benefit of checking first. The quiz tests understanding of outputs and process state changes. Remember to run these commands with proper permissions and confirm the process before stopping it.

Practice

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