Custom error messages in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to display a custom error message when a file is not found.

PowerShell

try {
    Get-Content -Path 'nonexistent.txt'
} catch {
    Write-Host [1]
}

Drag options to blanks, or click blank then click option'

AError occurred

BFile not found!

C"File not found! Please check the path."

D"An error happened"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the message

Using a variable name instead of a string

The Write-Host command needs a string in quotes to display the custom error message.

2fill in blank

medium

Complete the code to throw a custom error with the message 'Invalid input detected'.

PowerShell

if ($input -eq $null) {
    [1] 'Invalid input detected'
}

Drag options to blanks, or click blank then click option'

AWrite-Error

BThrow

CWrite-Host

DExit

Attempts:

3 left

💡 Hint

Common Mistakes

Using Write-Error instead of Throw for terminating errors

Using Write-Host which only prints text

The Throw statement is used to generate a terminating error with a custom message.

3fill in blank

hard

Fix the error in the code to correctly catch and display a custom error message.

PowerShell

try {
    Remove-Item -Path 'C:\temp\file.txt'
} catch {
    Write-Host [1]
}

Drag options to blanks, or click blank then click option'

A$_.Exception.Message

B$_.Message

C$error.Message

D$error[0].Message

Attempts:

3 left

💡 Hint

Common Mistakes

Using $error which is a global array, not the current error

Using $_.Message which does not exist

Inside catch, $_ represents the ErrorRecord object. $_.Exception.Message gives the error message.

4fill in blank

hard

Fill both blanks to create a function that throws a custom error with a given message.

PowerShell

function Throw-CustomError {
    param([string]$msg)
    [1] [2]
}

Drag options to blanks, or click blank then click option'

AThrow

B"$msg"

C$msg

DWrite-Error

Attempts:

3 left

💡 Hint

Common Mistakes

Putting quotes around $msg which makes it a literal string '$msg'

Using Write-Error instead of Throw for terminating errors

Throw is used to raise an error, and $msg passes the message string parameter.

5fill in blank

hard

Fill all three blanks to catch an error and throw a new custom error with a modified message.

PowerShell

try {
    Get-Item -Path 'C:\invalid\file.txt'
} catch {
    $msg = $_.[1]
    $newMsg = "Custom error: $msg"
    [2] [3]
}

Drag options to blanks, or click blank then click option'

AException.Message

BThrow

C$newMsg

DMessage

Attempts:

3 left

💡 Hint

Common Mistakes

Using $_.Message instead of $_.Exception.Message for detailed error

Using Write-Error instead of Throw for terminating errors

Passing the variable name as a string instead of the variable value

Use $_.Exception.Message to get the original error message, then Throw the new message stored in $newMsg.

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