Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Firefox ESR 128.x upgrade broken ?

  • 1 Antwort
  • 0 haben dieses Problem
  • 17 Aufrufe
  • Letzte Antwort von cor-el

stephen.wyatt
stephen.wyatt
Weitere Optionen

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

Alle Antworten (1)

cor-el
cor-el
  • Moderator
Weitere Optionen

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).