Windows - Software - Install Mozilla Firefox

What the Firefox Installer does

This Automox Worklet™ installs Mozilla Firefox on Windows endpoints by downloading the latest stable release directly from Mozilla's official download server. The Worklet automatically detects whether your endpoint runs a 32-bit or 64-bit operating system and downloads the corresponding MSI installer package.

The Worklet queries Windows registry uninstall keys to detect existing Firefox installations. It checks both the 64-bit registry path (SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) and the WoW6432Node path for 32-bit applications on 64-bit systems.

For 64-bit systems, the Worklet uses a scriptblock execution pattern through the native 64-bit PowerShell environment (sysnative\WindowsPowerShell) to handle the installation correctly. This approach prevents architecture mismatches that can occur when the Automox agent runs in a 32-bit context on 64-bit Windows.

Why deploy Firefox through Automox

Manual browser deployment across multiple endpoints consumes IT resources and delays new employee onboarding, preventing users from accessing applications that require Firefox. Mozilla Firefox provides an alternative browser option that many organizations require for application compatibility, user preference, or security policy compliance.

Automating Firefox deployment through this Worklet standardizes browser installation across your fleet. The Worklet downloads directly from Mozilla's official servers, so you always deploy the latest stable version with current security patches.

The Worklet includes installation logging at C:\ProgramData\amagent\Firefox_install.log, giving you diagnostic information if installations fail. You can also verify Firefox deployment status across your organization through Automox reporting.

How Firefox installation works

1. Evaluation phase: The Worklet searches Windows registry uninstall keys for "Mozilla Firefox" in both 64-bit and 32-bit registry paths. If found, the endpoint is marked compliant and no action occurs. If not found, the endpoint proceeds to remediation.

2. Remediation phase: The Worklet creates a staging directory (C:\temp\Automox\FirefoxInstall), downloads the MSI installer from download.mozilla.org, executes msiexec with quiet installation flags and logging enabled, waits up to five minutes for completion, and removes the staging directory after installation.

Firefox installation requirements

• Windows 10 or later

• Network connectivity to download.mozilla.org

• Write access to C:\temp\Automox directory

• Administrative privileges for MSI installation

• No user configuration required - all parameters are predefined

Expected state after Firefox installation

After successful remediation, Mozilla Firefox appears in the Windows Programs list and registry uninstall keys. The Firefox application icon becomes available in the Start menu, and users can launch the browser immediately. Users gain access to a standardized browser deployment with current security patches.

Installation logs are saved to C:\ProgramData\amagent\Firefox_install.log for troubleshooting. The staging directory is automatically removed after installation. Subsequent Worklet runs will detect the existing installation and exit without action, marking the endpoint as compliant and demonstrating consistent browser deployment across your organization.

How to validate install mozilla firefox changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for install mozilla firefox.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as New-Item, Out-Null, New-Object, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install mozilla firefox. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Write-Output, Get-ChildItem, Get-ItemProperty and remediation operations such as New-Item, Out-Null, New-Object. Use these indicators to verify that endpoint changes match intended policy outcomes.