Marcos

You can find that information at https://help.eset.com/updates/.

Unfortunately it is not clear what ESET product you are referring to. Basically manually running update should check for the latest version and install it. You can also find the latest version number on the product download page.

Please provide a screenshot or scan results from VirusTotal if you are referring to a suspicious file.

A 32-bit version would not install on Windows x64 and vice-versa. So you must have a 64-bit version of ESET installed.

The license email (mxxe.hxxxxxy@btinternet.com) and ESET HOME email (m.g.hxxxxxy@btinternet.com) do not match. Is it intentional? A verification email was sent to your license email address.

The strikethrough keys should be removed:

ESET NOD32 Antivirus doesn't contain network protection. Only ESET Internet Security, ESET Smart Security and ESET Ultimate Security do.

The error is not reported with v16 because it's an older version signed with the previous Entrust certificate and having only one entry in the above Provider registry keys for the AV and FW. Unlike the older versions, v17 is signed using an ACS certificate (the Entrust cert. expired last year in December) and therefore WSC created a new key under the Provider key. Since the original key related to ekrn signed by the expired Entrust certificate was not removed (it's undocumented by MS as far as I understood), WSC started reporting the errors. If v17 was installed on a vanilla system where v16 or older was never installed, the errors are not logged. Therefore the solution is to remove the redundant Provider keys related to the previous versions of ekrn.

The files is protected with Themida protector but is not signed. Please make sure to sign files if you want to use a protector, otherwise any future versions will be detected as suspicious too.

You can download the module em000k v1020 from https://forum.eset.com/files/file/131-em000k_1020zip/ or get it from another machine that updates from ESET's servers instead of the mirror with micro updates. In safe mode create the folder "C:\Program Files\ESET\ESET Security\Modules\em000k_64\1024" and copy the 64-bit version (em000k_64.dll) there. This module will be added to the micro update packages soon so that other machines update it from a mirror.

Obviously HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Provider\Fw\{E7B06BEE-DEA6-20D2-58F2-0EB69C7B826D} and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Provider\Av\{DF8BEACB-94C9-218A-73AD-A78362A8C516} keys are still there. They must be removed and the machine rebooted. Those will be removed automatically during a product upgrade in the future. The name of the value is based on the hash of the certificate used to sign the binary so after a certificate change after the original one expired the redundant key caused the above mentioned errors to be logged.

I was unable to find any license registered with your forum email address. Please provide your public license ID in the form of XXX-XXX-XXX.

Has the policy that disables password protection been removed and is no longer being applied on endpoints?

Please raise a support ticket for help with further troubleshooting of the issue.

if there was a policy enabling password protection applied on the client, the only way how to overcome it would be by enforcing another policy that removes password protection or by unassigning the policy from the client.

There's no reason for that if the above keys were actually deleted. I've also tested it with v16.2 upgraded to v17 and the errors were no more logged afterwards.

You can install v17 and then: Take ownership of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Provider\Fw\{E7B06BEE-DEA6-20D2-58F2-0EB69C7B826D} Grant full control to you Delete the key Take ownership of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Provider\Av\{DF8BEACB-94C9-218A-73AD-A78362A8C516} Grant full control to you Delete the key Please modify the registry with care since deleting incorrect keys or values may render the machine unbootable or cause other issues. Create a restore point first.

Basically it should work but it's not a tested scenario.

We expect the hotfix could be available by the beginning of March.

Here's how the results of vulnerability scans factor into decisions on cyber-insurance and how human intelligence comes into play in the assessment of such digital signalsView the full article

We disabled caching on the US backend a few hours ago which seems to have helped.

You can download EAV from https://www.eset.com/int/home/antivirus/download/ -> Show more download options. You can also download it through your ESET HOME account:

I assume the issue is not caused by ESET. Does the issue actually go away if you temporarily uninstall ESET NOD32 Antivirus and returns as soon you install it?

You can raise a support ticket by navigating to Help and support -> Technical support -> Request support which will take you to a web support wizard. At the end you will be provided with an option to create a support ticket.