I have updated from avast free 5.0.667 to 5.1.864. I did this by clicking “update program” under maintenance.
I have three shields running (file system shield, network shield and webshield)
file system shield and network shield is not scanning anything.
file system shield says “files scanned / infected : 0 / 0”
network shield says “connections scanned / infected : 0 / 0”
webshield works though
the eicar test files are not picked up by the file system shield…
Ive tried rebooting several times,
any ideas?
Windows 7 ultimate 64-bit, no other security software running, intel i7 920 system
UPDATE : I uninstalled avast, rebooted windows and did a clean installation of avast 5.1.864…now it works normally.
looks like doing upgrade from a previous version is broken somehow?
Im glad I clicked the “real-time shields” and saw the “files scanned 0” indicator, otherwise my computer would have been vulnerable without me knowing it.
Avast was reporting “Secured. your system is fully protected” when in fact the file system shield was doing nothing.
This is annoying. I’ve had such problem during beta test which was later gone when i re-installed avast! so i couldn’t reproduce it. I suggest you re-install avast!, that will fix the problem for sure. But i agree, it’s problematic because avast! is showing that everything is fine but in relaity it’s not scanning anything.
I have updated from avast free 5.0.667 to 5.1.864. I did this by clicking “update program” under maintenance.
file system shield says “files scanned / infected : 0 / 0”.
The avast tray icon never moves when I open programs.
edit: I just fixed it by uninstall/rebooted windows and did a clean installation of avast 5.1.864…now it works normally, but I might not have even noticed the problem if I was not reading this forum! I have another PC with Win XP, it updated fine, maybe it is just a problem for Win 7 64 bit?
Windows 7 Professional 64-bit, MBAM Pro security software running, Intel i7 950 system
This seems like a serious problem indeed since it doesn’t seem to be an isolated event. :-[
Maybe it would be a smart idea to stop the auto update and investigate this further before too many users are affected. But there doesn’t seem to be any particular rule for this problem to happen hm.
I’m also having problem as well on my current system XP Pro SP3 lucky for I’ve clone my last backup before the new version came out so I’m back to Avast v5.0.677 :-[
Hmm… Indeed this was reported by RejZoR in one of the beta builds but we could never simulate it here. The upgrade path from v4.8 to 5.1 was tested on a number of different systems and we couldn’t find a single problem.
Now, it would be really useful to find out what’s different about your systems.
To help us analyze the problem, please ZIP the following directories
In my case I was upgrading from the previous stable build (5.0.677) to the last version of the 5.1 beta that was released. Unfortunately I did a clean install so can’t provide a zipped copy of the install dir.
I’m also having this problem with Windows 7 x64 systems. Every one of them were completely “silent” after GUI update from build 5.0.677. x86 XPs updated ok. Fortunately Avast is so easy to re-install, so I ended up doing that.
Quite serious bug though, if people don’t check their AV after update.