{"id":78793,"date":"2026-07-13T13:55:27","date_gmt":"2026-07-13T13:55:27","guid":{"rendered":"http:\/\/bangla.sitestree.com\/?p=78793"},"modified":"2026-07-13T13:55:27","modified_gmt":"2026-07-13T13:55:27","slug":"write-error","status":"publish","type":"post","link":"http:\/\/bangla.sitestree.com\/?p=78793","title":{"rendered":"Write-Error"},"content":{"rendered":"\n

Write-Error<\/code> in PowerShell<\/h2>\n\n\n\n

Write-Error<\/code> writes an error message to PowerShell\u2019s error stream<\/strong>.<\/p>\n\n\n\n

By default, it creates a non-terminating error<\/strong>. That means PowerShell displays the error, but usually continues with the next command.<\/p>\n\n\n\n

Write-Error \"The file could not be found.\"\n\nWrite-Output \"The script continued.\"\n<\/code><\/pre>\n\n\n\n
Typical result:<\/p>\n\n\n\n
Write-Error: The file could not be found.\nThe script continued.\n<\/code><\/pre>\n\n\n\n
Make it terminating<\/h2>\n\n\n\n
Use:<\/p>\n\n\n\n
-ErrorAction Stop\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
Write-Error \"The file could not be found.\" -ErrorAction Stop\n\nWrite-Output \"This line will not run.\"\n<\/code><\/pre>\n\n\n\n
Now the error stops normal execution.<\/p>\n\n\n\n
Use with try\/catch<\/code><\/h2>\n\n\n\n
try {\n    Write-Error \"The server is unavailable.\" -ErrorAction Stop\n}\ncatch {\n    Write-Warning \"The error was caught.\"\n    Write-Warning $_.Exception.Message\n}\n<\/code><\/pre>\n\n\n\n
Possible output:<\/p>\n\n\n\n
WARNING: The error was caught.\nWARNING: The server is unavailable.\n<\/code><\/pre>\n\n\n\n
Without -ErrorAction Stop<\/code>, the catch<\/code> block normally does not run because Write-Error<\/code> is non-terminating by default.<\/p>\n\n\n\n
Inside a function<\/h2>\n\n\n\n
function Get-LabFile {\n    param(\n        [string]$Path\n    )\n\n    if (-not (Test-Path -Path $Path)) {\n        Write-Error \"The file '$Path' does not exist.\"\n        return\n    }\n\n    Get-Content -Path $Path\n}\n<\/code><\/pre>\n\n\n\n
Call:<\/p>\n\n\n\n
Get-LabFile -Path \".\\missing.txt\"\n<\/code><\/pre>\n\n\n\n
Error details<\/h2>\n\n\n\n
Write-Error<\/code> can provide more structured information:<\/p>\n\n\n\n
Write-Error `\n    -Message \"The configuration file is missing.\" `\n    -Category ObjectNotFound `\n    -ErrorId \"ConfigFileMissing\" `\n    -TargetObject \".\\config.json\"\n<\/code><\/pre>\n\n\n\n
This creates an error record containing:<\/p>\n\n\n\n