Try-Catch-Finally in PowerShell - Mini Project: Build & Apply

Handling Errors with Try-Catch-Finally in PowerShell

📖 Scenario: You are writing a PowerShell script to divide numbers. Sometimes the divisor might be zero, which causes an error. You want to handle this error gracefully and always print a message at the end.

🎯 Goal: Build a PowerShell script that uses try, catch, and finally blocks to handle division errors and always print a final message.

📋 What You'll Learn

Create two variables $numerator and $denominator with exact values

Create a variable $errorActionPreference set to 'Stop' to enable error catching

Use a try block to divide $numerator by $denominator

Use a catch block to handle division by zero errors and print 'Cannot divide by zero!'

Use a finally block to print 'Operation complete.'

Print the result of the division if no error occurs

💡 Why This Matters

🌍 Real World

Scripts often need to handle unexpected errors like dividing by zero or missing files. Using try-catch-finally helps keep scripts running smoothly and informs users about problems.

💼 Career

Knowing how to handle errors in scripts is essential for system administrators, DevOps engineers, and automation specialists to create reliable and maintainable automation.

1

Create numerator and denominator variables

Create two variables called $numerator with value 10 and $denominator with value 0.

PowerShell

# Create variables $numerator and $denominator with values 10 and 0
# Your code here

Hint

Use = to assign values to variables in PowerShell.

2

Set error action preference to stop

Create a variable called $ErrorActionPreference and set it to 'Stop' to make errors catchable.

PowerShell

$numerator = 10
$denominator = 0
# Set $ErrorActionPreference to 'Stop'
# Your code here

Hint

This setting makes PowerShell treat errors as terminating, so catch can handle them.

3

Write try-catch-finally blocks for division

Write a try block that divides $numerator by $denominator and stores the result in $result. Add a catch block that prints 'Cannot divide by zero!'. Add a finally block that prints 'Operation complete.'.

PowerShell

$numerator = 10
$denominator = 0
$ErrorActionPreference = 'Stop'

# Write try-catch-finally blocks for division
# Your code here

Hint

Use try { ... }, catch { ... }, and finally { ... } blocks. Use Write-Output to print messages.

4

Print the result if division succeeds

After the try-catch-finally blocks, add a line to print the value of $result only if it exists.

PowerShell

$numerator = 10
$denominator = 0
$ErrorActionPreference = 'Stop'

try {
    $result = $numerator / $denominator
} catch {
    Write-Output 'Cannot divide by zero!'
} finally {
    Write-Output 'Operation complete.'
}

# Print $result if it exists
# Your code here

Hint

Use if ($result) { Write-Output $result } to print the result only if it was set.

Practice

1. What is the main purpose of the try block in PowerShell's Try-Catch-Finally structure?

easy

A. To always run code regardless of errors

B. To handle errors after they occur

C. To run code only if no errors happen

D. To run code that might cause an error

Solution

1. Step 1: Understand the role of try

   The try block contains code that might cause an error during execution.

2. Step 2: Differentiate from catch and finally

   catch handles errors after they happen, and finally runs code always, but try is where risky code runs.

3. Final Answer:

   To run code that might cause an error -> Option D

4. Quick Check:

   try runs risky code = A [OK]

Hint: Try block runs code that may fail [OK]

Common Mistakes:

• Confusing try with catch
• Thinking finally runs only on errors
• Believing try runs only if no errors

2. Which of the following is the correct syntax to catch an error in PowerShell?

easy

A. catch { Write-Host 'Error occurred' }

B. catch() { Write-Host 'Error occurred' }

C. catch: { Write-Host 'Error occurred' }

D. catch[] { Write-Host 'Error occurred' }

Solution

1. Step 1: Recall PowerShell catch syntax

   In PowerShell, catch is followed by a script block in curly braces without parentheses or other symbols.

2. Step 2: Identify correct syntax

   catch { Write-Host 'Error occurred' } uses catch { ... } which is correct; others add invalid symbols like parentheses or colons.

3. Final Answer:

   catch { Write-Host 'Error occurred' } -> Option A

4. Quick Check:

   Correct catch syntax uses braces only = A [OK]

Hint: Catch uses braces {} without parentheses [OK]

Common Mistakes:

• Adding parentheses after catch
• Using colon or brackets with catch
• Missing curly braces around catch code

3. What will be the output of this PowerShell script?

try {
  1 / 0
  Write-Output 'Success'
} catch {
  Write-Output 'Error caught'
} finally {
  Write-Output 'Always runs'
}

medium

A. Error caught
Always runs

B. Success

C. Success
Always runs

D. Error caught

Solution

1. Step 1: Analyze the try block

   The code attempts to divide 1 by 0, which causes a runtime error, so the line Write-Output 'Success' is skipped.

2. Step 2: Check catch and finally behavior

   The catch block runs and outputs 'Error caught'. The finally block always runs and outputs 'Always runs'.

3. Final Answer:

   Error caught Always runs -> Option A

4. Quick Check:

   Error triggers catch, finally always runs = C [OK]

Hint: Error skips try rest, runs catch then finally [OK]

Common Mistakes:

• Assuming 'Success' prints despite error
• Ignoring finally block output
• Thinking catch runs only sometimes

4. Identify the error in this PowerShell script:

try {
  Write-Output 'Start'
} catch {
  Write-Output 'Error'
} finaly {
  Write-Output 'Done'
}

medium

A. Missing parentheses after catch

B. No error in the script

C. Misspelled 'finally' keyword

D. Missing semicolon after Write-Output

Solution

1. Step 1: Check spelling of keywords

   The script uses finaly instead of the correct finally keyword.

2. Step 2: Verify other syntax elements

   Catch does not require parentheses, and semicolons are optional in PowerShell; so these are not errors.

3. Final Answer:

   Misspelled 'finally' keyword -> Option C

4. Quick Check:

   Keyword spelling matters: 'finally' correct = B [OK]

Hint: Check spelling of 'finally' carefully [OK]

Common Mistakes:

• Thinking catch needs parentheses
• Expecting semicolons after commands
• Missing typo in finally keyword

5. You want to ensure a log file is always closed after writing, even if an error occurs during writing. Which Try-Catch-Finally structure correctly achieves this?

hard

A. try { Write-Output 'Write log' } catch { Close-LogFile } finally { Write-Output 'Error' }

B. try { Write-Output 'Write log' } catch { Write-Output 'Error' } finally { Close-LogFile }

C. catch { Write-Output 'Error' } try { Write-Output 'Write log' } finally { Close-LogFile }

D. try { Write-Output 'Write log' } finally { Close-LogFile } catch { Write-Output 'Error' }

Solution

1. Step 1: Understand Try-Catch-Finally order

   The correct order is try, then catch, then finally. The finally block always runs last.

2. Step 2: Identify correct usage for closing log file

   try { Write-Output 'Write log' } catch { Write-Output 'Error' } finally { Close-LogFile } correctly places Close-LogFile in finally to ensure it runs always, even if an error occurs.

3. Final Answer:

   try { Write-Output 'Write log' } catch { Write-Output 'Error' } finally { Close-LogFile } -> Option B

4. Quick Check:

   Try-Catch-Finally order with cleanup in finally = D [OK]

Hint: Put cleanup code in finally block [OK]

Common Mistakes:

• Placing finally before catch
• Putting cleanup in catch only
• Misordering Try-Catch-Finally blocks