I updated from EAV 3.0.667 to 672 on 8/23/2008 and began experiencing the above failure reported by NOD32, while at the same time the Windows Security Center error message indicated that NOD32 reported it was out of date. System is XP Home with SP3, ASUS P5K MoBd with E6750 CPU, 2 GB Memory and Nvidia 9600GT video. After a couple of days of occasional same errors, I uninstalled build 672, manually deleted remaining files/folders mentioned in other Posts, cleaned Registry with JV16 PowerTools 2008 Registry Cleaner and then reinstalled build 667 only to find that I now had the same error occurring daily. On 8/26, I did a System Restore back to 8/22/2008 (before the update to 672), after which NOD32 showed build 667 and had the same errors on start up. I manually initiated a Manual Update 2 times and it finally updated to vs 3390. Did full system scan with NOD32 and House Call with no problems found. Same problem started again on 8/31 and I gave up, uninstalled NOD32 and installed AVIRA. Since I still have 1 3/4 years left on my NOD32 license, I will continue to monitor the Forum to see if ESET fixes this problem. Question: can I install version 2.7 using my license information for version 3?