Closed Bug 1371360 Opened 7 years ago Closed 5 years ago

Firefox updates to a newer version even though I've configured Updates to "Never Check"

Categories

(Toolkit :: Application Update, defect, P3)

45 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: javascriptjedi, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20170411115307 Steps to reproduce: Installed Firefox 53.0.2 Configured radio button in "Options >> Advanced >> Update" to "Never check for updates (not recommended: security risk)" Actual results: About dialog popped up on its own and indicated an update had been downloaded, 53.0.3, and would be installed when I restarted FF. Expected results: Firefox should have behaved as one would expect from the UI configuration, which is to *never update*. Why have that option if it has no impact? It's misleading. I had to manually delete the updated directory. For now I've disabled and then uninstalled the maintenance service. I didn't even know there was such a service - why was I not prompted whether I wanted to install this when installing FF? Why do I have to uninstall it to get FF to do what's expected from its UI configuration? I thought Microsoft was bad with its dumbed down "Windows Update" service that forces updates down your throat, but looks like FF is following the same pattern. I can make my own decisions.
Component: Untriaged → Application Update
Product: Firefox → Toolkit
If the pref was changed after the download started the download will continue. Could you try to reproduce and only use a profile that6 already has it set to not update? Thanks!
I have been experiencing that for a long time throughout multiple versions of Firefox. In the Options the radio button "Never check for updates" has always been checked, but Firefox kept ignoring it and updating itself without ANY notification - I simply close it in the evening, run it again next day and a new version starts. There is no notification at all that a new version has been installed. Very annoying, especially if a new version is broken and makes using Firefox even more difficult than before.
BTW, I reported that bug 2 years ago and nothing has been done about it. Bug number: 1244516.
I can confirm this bug on Windows.
I have seen many people talking about this on Twitter, and some say the culprit is Kaspersky that automatically upgrades Firefox (and probably other outdated applications) regardless of the update settings.
(In reply to Kohei Yoshino [:kohei] from comment #5) I'm using ESET Internet Security and Firefox downloads the updates to its Updates folder and executes the upgrader next time I run Firefox.
Blocks: up-prefs
Priority: -- → P3
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64

No reply from the reporter for comment #1 so resolving as incomplete.

The main issue we've seen that causes this bug has been due to a different profile checking for an update and then starting the download of the update. Then the profile with the check disabled continues the download since the preference is only for disabling the check.

The latest version of Firefox on Windows stores this information using a method different than the pref system which applies to all profiles that use the installation which should resolve this issue. On Nightly (which will be Firefox 69) we also made it so if you change the setting in options from "Automatically install updates (recommended)" to "Check for updates but let you choose to install them" and there is an update in progress it will give you the option to cancel the update in progress.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE

Firefox now longer allows the user the setting to not update. This forces accessibility breakages on users and is absolutely not ok.

Auto updating didn't only happen with a different profile. Firefox also auto updated whenever the "about firefox" windows was opened - regardless of the setting. Is this fixed?

You need to log in before you can comment on or make changes to this bug.