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.

Avatar for Username

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 ESR 128.x upgrade broken ?

  • 1 tontu
  • 0 am na jafe-jafe bii
  • i mujjee tontu mooy cor-el

stephen.wyatt
stephen.wyatt
more options

My organization has been using Firefox ESR for many years. I am trying to upgrade from ESR 115.12 to ESR 128.1 The upgrade is hanging at the very end of the install. Procmon shows firefox.exe being launched in the background and hanging. When I manually run firefox.exe, it says "Unable to read configuration file". If I edit "autoconfig.js", and comment out the "general.config.filename", then everything works.

We still use the general.config.filename and have not fully transitioned to the newer policies.json configuration (we have settings in both).

Was a change made in ESR 128 that broke (or stopped supporting) the older format ?

thanks, -stephen

My organization has been using Firefox ESR for many years. I am trying to upgrade from ESR 115.12 to ESR 128.1 The upgrade is hanging at the very end of the install. Procmon shows firefox.exe being launched in the background and hanging. When I manually run firefox.exe, it says "Unable to read configuration file". If I edit "autoconfig.js", and comment out the "general.config.filename", then everything works. We still use the general.config.filename and have not fully transitioned to the newer policies.json configuration (we have settings in both). Was a change made in ESR 128 that broke (or stopped supporting) the older format ? thanks, -stephen

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can check the Browser Console for more info about what is wrong with the autoconfig.cfg file.

The autoconfig.cfg file is run as a JavaScript file and errors in the file throw an exception. Note that the update to 128 ESR is not yet done automatically, as there is an overlap of two versions (i.e. the switch would happen with 128.3.0).

Helpful?

Laajal dara

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.