Update in NOD32 beta 6.0.11.0

This is probably just an event confined to this day and time, but I noticed that when I did a manual update today, I got the updates for the program modules that were released today and then I ran the manual update again and got the entire download again. I repeated that and got it one more time.

In between these, I checked the advanced settings for update and decided to uncheck the option to regularly check for latest product version, in case that affected updates, but that seemed to make no difference.

Finally, when I ran update manually one more time, Eset found no new updates, so I guess it just took a while to clear the cache since I did not force that. If anyone else experiences this or even notices this when there is a program module update, maybe it is something worth investigating. Otherwise, there seems to be no problem with automatic updating in the program.

 

How much data is downloaded? In Megabytes.

 

Approximately 45MB (actually 45091 KB). It appears to have happened again this evening. I checked and it was a full download, but to be sure I did a manual update and it downloaded the same 45MBl. It reports the program modules have been updated, but, in fact, they are the same versions and dates as this morning, so they are simply being overwritten. I recall the same thing happening to others with older versions of Eset, so need to look up the thread on clearing the cache to get it to stop. However, why it started in the first place is a mystery to me. It was not happening until today, 6/28/2012. Every time it downloads the entire set of 12, it completes the download, installs all 12 and the quits and reports that the program modules have been updated, so the download and installation are not failing. However, the update module apparently doesn't have data to indicate that the modules are up to date. Blackspear's old instructions on clearing out the update cache don't seem to apply. There is no file named "nod32.000" nor is there a folder named "updfiles." I am not sure if there should be in this version of NOD32.

I was looking at the properties of files in the Eset program folder and noticed that ekrn.exe shows version 6.0.12.0, whereas egui.exe shows version 6.0.11.0, which is the version reported by "about" for the program. I wonder how that happened and why they do not match?

 

Switch the update channel from pre-release to regular in Advanced setup.

 

I thought about doing that, but it seems to have settled down today and I'm not planning on doing any more manual updates for a while. I also unchecked the option to have the program check regularly for new versions. I don't think it had anything to do with the update issue, but it was just something I did to see how it works and not something really necessary.

I do not want to revert to an earlier version of the internet protection module if switching back to the regular updates as opposed to the pre-release will roll back the version of the internet protection module. The most recent 1041 version of the internet protection module fixes the problem with Microsoft Update. I realize that being on the pre-release cnannel also makes things more likely to be unstable, but I'm using the beta version anyway. I'll just ride it out at this time. I can see that did an update today, but I was not observing it and don't know how long it took.

OK, I bit the bullet and just did a manual update check. NOD32 reported no update necessary, so it is working as it should today, and I still have it on pre-release.

 

Wow, it seems cache is not only supported in the regular updates.

I remember the cleared cache in v4 pre-release, as the modules were downloaded anyway.

 

I did not even go to the knowledge base to look up how to clear the cache in current versions, but do see that updates are now stored in the application data folder in documents and settings. I did not fiddle with those at this time, because I wanted to see whether the update would heal itself. It seems to have done so, for now. It's just interesting to follow this from day to day. Maybe there is some useful information in this for the developers, if they are monitoring the beta pages.

 

I finally did switch back to the regular channel after the update downloading issue reoccurred. No problems since then, so I suppose that is just something that can happen with pre-release, though I had not experienced in the past so far as I can recall.