[KB8271] ESET application update and release types (Business users)

Issue

• Keep your ESET security applications updated to protect your servers, endpoints and network against the latest known threats
• ESET applications use a modular design that enables new and updated versions, features and detection modules to be added at any time
• Module updates and auto-updates difference
• ESET applications release types

Details

Solution

Related solutions: Home and small office users

Module updates

Your ESET application checks for new components, including application modules and Detection Engine updates, many times each day. Along with the other multilayered technologies (such as Machine learning, DNA detection, behavioral detection and blocking), regular module updates help protect your device against the latest known threats.

To verify that you have the latest application modules and Detection Engine updates, you can manually check for the latest application updates.

Auto-updates

Auto-updates replaced Micro Program Component Updates (uPCU) in ESET PROTECT 9.0 and ESET PROTECT 3.0.

Auto-updates deliver both major releases and feature updates. There are two different Auto-updates types: Differential auto-updates contain some patches or files (.dup), whereas a full auto-updates contain all application files except modules (.fup). During the full auto-updates, the application downloads a complete copy of the latest version and installs it over your existing ESET application.

You can pause auto-updates in ESET Windows endpoint applications or in ESET PROTECT or ESET PROTECT On-Prem.

For ESET solutions that consist of multiple components (for example, ESET PROTECT On-Prem), ESET may not update the application version number each time one of the components is updated.

For more information on auto-updates, see ESET Endpoint Security for Windows auto-updates FAQ.

ESET applications release types

Feature updates

• Distributed via: Repository, web installer and auto-updates
• Required or optional: Can be paused
• Frequency: Three times a year (on average, per application)
• Changelog posted: Yes
• Known Issues posted: Yes

Feature updates consist of major and minor version releases. Feature updates introduce significant improvements, new feature additions and major changes to the application user interface or core technologies. Feature updates may also indicate operating system or software requirements changes. ESET application support levels and lifecycles are always linked to a Feature update.

Servicing updates

• Distributed via: Repository, web installer and auto-updates
• Required or optional: Can be paused, except for required security patches
• Frequency: As needed
• Changelog posted: Yes
• Known Issues posted: Yes

Servicing updates consist of build and patch version releases. Servicing updates provide fixes and improvements that are essential for security and stability. These updates do not add or remove functionality; they only fix or improve existing features.

Security and stability hotfixes

• Distributed via: Repository, web installer and auto-updates
• Required or optional: Required
• Frequency: Rare
• Changelog posted: No
• Known Issues posted: Optional

ESET uses Security and Stability Hotfixes to address critical issues and ensure the highest level of security and stability of your ESET application. The timing of hotfixes is determined entirely by their security impact. You cannot disable Security and Stability Hotfixes.

Repacked builds

• Distributed via: Repository, web installer and auto-updates
• Required or optional: Optional
• Frequency: Rare
• Changelog posted: No
• Known Issues posted: No

Sometimes ESET must react to emerging security issues by replacing a live application version with a repacked build. The purpose of a build repack is to include new configuration modules (CE) in the installation packages available on the download pages and ESET PROTECT or ESET PROTECT On-Prem repositories.