CANT UPDATE MOZILAFIREFOX
Hi All, this question seems to come up on various forums, but I cannot find a definitive answer. We run the Enterprise version of FF (140.7.0esr (32-bit)), the product in… (pročitajte više)
Hi All, this question seems to come up on various forums, but I cannot find a definitive answer.
We run the Enterprise version of FF (140.7.0esr (32-bit)), the product installs and includes the scheduled task that checks for updates at a regular interval. This works, but the update only ever seems to be applied once the browser is launched.
According to the documentation there is the following setting:
Software\Policies\Mozilla\Firefox\AppAutoUpdate = 0x1 | 0x0
We have a number of users that do not frequently open FF and therefore our reporting shows that they are running an out of date version of the browser.
Has anyone managed to get this auto update mechanism to work without opening the browser? Is it even possible?
Thanks
Does updating my Firefox version have anything to do with my chat gpt not working on my computer?
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… (pročitajte više)
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.
Wscanner is need firefox update and it's already updated, what should I do?
I read that Firefox is offering extended support for Windows 7. I have Windows 7 Pro 64 and get updates. How long will I be able to get ESR for Windows 7?
Recently we've began installing Firefox 140.2.0esr to our environment via the .msi file that Mozilla provides, however we're running in to a very odd incident. After appr… (pročitajte više)
Recently we've began installing Firefox 140.2.0esr to our environment via the .msi file that Mozilla provides, however we're running in to a very odd incident.
After approximately 24 hours from installing Firefox esr to devices, it appears that the application is "updating" to 141.0.3 on the "release" channel. As far as I'm aware, this shouldn't be possible to begin with. But we've applied these settings via GPO:
Computer Config > Policies > Admin Templates > Mozilla > Firefox Application Autoupdate = Disabled Pin updates to a specific version = Enabled = Set to 140.2.0 Background updater = Disabled Disable Update = Enabled Manual Update Only = Enabled
After applying the GPO, confirmed this appears within the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\ AppAutoUpdate = 0 AppUpdatePin = 140.2.0 BackgroundAppUpdate = 0 DisableAppUpdate = 1 ManualAppUpdateOnly = 1
At this point, I'm at a loss. We cannot have rapid release be what's installed in our environment. Is there something broken with 140.2.0 or are we doing something wrong here?
Hello! Currently we deploy Firefox via SCCM Package on our machines. The problem is, that Firefox currently only updates itself when you opened it once. This leads to al… (pročitajte više)
Hello!
Currently we deploy Firefox via SCCM Package on our machines. The problem is, that Firefox currently only updates itself when you opened it once. This leads to all sorts of Vulnerability warnings etc.
At the moment these regkey settings in HKLM\SOFTWARE\Policies\Mozilla\Firefox are configured: AppAutoUpdate (REG_DWORD) 0x00000001 (1) DisableAppUpdate (REG_DWORD) 0x00000000 (0)
These two are enough for the updates, when the user opened Firefox (and created a profile).
So we tried the information detailed on this page: https://firefox-source-docs.mozilla.org/toolkit/mozapps/update/docs/BackgroundUpdates.html
To achieve a 100% unattended update we added following Key: BackgroundAppUpdate (REG_DWORD) 0x00000001 (1) which yielded no results. Firefox stayed on his old Version (V131 for this example).
We also added pref("app.update.langpack.enabled", false) in the autoconfig.js File as kind of a 'hail mary' action (bc. the documentation wrote, that this setting should be disabled); but it still does not work.
We've been through this rabbit hole quite some times now, and researching it also yields inconclusive results. (answers like: you still need to start Firefox once, before it can update).
So, what are we missing/doing wrong? Is a true unattended Background Update even possible or is "start Firefox once to create a profile" still the only way to go?
Thanks in advance for your time & help
How do I make sure FireFox has current update? If not current how to update FireFox?
I am a DNS administator at my employers and notice that on my employers network that aus3.mozilla.org and aus4.mozilla.org seem to be returning NXDOMAIN both with our on … (pročitajte više)
I am a DNS administator at my employers and notice that on my employers network that aus3.mozilla.org and aus4.mozilla.org seem to be returning NXDOMAIN both with our on prem DNS and via the public dns providers when a browser attempts update it can fail.
Have other Australian users reported such behavior and are these hosts still valid
DIG
grudd@crayon:~$ dig @8.8.8.8 aus3.mozilla.org
mozilla.org. 2 IN SOA infoblox1.private.mdc1.mozilla.com. hostmaster.mozilla.com. 2024020614 180 180 1209600 60
grudd@crayon:~$ dig stun.services.mozilla.com
services.mozilla.com. 836 IN SOA ns-679.awsdns-20.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
grudd@crayon:~$ dig @8.8.8.8 stun.services.mozilla.com
services.mozilla.com. 127 IN SOA ns-679.awsdns-20.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
grudd@crayon:~$ dig @8.8.8.8 aus4.mozilla.org
mozilla.org. 40 IN SOA infoblox1.private.mdc1.mozilla.com. hostmaster.mozilla.com. 2024020614 180 180 1209600 60
grudd@crayon:~$ dig @8.8.8.8 aus4.mozilla.org
mozilla.org. 35 IN SOA infoblox1.private.mdc1.mozilla.com. hostmaster.mozilla.com. 2024020614 180 180 1209600 60
grudd@crayon:~$ dig @8.8.8.8 aus5.mozilla.org
aus5.mozilla.org. 48 IN CNAME balrog-aus5.r53-2.services.mozilla.com. balrog-aus5.r53-2.services.mozilla.com. 58 IN CNAME prod.balrog.prod.cloudops.mozgcp.net. prod.balrog.prod.cloudops.mozgcp.net. 984 IN A 35.244.181.201
grudd@crayon:~$ dig @8.8.8.8 aus5.mozilla.org SOA
aus5.mozilla.org. 42 IN CNAME balrog-aus5.r53-2.services.mozilla.com. balrog-aus5.r53-2.services.mozilla.com. 52 IN CNAME prod.balrog.prod.cloudops.mozgcp.net.
balrog.prod.cloudops.mozgcp.net. 300 IN SOA ns-cloud-d1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300
grudd@crayon:~$
Hi, I keep getting a message that I should update to a newer version of Firefox on Ubuntu. The problem is: I click on the install for 64 bit button, A ...tar.xz file down… (pročitajte više)
Hi, I keep getting a message that I should update to a newer version of Firefox on Ubuntu. The problem is: I click on the install for 64 bit button, A ...tar.xz file downloads to my desktop, and the process ends completely. How to proceed?
Thanks, Ildikó
When a user logs onto the PC, FF creates the Task scheduler folder but not the task inside. This only get created once the user opens FF for the first time. So as an adm… (pročitajte više)
When a user logs onto the PC, FF creates the Task scheduler folder but not the task inside. This only get created once the user opens FF for the first time.
So as an admin how would I manage the updates for FF when the user never opens Firefox?
We are needing to install the FireFox update to a large group of computers. Is there a script that we can use to update FireFox?
Dear Mozilla Firefox Team, I hope this message finds you well. We manage a network of workstations that frequently utilize the Mozilla Firefox browser. Recently, we have … (pročitajte više)
Dear Mozilla Firefox Team,
I hope this message finds you well.
We manage a network of workstations that frequently utilize the Mozilla Firefox browser. Recently, we have encountered a situation where many of our systems are showing vulnerabilities due to pending browser updates. The updates are being installed successfully; however, users often neglect to restart the browser, which is crucial for completing the update process and ensuring security.
To address this, we would like to inquire if there is an existing Group Policy that can be configured to automatically notify users when they need to restart their Firefox browser to apply the latest updates. Such a feature would greatly assist us in maintaining the security integrity of our workstations and ensuring that users are made aware of the importance of restarting their browsers when prompted.
If this functionality is not currently available, we would appreciate any insights on potential workarounds or future plans to incorporate such a feature.
Thank you for your attention to this matter. We look forward to your response.
I need assistance with updating an old version of Firefox installed in the local AppData folder on our users' machines. We currently use Intune for application management… (pročitajte više)
I need assistance with updating an old version of Firefox installed in the local AppData folder on our users' machines. We currently use Intune for application management, but I'm unsure how to remove the user-based installation and revert to a system installation without losing bookmarks.
Could you please provide guidance on how to:
1. Numbered list item Force update Firefox to the latest version while keeping user data intact.
2. Remove the user-installed version of Firefox using Intune.
3. Ensure that bookmarks are preserved during the update process.
Thank you for your help!
