To make sense of the others, you need to know that Bigfix isn’t interpreting the return codes as they’re intended, and a little bit about how negative numbers are represented in binary code.
Negative numbers in binary are stored in a format known as “two’s complement”. Without getting into the math involved, let’s just say any binary value where the most significant bit is a “1” is interpreted to be a negative decimal number and leave it at that. We can plug it into a two’s complement calculator to get the binary representation.
Take the last number from your first post, “-2146885628”. Navigate to https://www.exploringbinary.com/twos-complement-converter/ , paste in that negative number, and set the size to “32 bits”, and you’ll get the binary value “10000000000010010010000000000100”.
Knowing that a lot of Microsoft error codes are shown in hexadecimal (0xSomething), take the binary value and convert it to hex at https://www.rapidtables.com/convert/number/binary-to-hex.html , and you’ll get the hexadecimal value 80092004.
So Google for 0x80092004 and you see it’s a valid windows installer error code. The first result at https://support.microsoft.com/en-us/help/4345232/0x80092004-error-and-updates-kb4340557-and-kb4340558-don-t-install-aft points toward a problem with a July 2018 .NET Rollup Package. I hope you’re not still deploying something that old, but in any case that’s how to interpret the return code and hopefully Google can help further.
After I started writing I found a shortcut on that second link, at https://www.rapidtables.com/convert/number/decimal-to-hex.html - you can enter the negative decimal number directly, and the “hex signed two’s complement” result gets you directly to 80092004.
Edit: when I was first writing this I was manually converting and did your last number incorrectly… -2146498497 = 0x800F083F which is also a windows installer error code worth googling.