Custom error messages in PowerShell - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of custom error messages in PowerShell scripts?

Custom error messages help make errors clearer and easier to understand by providing specific information about what went wrong, instead of generic system errors.

beginner

How do you create a custom error message in PowerShell using try/catch?

Use a try block to run code that might fail, and a catch block to handle errors. Inside catch, use Write-Error or throw with a custom message to show your own error text.

beginner

What PowerShell keyword lets you stop script execution and show a custom error?

The 'throw' keyword stops the script and displays a custom error message you provide.

intermediate

Why is it helpful to include variable values in custom error messages?

Including variable values helps you understand the exact data that caused the error, making it easier to fix problems.

beginner

Show a simple PowerShell example of a custom error message using try/catch.

try { Get-Item 'C:\nonexistentfile.txt' } catch { Write-Error "File not found: $_" }

Which PowerShell block is used to catch errors and handle them?

A catch

B try

C finally

D begin

The catch block runs when an error occurs inside the try block, allowing you to handle the error.

What does the 'throw' keyword do in PowerShell?

A Logs errors silently

B Ignores errors and continues

C Stops script execution and shows a custom error message

D Retries the command

Throw stops the script and displays the error message you provide.

How can you include the original error message inside your custom error message?

A Use the automatic variable $_ inside catch

B Use Write-Host outside catch

C Use Get-Error cmdlet

D Use the $Error variable outside catch

Inside catch, $_ holds the error object, which you can include in your message.

Why use custom error messages instead of default ones?

A To hide errors from users

B To make errors clearer and easier to fix

C To slow down the script

D To avoid using try/catch

Custom messages explain the problem in simple terms, helping fix issues faster.

Which command writes an error message but does not stop the script?

A exit

B throw

C break

D Write-Error

Write-Error shows an error message but lets the script continue running.

Explain how to use try/catch in PowerShell to create a custom error message.

Think about how to run risky code and handle errors with your own text.

Describe why custom error messages improve script debugging and user experience.

Imagine telling a friend exactly what went wrong instead of a confusing error.

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