Toate produsele Community Forum

Hello everyone,

We have been using Mozilla Firefox ESR (32-bit) in the organization for several years. For installation on our clients, we use "Matrix42 Empirum" as the software distribution tool. All it does is install the MSI of Firefox.

However, for quite some time now (almost 2 years), we have been facing an issue where some installations are marked as successful (Error code 0), but once the MSI installer is automatically closed, files like "firefox.exe" disappear from the installation directory – despite the installation being marked as successful.

The problem doesn’t always occur, but a repair attempt usually resolves the issue.

In addition to Empirum, we also use Defender for Endpoint, but we couldn’t find any clues there.

Is this problem known, or are we the only ones experiencing it?

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?

bold text

If you have a legitimate question, please start a new question at /questions/new with details.

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.

Hi. On an Active Directory, we deploy Firefox (normal or ESR). It's OK. When we deactivate the link of the GPO, it's supposed to uninstall. But it doesn't (even if we delete the GPO, specifying to uninstall at once).

The gpresult command on each computer doesn't show the GPO anymore, but Firefox is still installed.

( FYI, we used to do that with FrontMotion Community Edition, and it was always working (instal and uninstal). We even just tried the "last" (but old) ESR edition present on the FrontMotion site (CEESR-102), and it works. But FM CE version has stopped being developped. )

So, any idea about why the official Mozilla Firefox version (normal or ESR) doesn't uninstall?

Thanks by advance.

We use Firefox ESR in our environment today, Is it possible to have a policy that would display "update required" message to end-users, or have it automatically update without users opening the browsers.

Debian 12 Linux on Dell laptop. Current "updated version" Firefox ESR 128.4.0esr (64bit) I received an update notice for Firefox ESR this morning. After running the Update, I lost the status bar. How can I get it back?

Le 05 novembre 2024 Bonjour, Je ne parviens pas à faire la mise à jour FireFox. J'utilise un MAC OS X version 10.9.5 Processeur 2,7GHz Intel Core 15 Mémoire 8 Go 1600 MH DDR3 MERCI de bien vouloir me répondre en Français. Bonne journée. Cordialement.

No matter which option I choose, I keep getting a message that tells me Firefox cannot be updated. The Oesr version wont update either. It tells me to update to 115.17 Oesr and when I click on update I keep getting this error.

Hi,

Looking to upgrade our org to ESR 128.2.0 due to compatibility issues - most notably, embedded PDFs not loading due to Promise.withResolvers() not being implemented on versions prior to 121.

Curious to know if there are any issues or concerns with upgrading manually/pushing this version out - would like to ensure we don't cause further issues in attempting to resolve one.