<\/p>\n\n\n\n
A non-terminating error<\/strong> reports a problem but allows PowerShell to continue running the remaining commands.<\/p>\n\n\n\n Example:<\/p>\n\n\n\n Possible output:<\/p>\n\n\n\n The file-reading command failed, but PowerShell still ran the next line.<\/p>\n\n\n\n Common examples include:<\/p>\n\n\n\n By default, many PowerShell cmdlets generate non-terminating errors.<\/p>\n\n\n\n A terminating error<\/strong> stops the current operation or script block. PowerShell does not continue normally unless the error is caught.<\/p>\n\n\n\n Example using The second command does not run because Another example:<\/p>\n\n\n\n Division by zero produces a terminating error.<\/p>\n\n\n\n Consider:<\/p>\n\n\n\n You might expect Therefore, PowerShell displays the error but may not enter the To make it catchable, add:<\/p>\n\n\n\n Correct version:<\/p>\n\n\n\n Now the non-terminating error is converted into a terminating error, so Expected output:<\/p>\n\n\n\n The Many cmdlets support the common parameter Common choices:<\/p>\n\n\n\n For exception handling, the most important one is:<\/p>\n\n\n\n By default, it creates a non-terminating error:<\/p>\n\n\n\n To make it terminating:<\/p>\n\n\n\n Use A non-terminating error reports a problem and usually continues. A terminating error stops normal execution and can be handled by Get-Content -Path \".\\MissingFile.txt\"\nWrite-Output \"The script continued.\"\n<\/code><\/pre>\n\n\n\nGet-Content : Cannot find path '.\\MissingFile.txt' because it does not exist.\nThe script continued.\n<\/code><\/pre>\n\n\n\nGet-Content \".\\MissingFile.txt\"\nGet-Item \".\\MissingFolder\"\nWrite-Error \"A problem occurred\"\n<\/code><\/pre>\n\n\n\n
\n\n\n\nTerminating error<\/h3>\n\n\n\n
throw<\/code>:<\/p>\n\n\n\nthrow \"The configuration file is invalid.\"\n\nWrite-Output \"This line will not run.\"\n<\/code><\/pre>\n\n\n\nthrow<\/code> creates a terminating error.<\/p>\n\n\n\n$result = 10 \/ 0\nWrite-Output \"Finished\"\n<\/code><\/pre>\n\n\n\n
\n\n\n\nMain difference<\/h2>\n\n\n\n
Feature<\/th> Non-terminating error<\/th> Terminating error<\/th><\/tr><\/thead> Displays an error<\/td> Yes<\/td> Yes<\/td><\/tr> Continues to the next command<\/td> Usually yes<\/td> No<\/td><\/tr> Automatically activates catch<\/code><\/td>No<\/td> Yes<\/td><\/tr> Can be converted using -ErrorAction Stop<\/code><\/td>Yes<\/td> Already terminating<\/td><\/tr> Typical source<\/td> Cmdlet failure<\/td> throw<\/code>, runtime failure, or -ErrorAction Stop<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\nWhy
try\/catch<\/code> sometimes does not work<\/h2>\n\n\n\ntry {\n Get-Content -Path \".\\MissingFile.txt\"\n}\ncatch {\n Write-Output \"The error was caught.\"\n}\n<\/code><\/pre>\n\n\n\ncatch<\/code> to run, but Get-Content<\/code> normally produces a non-terminating error.<\/p>\n\n\n\ncatch<\/code> block.<\/p>\n\n\n\n-ErrorAction Stop\n<\/code><\/pre>\n\n\n\ntry {\n Get-Content -Path \".\\MissingFile.txt\" -ErrorAction Stop\n}\ncatch {\n Write-Output \"The file could not be read.\"\n}\n<\/code><\/pre>\n\n\n\ncatch<\/code> runs.<\/p>\n\n\n\n
\n\n\n\nFull example<\/h2>\n\n\n\n
try {\n Write-Output \"Trying to read the file...\"\n\n $content = Get-Content `\n -Path \".\\MissingFile.txt\" `\n -ErrorAction Stop\n\n Write-Output \"The file was read successfully.\"\n}\ncatch {\n Write-Warning \"The file could not be read.\"\n Write-Warning \"Reason: $($_.Exception.Message)\"\n}\nfinally {\n Write-Output \"The operation is complete.\"\n}\n<\/code><\/pre>\n\n\n\nTrying to read the file...\nWARNING: The file could not be read.\nWARNING: Reason: Cannot find path ...\nThe operation is complete.\n<\/code><\/pre>\n\n\n\nfinally<\/code> block runs whether the operation succeeds or fails.<\/p>\n\n\n\n
\n\n\n\nErrorAction<\/code> values<\/h2>\n\n\n\n-ErrorAction<\/code>.<\/p>\n\n\n\nGet-Content \".\\MissingFile.txt\" -ErrorAction Continue\n<\/code><\/pre>\n\n\n\nValue<\/th> Behaviour<\/th><\/tr><\/thead> Continue<\/code><\/td>Display the error and continue; default behaviour<\/td><\/tr> SilentlyContinue<\/code><\/td>Hide the error and continue<\/td><\/tr> Stop<\/code><\/td>Convert the error into a terminating error<\/td><\/tr> Inquire<\/code><\/td>Ask the user what to do<\/td><\/tr> Ignore<\/code><\/td>Hide the error and do not add it to $Error<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n-ErrorAction Stop\n<\/code><\/pre>\n\n\n\n
\n\n\n\nWrite-Error<\/code> compared with throw<\/code><\/h2>\n\n\n\nWrite-Error<\/code><\/h3>\n\n\n\nWrite-Error \"The server was not found.\"\n\nWrite-Output \"The script continued.\"\n<\/code><\/pre>\n\n\n\nWrite-Error \"The server was not found.\" -ErrorAction Stop\n<\/code><\/pre>\n\n\n\nthrow<\/code><\/h3>\n\n\n\nthrow<\/code> creates a terminating error:<\/p>\n\n\n\nthrow \"The server was not found.\"\n<\/code><\/pre>\n\n\n\nthrow<\/code> when the script cannot safely continue.<\/p>\n\n\n\n
\n\n\n\nSimple rule<\/h2>\n\n\n\n
\n
try\/catch<\/code>.<\/p>\n<\/blockquote>\n\n\n\n