Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere
Arkiveret

Installing Firefox ESR in Enterprise Enviroments

Mike Kaply replied
WilliCat

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?

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?

Alle svar (1)

I have not heard of this problem. That is surprising.

It might be worth opening a bug at bugzilla.mozilla.org for this so we can work with the installer team.