UPDATE # 3 Consider me a less than satisfied customer. I purchased a 2-user license of NOD32, primarily for the ability to exclude certain directories (+subdirectories) whenever I wanted to do a manual scan of a given drive. I have 100s of thousands of files that are archived on different drives, that I do not want to repeatedly scan. I do, however, want to be able to manually scan other files on those same drives, whenever I wish. Whenever I list an exclusion (e.g., "D:\DATA\*.*") and then do a manual scan of drive D:\, NOD32 scans all the files in D:\DATA\*.* anyway. In my case, it is an issue of time and resources. I don't want NOD32 spending 3 hours scanning files that I specifically excluded. I uninstalled version 3 and installed version 2.7 = same exact result. ESET might as well acknowledge that the Exclusion feature does not work as advertised. I am disappointed that not one ESET staffer has responded to this thread (over 500 views). I think there is a message there. UPDATE #2 - When I originally posted this topic, I thought my problems with "Exclusions" would be quickly explained and resolved. This expectation was loosely based on the fact that I had read numerous (recent) threads with responses from posters who appear to be ESET employees (the term "we" was often used in their responses to various problems). If ESET staff are reading this, how about some help? The only response I have received from tech support was an email that said - "Your request for support has been received and will be reviewed shortly. Case #61701 - "exclusion is not working properly" has been created for you." Maybe I am expecting too much? or too soon? I will give this a couple more days then if no response, write it off as a bad choice/waste of money and move on to something that works as advertised. Thanks to Rupert for the initial responses to this thread. UPDATE #1 I tried terminating the ekrn.exe process in Task Manager and it appears to have been terminated. No warning messages that program was locked by system, etc. Also, none of the exclusions are working for me now. This is a major pain, because I prefer to do periodic scans but NOT for the older archived files. If the exclusion option was working, it would be a tremendous time saver. I would like to try version 2.7 to see if it works as it is supposed to. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Hello - I am a new poster to this forum but have perused it many times over the years. It is one of my go-to sources for reliable information. I just purchased a 2-user license for NOD32 (3.0.563) and installed it on my clean system. I have encountered 3 immediate issues that I would like to share with the ESET community and hopefully someone can help in resolution. I also called ESET Tech Support and emailed detailed info to them. I will share their response as soon as I receive it. [I should note, ESET phone support is excellent. I was quickly in contact with a human - no endless loops of recorded menus - and she was extremely courteous.] ISSUES: 1) The scan times were slow. 3.2 hours to scan 740,000 files on (2) 320GB SATA drives. Kaspersky (KAV 7.0) scanned the same drives in 1.23 hours (number of files differed slightly = 728,000). This is not a life or death issue with me, but one of the selling points for NOD32 was the speed advantage, particularly over KAV 7.0. 2)Exclusions - I have 8 logical drives on the 2 physical SATA HDD in my system. I have some archived files and some music files that don't need to be repeatedly scanned and that I want to exclude. If I opt to exclude " D:\DATA\*.* ", I expect the scanner to skip this directory and all of its subdirectories (24) when I do a manual (custom) scan. It does. This specific option works exactly as it it supposed to. Unfortunately, this is the only one that works. If I exclude " E:\Music\*.* ", then run a scan of drive E:\, the scanner scans every single file in " E:\Music " and every single file in all the subdirectories of " E:\Music\*.* ". This same anomaly occurs for every other exclusion that I choose - EXCEPT for " D:\DATA\*.* ". Tech support seems at a loss for this odd behavior, but is working on the problem. For clarification, my system is set up thusly: Windows XP Pro SP2 SATA Drive 0 = C:\, D:\, E:\, F:\ SATA Drive 1 = G:\, H:\, I:\, J:\ AMD X2 3800+ Comodo Firewall Pro 18.104.22.168 WinPatrol 12 Absolutely clean system (no malware) This exclusion feature is extremely important to me. KAV 7.0 worked fine on the same system, using various exclusions. (BTW, Norton Ghost image used between installations of KAV and NOD32 to ensure clean slate). 3)No Self-Defense ? - When NOD32 is setup to display in Advanced Mode, and I go to the menu item "Setup" (upper right hand corner) and click on "Advanced Setup" from the drop-down box, the entire NOD32 program freezes. Nothing can be accessed and the program cannot be minimized or closed. The only way to close the open menus, is to use the Windows Task Manager and end the "egui.exe" process. This actually kills NOD32 and it has to be restarted from the Start>Programs menu. This is a huge concern. KAV 7 (and most other high end antivirus apps) have a self defense mechanism that prevents such easy termination of protection. This is obviously the biggest issue here. I would like the "freeze/lockup" bug addressed, but I am worried that using NOD32 will make me a sitting duck for any malware that focuses on terminating the AV process. If anyone else has experienced these problems with version 3 and has a solution, it would be appreciated. I have never used v. 2.7, so don't know if these are teething problems for a major udpdate or not. Thanks for any help.