All Products Community Forum

I've been struggling for months to standardize a deployment of Firefox ESR across various client environments that reliably auto-updates and doesn't cause UAC prompts and XULRunner profile error pop-ups(I work in IT).

We deploy Firefox ESR in bulk on machines via a batch script which runs as SYSTEM, with msiexec /i and /qn flags.

Firefox installs fine, but then users are typically met with a UAC prompt when they first try to run Firefox. If they decline, then the UAC prompt comes back again next time and often fails to update at all, so the machine is left on an older, vulnerable version.

Regarding the environment: we have deployed the Firefox ESR admx templates and enabled the relevant auto update settings in Group Policy. But only some machines seem to stay up to date, and it seems like this only happens if a user with local administrative privileges has run the program at least once.

What I find unusual is that Firefox seems to attempt to make a "Background Updater" scheduled task for every user that runs the software on each PC, but these users do not have administrative privileges, and the scheduled task is set to only run when that user is logged in. Obviously a scheduled task running as a user with limited privileges isn't going to be able to update files in the Mozilla/Firefox subdirectory in "Program Files" as by default that's read-only access for non-admin users. And, obviously, if a user with local admin privileges DOES log into the machine, then it can update once, but then the scheduled task that it creates for that user (now with admin privileges) will only run when that user logs in - and we don't login as "admin"-privileged users day-to-day.

So, various machines are out of date, running vulnerable Firefox 128 instead of 140 or 142 even though they're all deployed from the same image and have the same policies and restrictions, and ran the same installer for Firefox.

Is there some reason why the auto update scheduled task isn't created at installation time, when administrative privileges have been granted? It's very odd that it doesn't, because then every time a user logs into a machine it seems like Firefox ESR creates the background upgrade task under a non-admin user which simply won't work. I see machines having 4 or 5 background upgrade scheduled tasks, all created by Firefox ESR, and yet the software still won't update - there's a UAC prompt every time the program launches, and going to Help -> About shows "Restart Firefox to update..." but then when clicking the button to restart Firefox, we get the UAC prompt, user doesn't have privileges, so this goes around and around in circles.

Is there a reliable way to keep Firefox up to date without manually logging into each machine and going through the UAC prompts? Can we manually create a scheduled task with the correct user account that has privileges to actually upgrade Firefox?

The background auto update mechanism simply doesn't make sense to our team on a machine-wide install.

Ever since I stupidly let Thunderbird 'update' to 140.5esr 64bit the date format has been wrecked. The program now forces the plain weird US date format of Month-Day-Year. I hoped that this obvious error would be fixed but it's been rather a long time now and the problem - and IT IS A PROBLEM - hasn't been addressed. It looks like Thunderbird is following Firefox in making each version worse. Whilst I switched to Pale Moon long ago there is as yet no fork of Thunderbird. If I were still on Windows for internet use I would just install an older version alas I do not know how to do this on Linux (Q4os Trinity) PLEASE fix this problem. I am far from the first to point this massive mistake out.

I am genuinely grateful to the people who work on these projects but a little more effort on actually being able to use the programs would be a substantial advance.

The last Firefox update to one of my Windows 10 machines was to 115 (which I thought was only for Win 7 & 8 installs). When I review the Help/About screen it is requesting an upgrade to 128, but 146 is the latest release. The ESR release for Win10 is 140.

After the latest (mid-December) Windows update destroyed so many things, including the sizing, movement, and display of Firefox windows, I'm freezing the automatic Microsoft update sequence, and installing the ESR 140 release as well.

Just trying to understand how Firefox determines which update level a browser will automatically download and install based on an existing, standard or ESR, release it finds installed.

Thank you.

It appears that any ESR version will auto upgrade to the Release version right after you close the program and shut your machine down. When you go back online, surprise!, you now have 144.0.1 installed with HALF your folders missing.

https://support.mozilla.org/en-US/questions/1548668/edit/1779923#answer-preview

Version 146.01 has me discombobulated. no shortcuts to add on anymore. can I have the previous version with my shortcuts?

Moderator note: This question has been edited to remove an unintended link and sensitive information. Moderator note: See also /questions/1560086.

Recently upgraded to windows 7, and upgraded firefox to version 115. Why am I getting notices that Windows Vista is no longer supported. [upgraded from vista to 7]