Well for me it didn't auto update, at least not first 20 minutes until I managed to activate it. If I opened main windows all I had was activation windows which couldn't be closed. There is an option to activate trial version but I didn't use it. After activation succeeded, it auto updated right away. So IDK if they really have covered a situation when activation would fail and how products updates. I'm glad to hear that problem was resolved.
Yes, if trial version activation would succeed. The fact that regular activation was not possible at the time of server problems, I somehow doubt that trial version activation would have different result.
https://help.eset.com/eis/12/en-US/idh_hips_main.html I'm using it but so far it only notified me about registry key changes done by uTorrent and CCleaner. IDK how it performs when (if) infection happens.
Depends on what you mean by this. For example if you set the HIPS to "Interactive" mode, you will receive an alert for any system activity for which no existing user rule exists. Warning - you will literally be bombarded with alerts. This mode is designed to be used after the HIPS has been run for a period of time in "Learning" mode. Eset will create a HIPS rule for any system or app activity encountered while in learning mode. Obviously, learning mode should only be used on malware free devices. The best time to deploy this mode is immediately after the OS and all apps have been installed. You can also create manual user HIPS rules in both the default "Auto" or "Smart" modes and set the rule action type to "Ask." Finally it should be noted that the HIPS processes all "Allow" action type rules first. As such, HIPS rule ordering is immaterial. Also of note is the HIPS uses a hidden internal rule set and these rules will take precedent over any user rules created.
@Minimalist and @mekelek Smart Mode seems a very lite HIPS and not that effective. @itman I meant an Interactive Mode for the Antivirus Module.
That is controled by the "Cleaning" mode selected in the ThreatSense section of Realtime protection settings. See the below screen shot. You can flip through the mode setting options and text will be displayed below it that will explain what each mode does. Also note that there are individual ThreatSense settings for each of Eset's protection mechanisms; Realtime, Internet Protection options, etc.. So one could if so desired have different cleaning options apply. Note that the default cleaning mode level is "Normal." I have all mine set to "Strict" cleaning mode. Eset has the lowest FP rate of AV vendors and something I have never had an issue with when using strict cleaning mode. -EDIT- Correction. There is one area where ThreatSense cleaning mode should be set at the default mode of Normal. That is for Web Access protection. Eset is fairly aggressive in its detection of PUA/PUPS. So you want to be alerted about those. However, I would be extremely cautious about overriding Eset's detections in this area. Their like detection doesn't necessarily imply that the software is just in the nuisance category and it could indeed be much more severe than that.
One of my ESET NOD32 installs was updated to a Product Version of 12.0.31.0 overnight and was requesting a system restart. As that W10x64 1803 system's NOD32 is set to accept Pre-releases, I suspect this version is a Pre-release too as ESET's on-line changelog still shows 12.0.27.0 as their release version. My brief searches uncovered little additional information. Ref: https://www.eset.com/int/home/antivirus/download/ > Advanced download HTH
I have the same OS version. For Internet Security ver. 12.0.27, the default setting is regular update - see the below screen shot. If you want regular updates, change it to that setting.
Hello itman and jadinolf: Thank you kindly for letting the community know that ESET Internet Security was also updated. Well done! Presently, I am truly still okay with my my recent change to Pre-release updates on that Windows system. However, I would like to easily find attributions when these Pre-release updates are made. i.e. - ESET! I know you just updated my system(s) with your well tested final Release Control (RC) but, exactly what did you just do to my system/NOD32? Paraphrasing, I have also posted similarly to the ESET forum. Ref: https://forum.eset.com/topic/17764-changelog-for-pre-release-cycle/ My post is presently hidden pending ESET moderator acceptance. Otherwise, all seems well with my updated NOD32. Thank you.
As far as I am aware of, Eset does not publically publish a release change log until the release is in production mode. The standard procedure for pre-releases is not to apply them unless specifically instructed to do so by an Eset forum mod or Eset support staff.
Hello jadinolf: Five (5) here. Thank goodness for this forum's good friend @Thankful and Newegg discounts...
