Peter Randziak

Next released versions of ESET products should contain a workaround for this issue.

Thanks Peter this is good to know.

Thanks. I'll have to wait for the next BSOD and report back.

Next released versions of ESET products should contain a workaround for this issue.

Hello @j-gray,
It seems that my colleague reproduced it we probably revealed the root cause.
The licenses are being removed on upgrade of the EEAM. So when it is upgraded to the v7, the loop errors start to appear and after the system reboot it starts to report that the EI connector is not activated.
The solution is to reactivate the EI connector so it will store again the license.
The fix needs to be done on the side of endpoint, the colleague will report it to the team responsible to address it.
Peter on behalf of our EI support specialist
 

Hello @j-gray,
not an issue, one may get easily confused. Also editing the posts might lead to an confusion so better to have it as a new post.
I checked it with the EI support specialist and he told me that this should be addressed in the hotfix release, which is about to come...
It should address the activation issues, issues with the stats reporting (showing the year 1969/1970), high RAM usage and EI connector crashes.
Peter

Hello @j-gray,
sad to hear that such unpleasant issue still affects your environment 😞 
As I mentioned in the other topic, a hotfix which should address such issues is on QA.
Can you please test it wit it, once it becomes available?
If it won't help, we can investigate the issue directly with you.
Peter

attention required / system updates available... working fine 👍
 

ESET Internet Security, home edition (international).  Need Firewall + HIPS.

In particular, Microsoft dlls used by ESET that are located in the ESET install folder will be cross-signed to establish trust without verification using catalogues to prevent excessive reads from catalogues causing significant delays when starting the service until the threshold for killing the service is reached.

The appropriate update files must first be published in the repository. As I wrote, we are working on adding the functionality to enforce autoupdates from the ESET PROTECT console before they are enabled globally for all Endpoint users.

It was still enabled but seems the proxy is buggy, had to remove the proxy temporary until this is fixed (then just turn off web access protection also).

Hello @JimChev3,
we are in contact with the Microsoft regarding this, I hope we will be able to address it together.
During the December we were under an impression that it is a one time issue, sadly it is not.
I agree it is an serious issue, especially for the machines which are not managed i.e. the error is not reported to a central management console...
Peter

Your dedication is awesome 😉 
 
 
Glad to hear that the data and logs were collected and the case is on the  HQ support, I hope they will be able to tackle it with you to reveal what is going on there...
Please keep us posted.
 
Glad to hear that.
Peter

Hi tese23,
this behavior will change in EMSX v10 - mailboxes with (msExchHideFromAddressLists = TRUE) will be displayed

As far as I know, the warning doesn't appear on managed Windows 7 systems, only in the ESET PROTECT console. Is it reported on the endpoints too?

Unfortunately this cannot be prevented once users have admin rights.
If installation / upgrade was password protected, administrators would have to enter the password each time they send a software install task. Needless to say that the password could be different for machines or groups of machines or it could be set by the user himself.

I was at the 10GB limit of the MS SQL Express version.
I upgraded the edition from Express to Enterprise and now I have no problem.

Just reminder for those of you who may be missing the latest update that "Browser's green frame" setting was modified and now when it's disabled, the badge and green frame are not showing at all. It remains only for orange and red status.
EIS > F5 > Web and email > Banking & Payment protection > Browser's green frame

HI guys, i could reproduce it with latest windows updates:


After installation and reboot, the view from PROTECT:

Remediation through dynamic group and run command works! But as stated before, a reboot is preffered.
 

Hi @Lockbits,
I am afraid that I do not, but I shall log this and do my best to update you when I know of a release window.
Thank you,
Kieran

Last night I was busy catching up with the state-of-the-art Apple macOS...

Hope to join the beta-team for macOS soon.

Have a splendid 2023 and cheers to all ESET Team & Insiders / BETA testers on these forums.

/m4v3r1ck 😎

 

Hi @rgoldman,
I would like to add as well that you can also provide the relevant feedback on our new survey which focuses on mail security which are able to find here.
Thanks,
Ingemar

Currently we do not offer a mail server solution for Linux. However, we would appreciate if you could take part in a survey on the future of Mail Server Security for Linux/BSD/Solaris:
https://survey.eset.com/index.php?r=survey/index&sid=964318&lang=en

Thank you! 👏