What are the different ESET product update and release types? KB2256

 

 

ESET products are composed of modules that can be updated with new versions, features and detections at any time. Detection Engine update information is displayed in the main program window of your product. You can also scroll over the ESET icon in the Windows notification area to view notifications. Module updates are announced In program notifications and on an RSS feed. View update notifications on the ESET ThreatSense® Updates page.

The different update and release options for ESET products are:

Regular module updates

Full version release

Repacked build release

uPCU (micro-update)

Program Component Update

End-of-life update

Business products only

 

ESET product versioning numbers follow this format:

[major].[minor].[build].[repacked] or [localization]

 

For example:

11 [major].0 [minor].159 [build].2 [repacked or localization]

Keep your ESET product updated to protect your computers, endpoints and network from malware.

 

 

 

 

Regular module updates

Required or optional: Required

Frequency: Often

Changelog posted: Yes

Known Issues posted: No

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.

 

 

 

 

Full version release

Required or optional: Optional

Frequency: Four times a year (on average, per product)

Changelog posted: Yes

Known Issues posted: Yes

ESET continuously works to improve the core functionality of our products and your  user experience by adding new features and resolving the issues brought to our attention by our users in each new product version.

 

The new version is available to download from the ESET download pages. After testing, the new version is sometimes released as a Program Component Update (PCU).

 

Major new releases are indicated by the first or second number in the product version number (for example, version 6.5 could be updated to version 7 or version 6.6). A regular service release or hotfix is usually indicated by the third set of numbers. For example, 11.0.159 would update to 11.0.160).

 

The changelog and known issues are posted to the product download page, the ESET Support News web page, the RSS feed and our RSS email Newsletter.

 

 

 

 

Repacked build release

Required or optional: Optional

Frequency: Rare

Changelog posted: No

Known Issues posted: No

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 enable the Microsoft patch for the Spectre/Meltdown flaw. 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 in the build, for example, 11.0.159.3 is replaced by 11.0.159.5. What is important to understand about repacked builds is that ESET products with the regular detection modules up-to-date already have the latest version and do not need to reinstall the repacked build.  

 

 

 

 

uPCU (micro-update)

Required or optional: Required (home products only)

Frequency: As needed

Changelog posted: No

Known Issues posted: No

The uPCU update is for updates within the same product version (for example, 11.0.154 to 11.0.159). You will see no option or indication in the user interface of the update.

 

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).

 

Current known issue:

 

Mismatch between PCU version number and installed version number:

This is a known visual issue with uPCUs: when applied, the information in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall is not updated.

 

 

 

 

Program Component Update (PCU)

Required or optional: Optional

Frequency: Four times a year (on average)

Changelog posted: No

Known Issues posted: No

The PCU update is for updates to a newer product version (for example, 10.0.380 to 11.0.159).

 

In certain cases when major changes to the product user interface or core technologies are required, they are distributed using a PCU update. This update is different from the regular module update which only updates modules. In a PCU update, a complete copy of the latest version of the software is downloaded and then installed over your existing ESET product. A PCU is the latest complete version of an ESET product and is released less often than module updates.

 

 

 

 

End-of-life update

Required or optional: Optional

Frequency: Rare

Changelog posted: No

Known Issues posted: No

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 a version 7 (or earlier) ESET product, you will be asked to upgrade to a more recent version.

 

 

 

 

Business products only

The ESET update policy for business products varies by product, version, and remote management status of endpoints.

 

To verify that the latest detection engine and modules updates have been received by client workstations, Check the detection engine version.

 

View the other topics in this section.