This article explains which Automox agent versions are supported, how to confirm what your devices are running, and what to do about devices that have fallen behind.
Is there a minimum supported agent version?
Automox does not enforce a single version number below which the agent stops working. The supported baseline is the 2.x agent, and the recommendation is always to run the latest available version. Older agents may continue to function, but they no longer receive fixes and improvements and are more likely to behave inconsistently.
The 1.x agent has reached End of Life and is no longer supported or updated. If any devices are still running 1.x, upgrade them to the current 2.x agent. For details, see Automox Agent 1.x End of Life (EoL) Announcement.
Finding the current and latest version
To see the newest available agent version, go to Settings > Agent in the console. The Agent Configurations section displays the Latest Agent Version, along with the number of devices running the agent.
To check an individual device, open its device details page in the console and review the reported agent version.
Note: Image from July of '26
Keeping agents current
Enable the Agent Updates toggle under Settings > Agent so devices upgrade themselves as new versions are released. The same page controls the Agent Release Channel (Stable or Beta), which applies to the entire organization or zone. For a full walkthrough, see Managing Automox Agent Upgrades.
Devices on very old agents may not upgrade in place
Devices running early 1.x agents can lack a working upgrade path to the current release. In that situation the agent needs to be fully removed and the current version installed fresh, rather than upgraded. The removal script in Cannot Uninstall Automox Agent can be used to clear the old agent before reinstalling.
Why agents fall behind
The most common reason a fleet drifts onto old versions is that automatic updates are being blocked rather than turned off. The agent upgrade process runs from a temporary working directory, and endpoint protection or application control tooling that blocks execution from that location will prevent upgrades while the agent otherwise continues to report in normally.
If agent versions are not advancing even with Agent Updates enabled, trust-list Automox in your endpoint protection platform. See Globally Trust-listing Automox Through EPP Application Control. Directory or path-based trust policies are preferred, because a hash-based policy has to be updated after every agent release.
Feature-specific requirements
Some console features require a newer agent than the general baseline. A device can be fully functional for patching while still being prompted to update before a specific capability becomes available. If a feature reports that an update is required, bring the device to the latest agent version first, then re-test the feature.