Marcos

Is ESET Online Scanner crashing during a module update?

It is also possible to create exclusions from filtering by IP addresses and certificates as a workaround.

Only ESET CyberSecurity Pro 6.11 is available with end of life to reach on August 31, 2024.

What password are you referring to? If you have purchased a license recently, please provide your license public number in the form of XXX-XXX-XXX.

What are the risks and consequences of having your health data exposed and what are the steps to take if it happens to you?View the full article

I'd recommend allowing all outbound communication for ekrn.exe and egui.exe, otherwise you may run into issues with some other services as there are quite many of them that ESET uses as you can see in the KB.

It is not actually a bug, we merely started to scan nodejs communication in order to detect nodejs malware payload. An easy solution is to tell nodejs to use the system CA cert.. store by running: node --use-openssl-ca https://stackoverflow.com/questions/29283040/how-to-add-custom-certificate-authority-ca-to-nodejs Alternatively (less safe) you can add nodejs executable to the list of applications excluded from TLS filtering.

If you don't know the password, you'll need to redeploy the management agent on clients using the current server settings and certificates.

The issue has been reported to developers. P_EESW-11455

The EI server is probably too busy with some tasks. Please raise a support ticket to determine the root cause and to find a possible solution.

There was a typo in your license email address which has been fixed by your local ESET distributor today. Please try to add the subscription to your ESET HOME account again.

A verification email was sent to sxxxs@sxxxxxxxxxxxxxd.com.

My Modules folder is 684 MB in size. Please run: dir /s "C:\Program Files\ESET\ESET Security\Modules" > modules.txt and upload modules.txt here.

A new log is created there with each on-demand scan. Most likely you have "Log all objects" enabled in a particular on-demand scan profile which causes logs to be extremely large. You should disable that setting.

Very theoretically, e.g. if they got infected when the disk was connected to an infected machine.