Attempting to patch a corporate template (reason why the version is so old) and when using any later ESR installer with the -ms parameters the old version remains. The installer returns a 0 exit code when done through our scripting. However it never actually installs. Being ESR there are no logs. When you manually install everything goes fine. The scripting handles elevating permissions, we use the same functionality across the enterprise so we know this should not be the issue. However, and this is the odd part, if we "inject" a new installer in our scripting it will install if done without any other actions. However, for production support we have many other third party app updates. I was leaning towards app conflicts (maybe handle locks on required libs etc) but after much testing, there are no conflicts. I am at a loss. Any thoughts?