Peter Randziak

Losing FDA is macOS issue. We did workaround for it in ECS 7.4.1600.0 and EEA 7.4.1500.0 too. We did nothing for V6, because V6 was not affected by this issue during our compatibility testing with Sonoma. 

If you need EES v6 for some reason and could not upgrade to EEA, you should wait until Apple fix that issue in macOS.

Just for my information, what functionalities from EES V6 are you using that prevents you to upgrade to v7.4.1500.0 ?

A newer version of the Cleaner module 1245.1 with a fix is going to be released later today which will most likely address this issue.

After December 7 it won't be possible to install any version of ESET on systems without Azure Code Signing (ACS) support. This is because Microsoft has deprecated cross-signing program and the current Entrust certificate expires on December 7. Afterwards it will be possible to install and upgrade ESET only on ACS-enabled systems. Some other AV vendors have required ACS support for some time already, the others will require it when their current cross signing certificate expires.

Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved

Hi Peter, 
It looks good! 
 

Hi Peter,
I will give a go when we are in the off peak time, estimated in 8~10 hours.

Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved

Thanks, Peter! Appreciate it! 
No problems! I can confirm that 
- I restored the update
- Upgraded with the latest modules
As a result, both ESET Server Security and ESET Mail security worked as expected!

Hello @Peter Randziak, the patch is fixing my issue, sorry for the late reply since i thought the patch is deployed 

Thank you for your hardwork

Hello @howardagoldberg
the module updates were fully resumed at ~13:00 CET (November 14, 2023).

Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved

Thanks for your great job. We're still analysing this scenario and preparing a few changes to the code flow that may lead to the result you're achieved.
I will ket you know, when current module fix will be fully released (but I think change of module update server setting fom pre-release to release doesn't downgrade modules)

Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved

Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved

Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved

Can confirm, it's working on all servers. Thank you Peter.

Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved

Yes I admit that the information provided in the alert was not up to date and accurate. The situation was quite dynamic and new findings were emerging...
As of now, it is up to date https://support.eset.com/en/alert8521-error-during-auto-updates-in-eset-server-security-for-microsoft-windows-server 
We apologize for the inconvenience caused.

Error persists after restarting the server. (tested for ESET Mail Security 10.1.10012.0 and ESET Server Security 10.0.12012.0 in 3 cases). In all cases ESET went green, and after 1-2 minutes back to red again. I sent one ESET Log Collector file @Peter Randziak

Good day everybody 
the same error is appearing on Windows Servers 2012-r2, apparently over the last module update.

thanks for the reply, here's the log, i use default profile collection
eis_logs.zip

Hello @bart_c,
I understand that for the advanced users, it might be a step back in terms of the ability to configure / fine-tune the product, but for standard users or even advanced ones it brings features for which there was quite high demand, like the apple silicon native version to name just one of many.
On top of that one user mentioned that the new version improved significantly performance of the time machine backups, which is often reported by users as an issue...
As I mentioned the version with the Advanced preferences available is to be release quote soon, so hopefully it will fit your needs and preferences...
Peter

Hello @NeilB,
thank you for the feedback provided.
The initial release comes with a features, which are essential for our users and we are aware of the demand for the additional features.
When it comes to protection, key component is the Real-time file system protection so if a file is being executed, accessed or created it is scanned by the product to ensure the protection.
A release with the Advanced preferences included is planned in upcoming weeks, it will improve the user experience for advanced users...
Peter

I can see from private message you send me that you quarantine is full of detected trojan infections. You should delete it to clean quarantine but you said you can not do it because there are files that are not infection and you want to restore it? You cannot restore that files because product GUI is not working and not show quarantine content. Do I understand it correctly?
 
I've send you how you can list commands for command line manipulation of quarantine. You are able to do everything with quarantine from command line what you need, like in GUI. In case of GUI is not working it is only one way how to restore file from quarantine.
 
This command prints you help for command line utility quar
"/Applications/ESET Cyber Security.app/Contents/MacOS/quar" --help
 
You should list help to read quar command. The you should list content of your quarantine. Then you should identify files you want to restore if you are sure that restored files are false positive, you should setup exclusion for this file to not detect it by real-time file protection again. then you could restore it  then you should delete rest infected files from quarantine it is better to setup exclusion before you restore detected file otherwise protection will detect it and put into quarantine again  
BTW: how do you know that detected files are false positive?
 
I advise you to run custom scan with 'In-Depth Scan' profile active on you whole disk. It seems that you iMac need it. It could take a time until it will finish because you have a lot of applications on your disk.
 
 

I know they are false positives as I have reported them to ESET in the past, it is flagging some WINE files as suspicious and rather than asking me it just quarantine them
https://www.codeweavers.com/support/wiki/mac/mactutorial/bitdefender
The detected trojans are ones I reported to ESET from scam emails I got. (mail program bug is downloading files even when I tell it not to), I reported them via fwd the email to ESET's sample email address.
Can you send the last ESET logs to the devs I sent in the DM so they can find the bug in the ESET GUI?
I have run an In-Depth Scan already and do a few times a year.