After upgrading last night to 4.5.514 I am having troubles with avast.
I use the avast screensaver, and VRDB is configured to update when the screensaver is running. If I leave my PC, the screensaver starts (and I asume VRDB is updating it’s database), but the screensaver and VRDB don’t stop when I start using the PC again. The screensaver is not visible anymore, but I still see the VRDB icon turning and in taskmanager the screensaver process is still present.
I can stop the VRDB update via it’s menu but when I set it again to run when the screensaver is running, it starts again. So it must detect the running screensaver running in the background.
The only way to stop it, is to kill the screensaver process in taskmanager.
My system:
Pentium4 3 GHz (hyperthreaded)
512 MB of RAM
Windows XP home SP2
Grumsel, welcome! 8)
I think the problem could remain into avast screen saver module.
It’s normal that it takes some seconds to interrupt the VRDB and scanning when the screen savers is stoped. But, if it’s scanning big packed archives at that time it could take longer.
Can you try changing the screen saver for a last intensive one?
Can you run VRDB manually and see if, after it finished, the problem remains?
I have this problem with the screensaver not stopping as long as I have Avast. Sofar noone (including myself) have found a way to solve it. And I have seen this problem on several systems and having the vrdb generation enabled or not doesn’t make a difference.
I know the screensaver can take longer to stop when scanning big files, but while scanning it is still visible on the screen (blue square). Or not?
In my case the screensaver was not visible anymore, and VRDB kept on running at least for several minutes, not seconds. It kept on running until i disabled VRDB via it’s menu, or killed the screensaver via taskmanager.
I will try your settings later on. Can’t try them now because I am still at work
Grumsel
P.s. I did not have this problem with previous builds of 4.5 beta.
I have some problems with avast 4.5.514 too, but not with the screen saver. After updated to version 4.5.514 i decidet do do the full system scan. The scaning was fine but after that when i decidet to test the quick scaner, but it didn’t work. After that i start avast but the memory scan didn’t work too. Only the resident scaners were working. After restarting the system everything was fine. But today i did full system scan and after that i had the same problem and had to restart my computer again.
I ran the VRDB update manual and waited for it to complete. After that I enabled the screensaver again, selected to update the VRDB when the screensaver is running. And now I cannot reproduce the problem anymore
I had it twice yesterday, with a reboot inbetween. I don’t know what went wrong and what cured it. Maybe the manual update?
You mean, the VRDB manual update… Maybe. You finished the work and then start the screen saver, this could make it work. Hope that, from now, you do not have this problem anymore
shessobad: it’s not a bug, network shield provider scans your network traffic and it found out, someone from that IP address is e.g. infected with Blaster virus and he attacks your computer (so if you dont have patched windows, you’d be infected). These warning can be disabled in Network Shield provider settings.
