Windows last exit code

DrFloyd5 DrFloyd5 If you're running directly from a Windows command line and always seeing 0 returned, see Gary's answer: stackoverflow. So "errorlevel 0" will match everything. The only thing that worked is if errorlevel Show 1 more comment.

Gary Gary 4, 1 1 gold badge 20 20 silver badges 19 19 bronze badges. I did not know about that command. Another reason why it might not work always zero is when it's inside an if or for. Consider using! Adam Rosenfield Adam Rosenfield k 95 95 gold badges silver badges bronze badges. It's not an actual environment variable which is, obviously, why it ceases to work if there is a variable named that way. Curtis Yallop Curtis Yallop 5, 3 3 gold badges 41 41 silver badges 28 28 bronze badges.

Is it case-sensitive? Mid self. WaitForSingleObject pi. GetExitCodeProcess pi. CloseHandle pi. It's worth noting that. I have small powershell script. I want to set a variable in if-then-else condition, which will be used by SCCM. My powershell script is compiled script exe format should return true or false depending on the condition. Don't set the LastExitCode, just use it after you perform a function, it already contains the result success or fail of the action Jack, I removed as well last line but it is still returning 0 value.

Please correct me if my approach for script and checking the value of exitcode is correct or is there better way? Before compiling script how can I test the exit code? Can you please tell me how to create unique environment variable so SCCM can handle properly? I guess I am not sure what you are trying to do.

If you just want to use exit codes that's pretty much any non-zero exit code is an "error". Applications can have custom error codes configured, as can OSD Task Sequences but Packages Programs can't, so maybe if you give an example of what you are trying to do, I can help a little more We have two different compiled PS exe files.

SCCM team pushing this exe to each user machines. Now we want to test that if first exe runs successfully we have some internal conditions in the program, if any of the conditions failed, we want to return exit code as 0 so thru SCCM we can check If exit code 0 so next exe will not run and if exit code is 1 then second exe will run.

That is why I am looking for lastexitCode option or probably by creating some unique environment variable and assign the value depending on the first executable conditions then in SCCM will check the value as I mentioned above and do the rest of process.

The LastExitCode is the actual result from what you run, for example, if you start a service with PowerShell and the service isn't found, or cant start, or whatever, the actual error is returned to PowerShell and stored in LastExitCode, so perhaps you are making this more complex than it need be?

I already saw this example. Here, if the condition is met, the script will terminate with the exit code 0. This guide demonstrates what exit codes are and how you can use them. It also demonstrates how to assign appropriate exit codes in a bash script. Interested in bash scripting? One of the easiest ways to get started is by writing your own scripts. Check out this simple guide on how to write a simple bash script. Community Bot 1. Sign up or log in Sign up using Google. Sign up using Facebook.

Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses.