Exit code in powershell still zero even though cmdlet throws an error

Question

Suppose I cd to an empty directory in powershell and run the following command:

get-childitem x

The command will throw an error that it cannot find the path, which is expected.

However, when I check the $LastExitCode it is still zero.

This is confusing to me, since according to the docs $LastExitCode should contain the exit code of the last windows-based program that was run.

Could anyone please explain why the exit code is still zero after I run a command which clearly fails?

mcbr · Accepted Answer · 2022-01-01 11:14:13Z

4

get-childitem doesn't start a new process. If a powershell function or command throws an error it will be stored in the global $Error array. $LASTEXITCODE is created and set when you start a child process, for example a new powershell session with a command:

PS C:\> Get-ChildItem x
Get-ChildItem : Cannot find path 'C:\x' because it does not exist.
At line:1 char:1
+ Get-ChildItem x
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\x:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

PS C:\> $Error.Count
1
PS C:\> $Error[0]
Get-ChildItem : Cannot find path 'C:\x' because it does not exist.
At line:1 char:1
+ Get-ChildItem x
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\x:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

PS C:\> $LASTEXITCODE
PS C:\> powershell -Command { get-childitem x }
get-childitem : Cannot find path 'C:\x' because it does not exist.
At line:1 char:2
+  get-childitem x
+  ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\x:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

PS C:\> $LASTEXITCODE
1
PS C:\> powershell -Command { get-childitem . }


    Directory: C:\


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
.....
.....
.....


PS C:\> $LASTEXITCODE
0
PS C:\>

answered Jan 1, 2022 at 11:14

mcbr

8016 silver badges6 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

user32882 Over a year ago

Thank you for this clarification on the difference between starting a child process and running from the current process.

zett42 Over a year ago

I would add that there is also $? which could be used if you just want to check if the last command or process was successful (in case of process this means $LASTEXITCODE is not 0). Note that for processes one could not rely on $? until recently (PS 7.1.x or 7.2.x, I'm not sure).

zett42 Over a year ago

I've checked, $? has been fixed for native processes with PS 7.1 (see breaking changes)

js2010 · Accepted Answer · 2022-01-01 14:09:42Z

-1

In a powershell script you can do something like this at the bottom:

exit $error.count

Then the exit code will be the number of errors.

answered Jan 1, 2022 at 14:09

js2010

28.3k6 gold badges82 silver badges88 bronze badges

Collectives™ on Stack Overflow

Exit code in powershell still zero even though cmdlet throws an error

2 Answers 2

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related