MarcFL

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. 

Why fix what wasn't broken?
Prior to the "update" all my devices were visible there with their corresponding license.  Now I have to wrestle the devices  from my family and re-register them.  Why?

Updating Eset NOD32 to the new version 14.1.19  fixes this issue.  You will be prompted to login to your license manager account by Eset NOD32 in Windows after the update is installed and you reboot.

Hello MarcFL, I have to say I have noticed the same bug in licence manager, that happened right after my eset.som portal was updated at 21st of this month. Before the update everything was working well. I hope they will fix this bug soon. At least I know that I'm not only one with the same problem.
With best regards MTPP

Same Here.  I purchased Eset DIRECTLY from Eset.  Thanks for looking into this Marcos.
In my case, the setting "Display Marketing Messages"  was set to a question mark "?" (center of slider).

I have IN-PRODUCT MESSAGING (display marketing messaging) disabled, but this popped up a few minutes ago.  Hope it was a one-off.
NOD32 Antivirus 14.0.22.0
 
 

Always seems backwards to me that users are given the opportunity to upgrade to a new version before they are able to consult a changelog.

The documentation for any general releases are available from the offline installer page on the Eset website.

Under the advanced options for each particular download
 

Appears Eset has changed how it is announcing and detailing new releases: https://support.eset.com/en/kb7674-what-s-new-in-eset-version-14-home-products

Resolved - the long way:  I restored an backup image.  The 13.2.18 update was prepared but not installed.  I went into Eset advanced settings and disabled Protocol Filtering*.  Then uninstalled Eset and rebooted.   Installed 13.2.18 using the offline installer and internet is working again. 
*Could not do this with a fresh install of 13.2.18 because you can't get into settings without registering and you can't register without internet.  You can't even activate evaluation without internet.
Not happy Eset.

Done.  Thanks.

This is happening on my client workstations throughout the country.  This is an Eset issue.  Thanks.

Several different computers in different states with Eset NOD32 v12.0.31.0 are randomly reporting this error:
During execution of Update on the computer xxx the following event occurred: File not found on server.