How to Use Try-Catch Blocks in PowerShell for Error Handling

by
PinLinkedIn

Programming can be like making a sandwich. Sometimes, things go wrong. Maybe the cheese falls off. Or the bread is moldy. In PowerShell, when things go wrong, we call these errors. Lucky for us, PowerShell gives us a handy tool to deal with such messes — try-catch blocks.

Try-catch is a way to say: “Try this code… but if something breaks, catch the mistake and do something about it.” Neat, right?

Let’s break it down into small bites.

What is a Try-Catch Block?

Think of it like a seatbelt for your scripts. It helps protect your code when errors happen. Here’s the basic structure:

try {
    # Code that might cause an error
}
catch {
    # Code that runs if there is an error
}

Here’s a real example:

try {
    Get-Content "C:\NonExistentFile.txt"
}
catch {
    Write-Host "Oops! That file doesn't exist."
}

If the file’s not there, no worries! The catch part kicks in and handles it nicely.

When Should You Use Try-Catch?

Use it when:

  • Accessing files
  • Running external commands
  • Working with network resources
  • Anything risky where things could fail

Bonus: It makes your scripts look super professional.

Using Catch to Handle Errors

The catch block is where you clean up, log, or notify about the error. You can even get details about what happened:

try {
    Get-Item "C:\ThisFileDoesNotExist.txt"
}
catch {
    Write-Host "Error: $($_.Exception.Message)"
}

Here, $_.Exception.Message gives you the error message PowerShell encountered. Now your script talks back when things go wrong!

What About Finally?

Want to do something no matter what? Use finally.

try {
    # Code that could break
}
catch {
    # Handle the error
}
finally {
    # Always run this part
    Write-Host "This runs no matter what."
}

The finally block helps clean up. Maybe close a file. Disconnect a session. Take out the trash — metaphorically speaking.

Multiple Catch Blocks?

PowerShell doesn’t support multiple catch blocks like other languages. But you can check the error type inside a single catch:

try {
    # Code here
}
catch [System.IO.FileNotFoundException] {
    Write-Host "File not found!"
}
catch {
    Write-Host "Some other error occurred."
}

Yes! You can catch specific error types. That makes your error handling smarter.

Throwing Your Own Errors

Want to make up your own error? You rebel.

try {
    throw "Custom error message!"
}
catch {
    Write-Host "Caught my own error: $($_.Exception.Message)"
}

This lets you control how errors behave, even when nothing’s broken… yet.

Tips for Better Try-Catch

  • Keep your try block small. Only risky code goes there.
  • Don’t catch errors you can’t handle. Let them bubble up if needed.
  • Use logging in catch to track what went wrong.

Try-catch isn’t magic — it’s a tool. But it makes your scripts safer, smarter, and more robust.

Time to Practice!

Now that you know the basics, go build a small PowerShell script. Intentionally break it! Then fix it with a try-catch. Laugh at those errors — you are now the boss.

Remember: even mistakes are just stepping stones… with PowerShell safety nets.

PinLinkedIn