At each boot-up, I see these messages in the Event Log ... Error initializing file submission system. Virus scanner initialization failed. Antivirus protection will not function properly. In addition, ESET claims the database is current even though the "Version of the virus signature database" is blank. My workaround is to force an update of the Virus signature database. This seems to restore functionality ... or does it? When reported to ESET support, they claim the issue is caused by insufficient RAM or they claim the issue is caused by a corrupt database. My configuration: Dual P-III 1000 MHz; 512MBy RAM; RAID-1 array for C: drive (system); RAID-1 array for D: drive (my data); Windows XP with all current updates applied. ESET support has suggested that I increase the installed RAM. (I can't do that because of motherboard limits). OTOH, their System Requirements state that 45 MB is required. Therefore, 512 MBy should be enough. ESET support has also suggested that I reinstall the product. I have done that. This has never corrected the issue. My current workaround is ... Automatic "Update" "Every time computer starts" (Scheduler) "System startup file check" after every "Successful update of the virus signature database" (Scheduler) I also allow 5-6 minutes between power on and Windows Login so that the signature download and update as well as the startup file scan will have completed. Questions ... 1. Is ESET _really_ working properly? 2. Aside from upgrading to a newer system with more RAM, are there any other changes I could make to eliminate this annoyance. Thanks for any comment or suggestion.