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.