ESET product

ESET Windows Server products

Product version

Versions 6.4.x and below

Lifecycle status

End of Life

ESET product

ESET Windows Server products

Product version

Versions 6.5.x

Lifecycle status

Limited support until August 2021

Operating system

Windows Server 2003

End of Life date

July 14, 2015

Details

Windows Server 2003 is no longer supported by Microsoft

ESET product issue

SHA-1 certificate expiration

End of Life date

December 2020 (some products expired January 27, 2020)

Details

ESET has obtained replacement certificates to sign binaries of its Windows products because both ESET’s SHA-1 and SHA-256 code signing certificates are expiring in a short time.

Operating systems or ESET products without SHA-2 support will no longer update modules, including the detection engine, ultimately making your ESET product not fully functional and unable to provide sufficient protection.

ESET released high-priority information in Online Help for each ESET Server product for Microsoft Windows on how to resolve it: SHA-2 required compatibility

ESET product issue

Cross Certification issue

End of Life date

April 15, 2021

Details

Important! The certificate used in ESET products is signed by a trusted certification authority (TRCA), and this TRCA can be signed by different TRCAs. The mutual trust relationship between two specific TRCAs is expiring and will not be renewed, as the digest algorithm is SHA-1, which is no longer secure.
Newer ESET products use more secure and up-to-date certificate chains that meet security standards and do not expire on April 15, 2021.
This issue is not dependent on the Windows operating system version, and if you have the ESET products mentioned below, it will happen on Windows with the latest updates.

More information

ESET product issue

Legacy products startup issue

End of Life date

February 7, 2020

Details

ESET has identified that our kernel has a problem with verification of the timestamp of an already expired certificate (expired by 7th Feb 2020). This method fails and our modules in older, legacy versions, are declared as untrusted and therefore are not loaded. This mechanism ensures that no untrusted library is loaded.

As a result, the affected versions fail to load modules (HIPS, Update, Device Control, Web and Email protection) and are not functional, therefore the protection is not functional.

For more information, refer to the ESET Knowledgebase article.