The server hasn't been updating its virus signature database in the last few days, and upon trying to do a manual update, I get the following error message: "Base file missing". Here is a screenshot of the error: I've tried to find a solution for this problem on the ESET website, as well as on Google, but this hasn't been successful. I still couldn't find out what was causing this problem, but upon advice from ESET support, I re-installed ESET NOD32 and cleared the Update Cache. In previous versions of Windows I did get more driver updates directly through Windows Update automatically. Another example of updates (available from the Windows Update Catalog), but not being brought in through windows update were the Azure Power pack found here: Eset contacted me and will do a remote screen sharing session to see what's going on.Remarks know some of the answers below, yes windows update provides generic drivers for some devices, but also provides drivers which are the same as the ones provided by oems, the Lenovo power management drivers for example are identical, whether I install them through windows update or Lenovo.And, even more embarrassing, Service Pack 2 RTM for Windows Vista and Windows Server 2008 are released and ESET is not able to offer fixed software that will solve the severe problems related to Service Pack 2. You can’t treat your customers with such incredible arrogance and ignorance.Smokey “Just to let you know, the web pages ESET posted on the matter have been revised, problem explanation and FAQ (Newsbulletin): I do not presently have any deferred updates and I'm otherwise up-to-date.
I've had about 40 machines connected to an ERAS server and periodically they all would receive update module errors such as "could not connect to server." The problem has to be resolved by manually clearing the cache in ERAC and downloading the updates again.The remaining drivers I seem to be missing are those for printers.One can't update these from Device Manager as the drivers listed there are all of the generic local printer queue type.Embarrassing: the total lack of feedback from ESET regarding the issue.Like I today already wrote on DSLReports, looking at all the threads and posts in their own support forums regarding the severe Service Pack 2 related problems, like e.g.system crashes, BSODs aso, and the fact that (apparently) ESET refuse to communicate with their PAYING customers about the SP2 related occurances, it is evident that ESET will lose customers.