I upgraded ESET NOD32 from 2.7 to 4.0 on my SBS 2008 server this weekend. Within a couple of hours, Exchange was not working and the computer was freezing. I realized that in less than two hours I had gone from 40GBs of free space on C to < 500MBs, which explained Exchange's not working and other weird behavior. I found a file named NOD7776.tmp, which ironically in my Google search anyway was not found. Plenty of things on NOD777.
I moved the file and deleted it from the C drive and everything was fine. I emailed ESET and tech support told me that indeed it is a known issue and should be fixed in a few weeks with v4.3. I thanked him for letting me know ahead of time.
I then received another email stating quote, "The temp file will reappear, you may want to run a batch file to delete the file daily if you are running out of space on the server until the new release of ESMX 4.3."
So, this leaves me with many questions. How often does it appear. If the batch file runs at 7 am but the temp file is created at 3 am, then Exchange will stop working. How do I know it will "only" be 40GB next time? So, should I create this batch file? Should I uninstall and go back to 2.7 until the new version is out? Should I just turn the AV off on the server?
And, should I write to someone higher up at ESET and ask A) why aren't users being notified, and B) why would you recommend only a week ago that I upgrade knowing that there was a known issue?
The temp file (when it is there) is located at C:\Windows\Temp
If the batch file is possible and would be able to delete the file the moment it is made (I no very little about batch files), then maybe that is doable. So far, it has been 25 hours and no new meter-like temp file.
Thanks in advance.