Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Firefox is forcefully updating when configured to never update

  • 6 wotmołwy
  • 1 ma tutón problem
  • 6 napohladow
  • Poslednja wotmołwa wot alchemist111

more options

We use multiple Firefox profiles to do automated testing using Selenium. All of them are set to never update.

Recently, they have started updating themselves to 47.0. Selenium is apparently incompatible with this version, as soon as it tries to open Firefox 47.0, Firefox crashes.

I also noticed that simply checking the FF version in "About Firefox" causes it to update--this seems like intrusive, malicious behavior.

  1. 1: Why is Firefox updating when configured not to?
  2. 2: Anyway to get Selenium to work with 47.0?
  3. 3: Anyway to disable the auto-update that happens when we simply check the FF version?

Thanks

We use multiple Firefox profiles to do automated testing using Selenium. All of them are set to never update. Recently, they have started updating themselves to 47.0. Selenium is apparently incompatible with this version, as soon as it tries to open Firefox 47.0, Firefox crashes. I also noticed that simply checking the FF version in "About Firefox" causes it to update--this seems like intrusive, malicious behavior. #1: Why is Firefox updating when configured not to? #2: Anyway to get Selenium to work with 47.0? #3: Anyway to disable the auto-update that happens when we simply check the FF version? Thanks

Wšě wotmołwy (6)

more options

Hi alchemist111, I cant remember if the prefs changes prevent that. Personally if I wish to check the version I do NOT use

Menu -. Help -> about Firefox

Instead look at the troubleshooting page (also available by keying into the address bar about:support)

That confirms the version without triggering an update even in Windows with the maintenance service. Note it is also possible to abort such updates by deleting the files before you restart.

See https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment note to change or lock the prefs

"app.update.enabled", false;
"app.update.auto", false;
"app.update.mode", 0;
"app.update.service.enabled", false;

I do not recall noticing any recent changes in update behaviour. It has triggered updates when you use the about firefox for years that is not new.

Sorry I am not sure why your Firefox installs are upgrading automatically if it is not you using the about firefox. Neither do I know about selenium's compatibility, but I hope the partial answer may help you.

I do note a related Selenium issue was reported before /questions/1128976#answer-892517 . Perhaps you could try Selenium's support and report back what the answer is with a link to their response. If we know what the issue is it may be possible to file a bug or see if one has been filed.

more options

https://www.mozilla.org/en-US/firefox/47.0.1/releasenotes/ Fixed Selenium WebDriver may cause Firefox to crash at startup

The Firefox 47.0.1 soft-release was made to fix a problem particular to Selenium users, where 47.0 was crashing.


Using Help > About Firefox has always caused an update check to occur and the update to be installed when the user selected Never check for updates (not recommend security risk) in Options > Advanced - > Update.

Also the Mozilla Maintenance Service can bring about unwanted updates. https://support.mozilla.org/en-US/kb/what-mozilla-maintenance-service

That is intended to solve a bit of flakiness in some versions of Windows to allow non-Admin User Accounts to do Firefox updates, to overcome certain user settings in Windows that kept Firefox updates from proceeding,

But there is another effect to that service - check your Private Messages for this forum for further information.

more options

Even if we fix the current situation, the main issue is that FF seems to spontaneously update itself despite having all configuration options set to not update. This is not the 1st time it has happened, and each time there is a significant chance that things break.

As we have created a fairly extensive testing automation platform, the last thing we want is FF updates outside of our control.

Does anyone know a way to lock-down FIrefox so it can absolutely not update without our putting it into motion ourselves? Perhaps by deleting certain files or configuring registry settings?

Btw we also tried upgrading to 47.0.1, it does not crash FF from Selenium, but still seems to not work correctly with our current Selenium based automation tool.

Wot alchemist111 změnjeny

more options

Have you tried the prefs mentioned and uninstalling the maintenance Service. Could someone else be deliberately updating Firefox ? With the maintenance service active it will update Firefox on all Windows accounts.

I do not see spontaneous updates of Firefox myself and do not see how or why that is happening. Did you check ed's private message in case that had something relevant ?

more options

John - Yes, he did contact me by PM this morning about MMS.

Didn't mention the continuing problem with Selenium though, so I am going to link the other current Selenium thread here: https://support.mozilla.org/en-US/questions/1128976

more options

We will go ahead and start deleting the MMS files as well, thanks for that advice, hopefully that will help.

I don't think anyone is deliberately updating them. Although occasionally, someone has checked Help-About. I've instructed our team to stop doing that as well.