Try-Catch-Finally in PowerShell

Introduction

Try-Catch-Finally helps you handle errors in your script so it doesn't stop unexpectedly. It lets you try code, catch errors, and always run cleanup code.

When you want to run a command but handle possible errors without stopping the script.

When you need to log or show a friendly message if something goes wrong.

When you want to make sure some code runs no matter what, like closing a file or releasing resources.

When you want to separate normal code from error handling code for clarity.

When debugging scripts to catch and understand errors.

Syntax

PowerShell

try {
    # Code that might cause an error
} catch {
    # Code to handle the error
} finally {
    # Code that always runs
}

The try block contains code that might fail.

The catch block runs only if an error happens in try.

Examples

This tries to read a file. If the file is missing, it shows a message instead of stopping.

PowerShell

try {
    Get-Content 'file.txt'
} catch {
    Write-Host 'File not found.'
}

This tries to divide by zero, catches the error, shows a message, and always prints 'Done trying division.'

PowerShell

try {
    1 / 0
} catch {
    Write-Host 'Cannot divide by zero.'
} finally {
    Write-Host 'Done trying division.'
}

Sample Program

This script tries to divide 10 by zero, which causes an error. The catch block shows a friendly message. The finally block runs always.

PowerShell

try {
    $number = 10
    $result = $number / 0
    Write-Host "Result is $result"
} catch {
    Write-Host "Oops! You can't divide by zero."
} finally {
    Write-Host "This runs no matter what."
}

Important Notes

Use finally to clean up resources like files or connections.

If no error happens, the catch block is skipped.

Errors caught by catch are called terminating errors in PowerShell.

Summary

Try-Catch-Finally helps manage errors smoothly in scripts.

try runs code that might fail, catch handles errors, and finally runs always.

This makes scripts more reliable and user-friendly.

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