armadillo extraction error ES1 demystified

just thought i'd share this cuz there is almost no specific answers out there as to what causes armadillos 'general extraction errors'

if you are one of those who have experienced the ES1 extraction error, this is caused by having initialized SuperBPM. it doesn't need to be running at the time, all it takes is to start it once and the service remains active. armadillo detects this and stops unpacking itself.

you can, in a variety of ways, change SuperBPM resources to rename the service... be creative. this will stop dillo from messing up.