End Program - Missing virus definitions when logging off
Has anyone any ideas why a Windows XP system running Symantec Antivirus Enterprise 10 should keep on displaying a popup window (with prompt to end) titled 'End Program - Missing virus definitions' when the user attempts to logoff ?
I have tried uninstalling SAV, removing everything I can find in the registry, rebooting & reinstalling SAV to no effect. SAV looks OK, the virus signature files are current, as is the SAV client code & a full scan runs clean. I cannot find out any more details of which program might be causing this as the popup only exists for maybe 5 seconds before disappearing.
It is very frustrating, especially as this is happening on a PC I have been building for a new ghost image & I don't want this problem spreading.
Re: End Program - Missing virus definitions when logging off
Yes! I have exactly the same problem!
I found this forum via Google and yours was the one single hit .... so either there are only two of us, or else it doesn't bother other people. I have done the same things, i.e. remove, reboot, reinstall, several times, all to no avail. I've also gone back to recent previous editions (10.0.1, 10.1.5000) with the same effect. I'm now on 10.1.5010 on XP, mine is Corporate Edition on my home PC because I VPN into work.
I've never seen this particular problem before, even though I've been using SAV for almost 10 years. One clue though ... I recently upgraded to a savagely fast quad-core PC .... perhaps a faster PC shuts down quicker as well, and something in SAV doesn't like that?
In my case it's just a minor niggle (everything else works fine), but if you're creating a sysprep image then it's a show-stopper really ... could I suggest that you don't install the SAV client on your image, but instead include it as part of the installation process to manually install from the SAV server? If you want to automate that you could do it with AD Group Policy, or something like LanDesk. Something that needs to be updated continually like AV software is not a good candidate for inclusion in a sysprep image.
Anyway if I get any information on what's causing this problem I'll update people here.