I am experiencing the same problem with this public beta that I have had for a long time with the release version on my XP box. I cannot copy the log files without having my RAM usage shoot to 100% and NOD32 control Center freezes and I have to resort to killing the nod32kui.exe in task manager. After trying to copy the logs, I then cannot even VIEW the logs without NOD32 control center SILENTLY crashing a few minutes after I view the logs. This problem occurs on the release version and it was because of this problem that support gave me an early beta to try. That early beta seemed to fix the problem. Now though it is back in the public beta. I also am unable to complete a full scan of the C drive with this public beta on the XP box. The scan hangs on a particular file ...same file each time and the logs show that NOD32 scanner is running when it it has actually stopped on this file and then silently crashed. The file in question is an ordinary file in my downloaded programs folder on my desktop. The release version has no problem with the file and scans the entire C drive as it should. (The release version does have the problem with NOD32 crashing silently and not allowing copying of the log files). When I originally experienced the almost constant crashing of NOD32 Control Center and Mark sent me the early beta, he thought I might have some application running that is severely conflicting with NOD32 but I sent a Hijackthis to him and did not hear anything back so I think he didn't see any application that might be causing this conflict. It appears that NOD32 release and beta do not like my XP Pro box. NOD32 beta runs fine on my W98SE box as did the release version one and two. These constant problems with NOD32 on my XP box are one of the reasons that I will not be renewing my license as I mentioned in another thread. I also have a false positive that I submitted to Eset back in May. It is still not fixed two months later. I don't see any way to exclude the folder when I run a full on demand scan. I have excluded it for AMON. (Of course, I cannot run a full scan so it doesn't really matter).