Detection Engine update information is displayed on the home screen of the main program window. It can also be viewed by scrolling over the ESET icon in the Windows notification area. In addition to those in-program notifications, module updates are announced on an RSS feed. View or subscribe to update notifications on the ESET ThreatSense® Updates page.
ESET product versioning numbers follow this format:
[major].[minor].[build].[repacked] or [localization]
11 [major].0 [minor].159 [build].2 [repacked or localization]
Are you a Business user? See the Business products section.
ESET continuously works to improve core functionality and user experience, add new features, and resolve customer feedback by releasing new product versions.
The new version is available to download from the ESET download pages. After appropriate testing, the new version is released as a Micro Program Component Update (uPCU).
Major new releases are indicated by the first or second number in the product version number (for example, 6.5 could update to 7 or 6.6). For a regular service release or hotfix, this is usually indicated by the third set of numbers, for example, 11.0.159 could update to 11.0.160).
The changelog and known issues are posted to the corresponding download page, to the ESET Support News web page, and available by email or RSS Newsletter.
Your ESET product checks for new components including product modules and Detection Engine updates many times each day. Along with our other multi-layered technologies (such as DNA detection, behavioral detection and blocking and Machine learning), regular module updates help to ensure that you are protected against the latest known threats.
Verify that the latest product modules and Detection Engine have been received: Update ESET Products—check for latest product modules.
You can view module changelog history from the Virus Radar Update Info page.
In the main window of your ESET product, click Update → Show all modules to open the Modules dialog window.
The uPCU update is used to deliver both major releases (for example, 10.0.380 to 11.0.159) and feature updates (for example, 11.0.154 to 11.0.159).
There are two different uPCU updates: Differential uPCU contains some patches or files (.dup), whereas a full uPCU contains all product files except modules (.fup).
In certain cases when major changes to the product user interface or core technologies are required, they are distributed using a uPCU update, which is different from the regular module update. In a uPCU update, the program downloads a complete copy of the latest version which is then installed over your existing ESET product. A uPCU is the latest complete version of an ESET product and is installed similar to regular module updates but is released less often.
Refer to the article Free Upgrade Available message or New version available for more information.
Security and Stability Hotfixes address critical issues and ensure the maximum security and stability of your ESET product. The timing of hotfixes is determined entirely by their security impact.
Security and Stability Hotfixes are distributed in the same way as uPCU updates. However, users cannot disable automatic Security and Stability Hotfixes (even when they disable regular uPCU updates) due to their nature and importance.
Before installing the Security and Stability Hotfix, your ESET product may display "Security Alert. Restart required." or "Security and stability update to newer version is prepared. Restart your computer for all changes to take effect". If you have more updates pending before a restart, your ESET product will update automatically to the latest version and install all hotfixes.
Sometimes ESET must react to emerging security issues by replacing a full version with a repacked build.
For example, ESET was one of the first security vendors to allow the Microsoft patch for the Spectre/Meltdown flaw to be enabled. To ensure that ESET versions are compatible with future security issues (for example, new Spectre/Meltdown Windows Update distributions), we will sometimes replace existing builds with a repacked build.
A repacked build is indicated by the fourth number, such as 220.127.116.11 replaced by 18.104.22.168. What is important to understand about repacked builds is that ESET products with up-to-date regular detection modules already have the latest version and do not need to reinstall the repacked build.
ESET products that are nearing or have reached their end-of-life will ask you to automatically upgrade to the latest version compatible with your system.
For example, if you currently have version 9 (or earlier), you will be asked to upgrade to the latest version. "Your product is outdated" message—what does that mean?
The ESET update policy for business products varies by product, version, and whether endpoints are remotely managed.
Verify that the latest detection engine and modules updates have been received by client workstations: Update ESET endpoint products (7.3 - 9.x) on individual client workstations – check for latest product modules
See the information about the ESET business products that support auto-updates.
Follow the procedure to opt-out from auto-updates in the latest version of ESET PROTECT and ESET PROTECT Cloud.