st3fan

Does anyone know when Endpoint Antivirus version 10.1.2063.0 will be available via the auto-update mechanism? We would like to upgrade to this version due to the reported vulnerability (CVE-2024-0353) but our endpoints are not receiving this update yet (auto-update policies are applied). The update is only downloaded if a manual "check for updates" is done but it is not automatically deployed via the auto-update option yet.
Thanks,
Stefan

Hi everyone
I am busy testing/installing the latest Windows Updates on Windows Server 2016. After the reboot I noticed that ESET (Server Security 9.0.12013.0) did not start. I am setting this in the Event Viewer.
The ekrn service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.

 
Is anyone else seeing this?
 

Hello guys,
the module which implements the new EoL messages behavior has been released for general public.
Peter

This is great news. @Peter Randziak please advise when this will reach the regular update channel? Thank you.

Hello guys,
few moments ago we released a module update to pre-release update channel so far, which will adjust the EoL messages behavior and those will be reported in the management console only in the managed environments.
Thank you for the feedback and use cases provided.
We apologize for the inconvenience caused by this.
Peter

Any news on this please Marcos?
9.1.2160 is still a real PITA with Outlook and shared mailboxes - makes them hang, crash, slow down to a complete crawl.
Still having to put some clients back to 9.0.2046 which is the last known good working version with Outlook
Thanks

This is a perfect example why it should be up to the IT teams to determine whether (and when) an update should be applied.

I'm not sure about @st3fan's use case, but updates always carry the risk of breaking stuff. Which is why we test new releases before we roll out to thousands of managed devices. Eset has quite a history re-introducing problems that were already fixed in past releases (like here ).
Another point is, that large companies usually have a software managment system that might undo your automatic update (downgrade) - just to watch eset redo the update - creating race conditions and reboots along the way...
So every time you decide to ignore an explicit "do not update automatically" configuration our whole software management team starts to panic...
We love the "waiting state" feature for updates - but PLEASE give us a chance to choose the activation date of this feature by ourself!
In an enterprise environment we justify decisions for/against updates to our management and to our customers - not to Eset.

Thank you.

Is the HTTP proxy affected by CVE-2021-44224 or CVE-2021-44790 (see https://httpd.apache.org/security/vulnerabilities_24.html)?
I would assume yes for CVE-2021-44224 since it is configured as a forward proxy (ProxyRequests on) and no for CVE-2021-44790 since mod_lua is not enabled. Would appreciate if ESET admins could clarify and update the now outdated apachehttp.zip (https://www.eset.com/int/business/download/eset-protect/#standalone) from 2.4.51 to 2.4.52.
Thank you,
Stefan