Replies: 1 comment 1 reply
-
You would likely have to ask either PSADT, or the vendor providing the setup file. In that example PSADT is likely checking the exit code of the installer and exiting with that error code if it's not 0. As far as I know PowerShell itself only ever exits with |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've had issues in the past where I've seen exit codes like
64
, meaning the provided command line was bad. I've got a situation now where I have otherwise reliable scripts exiting with255
, and I'm not sure why.Appreciate the below is from Windows PowerShell but I'm tied to it for now. This is literally all I receive out of a global transcript log when a script happens to fail in this manner.
Beta Was this translation helpful? Give feedback.
All reactions