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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Firefox Auto-Update not working

  • 3 àwọn èsì
  • 1 ní ìṣòro yìí
  • 5 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ Mike Kaply

more options

To whom it may concern

I am testing the autoupdate on one of my vm`s and I cannot configure what we need.

Goal: - We would like to update firefox esr yearly with a package through sccm. - After installation or after first startup, firefox should imediately update to newest version - From then, firefox esr should installed newest version as soon as available and check daily for a new version


My Config:

// Enable updater lockPref("app.update.enabled", true); lockPref("app.update.auto", true); lockPref("app.update.mode", 0); lockPref("app.update.service.enabled", true); lockPref("app.update.silent", true); lockPref("app.update.timerFirstInterval", 60); lockPref("app.update.promptWaitTime", 60); lockPref("app.update.download.backgroundinterval", 0); lockPref("app.update.doorhanger", false); lockPref("app.update.disable_button.showUpdateHistory", false);


The config file was implemented. I could see the changes in about:config, but if I today distribute version 78.7.1 with the above config file, firefox esr does not automatically update to the newest version 78.8.0. Only if I open the settings or the help about.

What am I missing? How can I achieve that firefox will update silently(without user intervention) imediately to newest version after install and update regularly to newest version?

Regards, Jonas

To whom it may concern I am testing the autoupdate on one of my vm`s and I cannot configure what we need. Goal: - We would like to update firefox esr yearly with a package through sccm. - After installation or after first startup, firefox should imediately update to newest version - From then, firefox esr should installed newest version as soon as available and check daily for a new version My Config: // Enable updater lockPref("app.update.enabled", true); lockPref("app.update.auto", true); lockPref("app.update.mode", 0); lockPref("app.update.service.enabled", true); lockPref("app.update.silent", true); lockPref("app.update.timerFirstInterval", 60); lockPref("app.update.promptWaitTime", 60); lockPref("app.update.download.backgroundinterval", 0); lockPref("app.update.doorhanger", false); lockPref("app.update.disable_button.showUpdateHistory", false); The config file was implemented. I could see the changes in about:config, but if I today distribute version 78.7.1 with the above config file, firefox esr does not automatically update to the newest version 78.8.0. Only if I open the settings or the help about. What am I missing? How can I achieve that firefox will update silently(without user intervention) imediately to newest version after install and update regularly to newest version? Regards, Jonas

All Replies (3)

more options

You shouldn't need to change anything for autoupdate to work - it works by default.

How quickly do you get an update if you don't change anything?

more options

Mike Kaply said

You shouldn't need to change anything for autoupdate to work - it works by default. How quickly do you get an update if you don't change anything?

I installed Firefox Firefox Setup 78.7.1esr.exe (fileversion 18.5.0.0) on the 1st March, but no update yet. No config file or something else was added. It only updates manually if I check the file version. The only thing which may be different to other installations. I was running a previous installation on that system before. I will use a plain vm to test again.

more options

That's odd, there must be something blocking the update.

Is anything set in about:policies?

Does it update if you open the about dialog?