MarcFL

The real question is why is this Eset service being invoked on Eset consumer versions: https://help.eset.com/protect_admin/11.0/en-US/epns.html ?

Hi Peter,
Today, my customers reported the same issue.This issue may be occurred on some customers.

@Peter Randziak Is there any update for this? We are using Protect Cloud and this has been going on for at least 5 days. Should we be logging support tickets for this?
I'm also seeing no indication of this issue at https://status.eset.com/.

Yes, that's correct. The ESET Push Notification server is having intermittent issues and repair is underway.

It is the website of ESET ME. If you are from the Middle East region, please report it to ESET ME. The page doesn't exist for other countries, e.g. https://www.eset.com/us/support/sysrescue/#download or https://www.eset.com/uk/support/sysrescue/#download.

It's fixed in v17.1. which is now available for Insiders to test.

👍

After years of frequenting this forum, I can state with confidence the following.
Eset "silence" to a posted problem means;
1. Yes. its a problem.
2. Eset doesn't want to discuss/admit the problem publicly.

I've given this situation more thought.  Eset should pull this faulty update immediately.   I have multiple devices and I also manage other home users with Eset.  I have no desire to reinstall on all those devices - most with custom settings.   Please advise if this will be fixed in a future update.  Also advise if this "Browser Protection" module is still operational even though the configuration page is missing.  Thank You for your assistance.

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

What you have pinned in the forums is the wrong advice! Servers that haven't rebooted still have the real time protection working. If you reboot you lose malware protection. Rolling back updates does not work.
Tested with Eicar file. Please advise people NOT TO RESTART THE SERVERS until the issue is solved!

If eicar is not detected, the advanced setup window will be likely blank as well. In such case a reboot should resolve the issue and modules should load alright then according to our tests.  We continue working on finding out the root cause.

This should not be necessary, as MarcFL wrote, clicking Dismiss in the warning should suffice and the protection status will be green. The eicar test file is detected then so protection seems to work fine. We'll make some further tests to make sure. So far it appears to be a glitch with the notification during modules reload after update.

Add me to this list....only 2012 servers so far. if i dismiss error on the server...protection status shows green across the board...both 7.x and 8.x versions of file security...

Am also seeing this across every Server 2012 R2 ESET Server security install, been on hold for USA Business support for 10 minutes trying to check with them about this. I don't think I've seen it on newer server versions but as far as I'm aware 2012R2 should still be supported by ESET for another year?

ESET creates industry-leading signatures and is good at detecting known ransomware.
But I hope ESET can improve its behavioral blocker or introduce protected folder function to better deal with unknown ransomware.

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?
 

Are you sure you can still import exclusions like this?  This is what I have done in previous versions, but in the latest version it will not import an exclusion for a whole drive, the import will only accept subfolders.

Thank you for this. I have been pulling my hair out for days trying to figure out why notifications were not displaying when both Desktop Notifications and HIPS blocking verbosity were set to Warning. Once I dropped desktop notifications to informative they started functioning properly. This is definitely a bug.

Reported this bug to Eset:
BUG REPORT
Details: My custom HIPS rules are set to "Notify User" and Logging Severity set to Warning.   Under Desktop Notifications, Minimum Verbosity of events to display - It is also Set to "Warning".
Bug:  No desktop notifications appear when a HIPS rule is triggered.  
But they should appear because "Desktop Notifications, Minimum Verbosity" is set to Warning AND the HIPS rule is also set to Warning.    
Note: If Desktop Notifications, Minimum Verbosity is set to Informative, HIPS notifications appear.    
See Attached Screenshots and Forum post with all the details of this bug:
https://forum.eset.com/topic/28730-hips-notify-user-not-working/

Thanks for your reply.   The notifications should display when minimum verbosity is set to Warning as I explained.  I have no desire to set it to Diagnostic or Informative as a workaround.   I hope Eset fixes it.

Closing this topic due to trolling. The OP obviously also lyed, initially pretending to be a user who accidentally felt a victim of ransomare and then he turned out to deliberately perform amateurish tests by skewing the reality to bash ESET in favor of his favorite AVs 

Since you seem to be so keen on BitDefender's anti-ransomware behavior protection, note that it's not bullet-proof:
https://sea.pcmag.com/security/5981/bitdefender-antivirus-plus

Yes, but if you login to the web portal, all of your devices are there but shown as, "not connected."
Wouldn't it be easier for the customer to re-activate the device from the web portal?
I didn't disconnect the device - ESET did.

Token engine was changed and new pair need to generated. Otherwise previous registered apps/devices will be `NOT SEEN` in myESET and their status will be misleading. 

Removing all them from myESET (devices, not licenses!) and pair them again in app via login to myESET in App fix issue. 

Sadly Devs does not inform people about this steps for properly myESET work.