User2345

Well, I have a test folder with 347.322 JPEG files (~18GB). Takes ages to scan that folder. Like said, I wouldn't bother if my system would be utilized during that scan but it is idling the whole time. So for me it looks like the engine is the bottleneck.

Hi, I am currently evaluating ESET NOD32 Antivirus. I am testing on a high end workstation with 32 cores CPU, 128G RAM, latest PCI Gen4 NVMEs (doing 7000MB/s): That's a very long time. I wouldn't bother that much if system would be utilized during that scan by the engine but it wasn't: My expectation: Scan should use 100% system resources to finish the scan ASAP. If it is designed to run in background, it should have detected that system was idling and scale up after 5-10 minutes like any other background job would do.

Thank you, this will explain a bit. However, it reveals a problem in categorization: It doesn't make sense to categorize one toolbar as adware and handle it as a threat but categorize the other just as PUA which is basically doing the same.

Interesting, "Exclude signature from detection" can be selected for PUA:

Hi, I am currently evaluating ESET NOD32 Antivirus. It is detecting the following installer in my folder where I am archiving all my installers: I am fully aware of this "threat" and I want to keep this installer. Enabling "Exclude signature from detection" sounds exactly like the setting I want. However, this checkbox is disabled with the result that when I click "Ignore threat" button, that the same dialog will show up again whenever Windows Explorer, Total Commander or any other tool will access this folder.

Not sure if I understand the last comment correctly: I am currently using ESET NOD32 Antivirus 16.0.22.0 and are experiencing exactly the same problem when trying to enter my master password for KeePass on Microsoft Windows 10 Version 22H2 OS Build 19045.2193. I hope this will also be fixed for NOD32 Antivirus and not just Internet Security... Can you share an ETA when 16.1 will be available?