Windows Powershell 2.0 returns incorrect exit code, when it is a negative number

Symptoms

Consider the following scenario:

You use Windows Powershell 2.0 to call a Powershell script that returns a negative exit code.
Example:
- To check if a product installation finished successfully or not.
- If a scheduled task with a Powershell script finished successfully or not.
PowerShell 2.0 may not return the correct exit code.

To workaround this problem, do not use negative exit codes with Powershell version 2.0.

==== Sample Script ====

PS C:\temp> gc .\Exit-3.ps1
exit -3

==== Sample Script ====

Calling the script from a powershell window
PS C:\temp> .\Exit-3.ps1
PS C:\temp> $LastExitCode
-3
Note: Calling the script directly from a powershell window - Works as expected !

As seen below all other calls from powershell or cmd window with –command or –file parameter do not return the right code.
Calling the script from a powershell window with parameter –command
PS C:\temp> powershell -c "c:\temp\Exit-3.ps1"
PS C:\temp> $LastExitCode
1
Calling the script from a cmd window with parameter –command
c:\TEMP>powershell -c "c:\temp\Exit-3.ps1"
c:\TEMP>echo %errorlevel%
1
Calling the script from a cmd window with parameter –file
c:\TEMP>powershell -f "c:\temp\Exit-3.ps1"
c:\TEMP>echo %errorlevel%
65533
Calling the script from a powershell window with parameter –file
PS C:\temp> powershell -f "c:\temp\Exit-3.ps1"
PS C:\temp> $LastExitCode
65533

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Keywords: kb

Article Info