There's a chance I'll be flamed, but I can't stop myself shouting NOD 2.7 has some design problems. Minor or major depends on what side you're looking at the problem. If it is a minor glitch, easily fixable once Eset spots out the problem, or something bigger, something related to NOD's architecture. If you recall I've allready spotted out in the past some conditions where NOD locks up the computer: - Amon: Accessing sector/damaged CD - Amon: Accessing some network files when in offline mode Today I can definitelly add another case: - Amon or Dmon: accessing Office documents Symptoms are always the same: - computer locked - mouse hourglass - keyboard only responds to ALT+TAB, showing the ALT+TAB dialog (but the task switch does not occurs) - No task manager availability - CPU usage is normal - Pc needs hardware reset / power off I'm not kidding, tricking; what I write here comes from more than 5 months of usage on 4 PCs each one whit it's own config, server and workstations. The computer showing locks with Office documents has a brand new install, due to hard disk change: it has a freshly installed XP professional, freshly installed Office 2003, NOD 2.7 + Zone alarm 6.x. And after a few days it started locking up. That is after the xth lock up I've decided to uninstall NOD and see what would happen. Since then, the computer did not lock anymore. I definitelly think it is a design problem, even if I don't know exactly how NOD works. Nevertheless using the product and observing how it beheaves I've came to this conclusion: NOD modules manage a queue of files to be scanned and this could explain why NOD is so fast scanning; when possible, queue up accessed files and when possible do the scan. Till that moment, delay requests. If this is the approach, what happens if a file gets unaccessible? Probabily a computer lock; especially if NOD kernel is running in very low priority ring and has the capability to lock ALL the processes running. If that is the case Eset should change the approach to something different; manage timeouts and do something, instead of locking up the PC. I understand that it is difficult to spot out the problem, but Eset should start seriuosly to work on the problem. I did allready go thorugh Eset's support but came out after one month of mailing with nothing and quite disappointed about it. Now for privacy reasons I'm not publishing mailing contents between me and Eset, but it ended all with nothing. At this point I'm asking NOD users to post they're experiences and thoughts, wishing Eset will try to do something. I currently own five NOD32 licenses till november 2007 and would like to renew if this tedious flaw will be complitely fixed. I hereby ask the forum admin not to move this message in a previous thread, to be sure that it captures the attention of every user.