We have installed version 4 on few PCs and servers using Server 2003 last week. Since then we have huge problems with our file servers! Some of our servers are failing on a random times hanging and when you’re trying to log in to diagnose the problem it’s at either "preparing network connections" or "applying computer settings". The only solution is to do the hard reset! Of the 4 file servers all of them are crashing after upgrading to version 4! That looks like performance issue. Also we have noticed that users using Software storing data on the fileservers are reporting huuuge slowdown. Operations which were taking 15 seconds when server was running version 3 now are taking about 3 minutes!!! That problem resolves turning off real time file system protection, but server crashes anyway later on! Yesterday morning I have uninstalled version 4 and installed version 3. As servers didn't last more that 24 hours without crashing on version 4 now it's working fine again. The only problem with version 3 is that it's stopping to update randomly on the servers with error: "Virus signature database could not be updated. Undocumented serious error (0x101a)". We were advised by Eset support to update to version 4 to fix this issue as we can't restart file / exchange servers or reinstall NOD32 anytime it happens. And that was the biggest mistake of all! Since last week people lost their documents as servers stopped responding and crashed. I have logged a call with Eset support on Wednesday as this is absolutely CRITICAL to have the problem fixed. We are not the only ones with the problem as I found many threads on the internet like this: http://www.wilderssecurity.com/showthread.php?t=235012 My local support is saying he didn't get any response from headquarter about the issue!!! The only advice is to come back to version 3. But there are updates issue with version 3 which are still not sorted! Now I am thinking that there's a reason why people are using big names like Symantec or McAfee and staying away from small brands like Eset. It's simply because the support sucks in Eset! The problem with updates on version 3 stayed untouched by support for months! Now there even bigger problem with version 4 and there's no response from Eset.... Regards!