This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 60.9.0 ESR remaining after newer version silent install

  • 1 reply
  • 1 has this problem
  • 27 views
  • Last reply by m30guy

more options

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?

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?

All Replies (1)

more options

Forgot to mention this is on Windows Server 2012 R2 x64 (yes I know using servers as client platforms is wonky)