Discussion in 'other anti-virus software' started by FanJ, Oct 21, 2019.
License checking seems to be #1(Telemetry), no improvements I can see.
You haven't seen this?
I'm not sure what you are talking about.
Are you talking about the Telemetry module?
That is about the Customer Experience Improvement Program.
You have the option not to participate if you don't want to.
Check your settings in Advanced setup -> User Interface -> Customer Experience Improvement Program
2. No Improvements?
You need to read the changelog given by Marcos. I already have given the links and info given by Marcos.
And, BTW, you should better read the following thread at the Eset forum about BSOD reported by several users; it seems to have been fixed in this version 13.1.21
I just installed NOD32 after having had stopped using it for a year. I see a few changes that I am not sure about.
1) When I installed it using the downloader that I got when I bought it, it didn't ask for a product key and just activated automatically. Is that something new I guess? Pretty neat.
2) What I'm confused about is under exclusions there is performance exclusions and detection exclusions, can someone explain what is performance exclusions?
I can handle one item. NOD32 should have asked for license information and a few other things.
I've been using ESET products for years and it never failed to ask me.
oh no this is my 2nd installation, it doesn't ask for any info, it installs and activates right away. I think maybe this is a new thing since I downloaded the installer by logging in to My Eset there is a download button right next to my license.
O.K. Well, you explained that.
There have been a couple of forum postings about this happening. I assume you originally purchased from an Eset web site? Suspect the "Live" installer these use just auto activate Eset with the purchased license key.
In a nutshell, performance exclusions are Eset real-time scanning exclusions. In other words, the file will never thereafter be scanned. So if the file contains malware that Eset did not detect initially but at some later subsequent time does; e.g. new signature, behavior, etc., the malware will not be detected by Eset. It is recommended that only detection exclusions be employed for this reason if the detection is due to PUA, etc., and the user insists on using the software.
Version 126.96.36.199 released
I got it offered via the internal updater. (I'm on the regular release channel)
Reboot required as usual.
Go there to the advanced download option
Added: Windows 10 H2-2020 Compatible
Added: WMI Scanner scan & System registry scan option added
Added: IPM improvements: Gamer Mode support, Expired product pop-up support
Improved: BPP: Visual improvements
Improved: product install and uninstall analytics
Minor bug fixes and improvements
At the moment I don't see it yet announced at the Eset forum; that will come later.
I'm afraid that I have an elderly moment (or how do you call that?):
What means "IPM" in "Added: IPM improvements: Gamer Mode support, Expired product pop-up support"?
@Minimalist 's right. see this link.
First scan with the new version took forever...about 15 minutes for a 500 GB SSD
15 minutes is forever? LOL. I just ran a scan for comparison. SSD x2 RAID 0. 500 GB partition. 113 GB used. 52 minutes.
Thanks for the heads up!
Anyone else seeing WMI errors in the Reliability monitor/Event log after a scan with the corresponding WMI option checked?
Yes i have seen a lot of errors on my system system scan log. I thought first the eset update would be broken
Yes, during Initial scan wmiprvse.exe crashed on my system also. Checking Initial scan log I see unable to open error  on 55.341 files on my system partition, so I don't know if they were actually scanned or not.
Thanks @Minimalist and @imdb !
You're most welcome, @Thankful !
Just received an in-product update for NOD32 to v188.8.131.52
Edit, sorry didn't realize it was posted earlier by FanJ
Usually my full, custom scan took 5 - 8 minutes.
Now, with those two new options enabled more than 40 minutes.
(one internal SSD together with one internal HDD). Win7.
Wow! 26 minutes. I have never timed it before but I'm sure it never took more than a few minutes. I noticed that there was a warning before I started it. Really something.
you're welcome, @FanJ .
It's the Registry scanner folks that is taking so long to run. On my Win 10 1909 build an On Demand scan of only Registry and WMI took over 21 mins. to complete. To make matters worse, most of the file references it tried to scan were locked by the OS.
Bottom line - if your want faster scans, don't scan the Registry.
Separate names with a comma.