So, when is this going to be fixed?
Not yet, because ESET hasn't said anything official or replied to my case yet. Until then, I am reluctant to re-enable the XMON background...
Yes, others are experiencing this problem. Check out the following thread... CPU usage problem on Windows Server 2003
Not to mention that well-designed services shouldn't require constant rebooting of the server just to apply an update!
Well, after the 3223 update, I just re-enabled the XMON. After about 10 minutes, nod32krn.exe went wild again. :thumbd: I will wait until...
Ok. Now it's really bad. I had to disable XMON and (and kill the nod32krn.exe process) because Exchange is not able to sync with the Outlook...
Our SBS2003 server has been experiencing similar problems since yesterday. Suddenly, the nod32krn.exe is running constantly at 50% (server only...
Separate names with a comma.