Custom error messages in PowerShell - Step-by-Step Execution

Concept Flow - Custom error messages

Start Script

↓

Try Block: Run code

↓

Error Occurs?

No→Continue Normal Execution

Yes↓

Catch Block: Capture error

↓

Display Custom Error Message

↓

End Script

The script tries to run code. If an error happens, it catches it and shows a custom message instead of the default error.

Execution Sample

PowerShell

try {
  Get-Item 'C:\NoSuchFile.txt'
} catch {
  Write-Host "Oops! File not found. Please check the path."
}

This script tries to get a file. If the file is missing, it shows a friendly custom error message.

Execution Table

Step	Action	Evaluation	Result
1	Try to get file 'C:\NoSuchFile.txt'	File exists?	No, file not found error occurs
2	Catch block activated	Capture error	Error captured
3	Display custom message	Write-Host executed	Output: Oops! File not found. Please check the path.
4	Script ends	No further code	Execution stops

💡 File not found error triggers catch block, custom message displayed, script ends

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
Error	None	FileNotFoundException	Captured in catch	Handled with custom message

Key Moments - 2 Insights

Why does the script not show the default error message?

Because the error is caught in the catch block (see execution_table step 2), the script shows the custom message instead.

What happens if the file exists?

The try block succeeds without error, so the catch block is skipped and no custom message is shown.

Visual Quiz - 3 Questions

Look at the execution table, what is the output at step 3?

A Oops! File not found. Please check the path.

B File found successfully.

C Default error message.

D No output.

💡 Hint

Check the 'Result' column in execution_table row for step 3.

At which step does the script detect the error?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Evaluation' column in execution_table for step 1.

If the file exists, which step is skipped?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Catch block runs only if error occurs (see concept_flow).

Concept Snapshot

try { <code> } catch { <custom message> }

- Runs code inside try
- If error, catch runs
- Show friendly message
- Prevents default error output

Full Transcript

This PowerShell script tries to get a file. If the file is missing, an error happens. The catch block catches this error and shows a custom message: 'Oops! File not found. Please check the path.' This stops the default error from showing. If the file exists, the catch block is skipped and no message is shown. This helps make scripts friendlier and easier to understand.

Practice

1. What is the main purpose of using custom error messages in PowerShell scripts?

easy

A. To hide all errors from the user

B. To make the script run faster

C. To make error messages clearer and easier to understand for users

D. To automatically fix errors without user input

Solution

1. Step 1: Understand the role of error messages

   Error messages help users know what went wrong in a script.

2. Step 2: Identify the benefit of custom messages

   Custom messages explain errors in simple words, making them easier to fix.

3. Final Answer:

   To make error messages clearer and easier to understand for users -> Option C

4. Quick Check:

   Custom error messages improve clarity = A [OK]

Hint: Custom messages explain errors simply for users [OK]

Common Mistakes:

• Thinking custom messages speed up scripts
• Believing errors should be hidden completely
• Assuming errors fix themselves automatically

2. Which of the following is the correct syntax to catch an error and display a custom message in PowerShell?

easy

A. try { command } finally { Write-Host 'Error occurred' }

B. catch { command } try { Write-Host 'Error occurred' }

C. try command catch Write-Host 'Error occurred'

D. try { command } catch { Write-Host 'Error occurred' }

Solution

1. Step 1: Recall try-catch syntax

   PowerShell uses try { } catch { } blocks to handle errors.

2. Step 2: Identify correct placement of Write-Host

   The custom message should be inside the catch block to show on error.

3. Final Answer:

   try { command } catch { Write-Host 'Error occurred' } -> Option D

4. Quick Check:

   try-catch with message in catch = A [OK]

Hint: Put custom message inside catch block [OK]

Common Mistakes:

• Swapping try and catch blocks
• Using finally instead of catch for errors
• Missing curly braces around blocks

3. What will be the output of this script?

try {
  Get-Item 'C:\nonexistentfile.txt'
} catch {
  Write-Host 'File not found, please check the path.'
}

medium

A. Get-Item : Cannot find path 'C:\nonexistentfile.txt' because it does not exist.

B. File not found, please check the path.

C. No output, script runs silently

D. Syntax error in script

Solution

1. Step 1: Understand Get-Item behavior

   Get-Item throws an error if the file does not exist.

2. Step 2: Check catch block output

   The catch block catches the error and prints the custom message.

3. Final Answer:

   File not found, please check the path. -> Option B

4. Quick Check:

   Error caught and custom message shown = C [OK]

Hint: Catch block shows custom message on error [OK]

Common Mistakes:

• Expecting default error instead of custom message
• Thinking script runs silently without output
• Confusing syntax error with runtime error

4. Identify the error in this script that tries to show a custom error message:

try {
  Get-Content 'missingfile.txt'
} catch {
  Write-Host Error: File missing
}

medium

A. Missing quotes around the error message string

B. Incorrect use of Get-Content command

C. No catch block present

D. Try block syntax is wrong

Solution

1. Step 1: Check catch block syntax

   Write-Host requires the message to be a string inside quotes.

2. Step 2: Identify missing quotes

   Error: File missing is not quoted, causing a syntax error.

3. Final Answer:

   Missing quotes around the error message string -> Option A

4. Quick Check:

   Strings need quotes in Write-Host = D [OK]

Hint: Always quote strings in Write-Host [OK]

Common Mistakes:

• Forgetting quotes around text
• Assuming Get-Content is wrong here
• Thinking catch block is missing

5. You want to create a script that reads a file and shows a custom error message only if the file is missing, but lets other errors pass through. Which approach is best?

hard

A. Use try-catch and check if the error is 'ItemNotFoundException' before showing custom message

B. Use try-catch and always show the same custom message for any error

C. Use only try block without catch to let errors show normally

D. Use catch block to ignore all errors silently

Solution

1. Step 1: Understand error filtering in catch

   PowerShell catch blocks can check error types to handle specific errors.

2. Step 2: Apply condition for missing file error

   Check if error is 'ItemNotFoundException' to show custom message only for missing files.

3. Final Answer:

   Use try-catch and check if the error is 'ItemNotFoundException' before showing custom message -> Option A

4. Quick Check:

   Filter error type in catch for custom message = B [OK]

Hint: Check error type in catch to customize messages [OK]

Common Mistakes:

• Showing same message for all errors
• Ignoring errors silently
• Not using catch block at all