I have updated my virus defs and i wanted to post this to tell others to do the same. cause avast fixed the problem with the antivirus blocking google, youtube, yahoo, etc. 
See this Blog report on it, https://blog.avast.com/2011/04/11/false-positive-issue-with-virus-defs-110411-1/
I never had the problem but I just checked my program and I’m still on db# 11411-0 so I never even got the bad one. it says the last update attempt was at 3:02 PM US Eastern time so the bad update must have been put out after that.
It might have been the update servers having been taken down to restrict the number getting this update before they corrected the FP and issued VPS 110411-2 and released the update servers.
Well since it last tried at 3:02PM and my interval is at the default 4 hours, I still have 30 minutes before it will check again and I guess I’ll get 11411-2 then and avoid the problem.
You can also update manually.
DJBone
I’m aware of that but why bother when it will do it in 30 minutes by itself?
Yesterday i let avast delete the files it found in the %TEMP% folder. would that harm my computer by any chance?
CoolMario88cp, you should be ok in a temp folder, but I deleted 500 odd files before my boot time scan fell over, see my post on “5000 High Risk Items Detected”. It appears the delete option in boot time scan (at least) rather surprisingly leaves the infected files in the recycle bin. I was able to restore the files I let it delete so you can probably do the same if you are worried.
JasonLadas, does avast send files to Recycle bin? At boot time? Strange… Aren’t they there before?
its not now also for me… delete means just Shift+delete for avast…(just an example) You can’t recover it unless you have recover my files
Tech and Aish Singh. I’m not entirely clear what either of you are saying. I would have thought that the delete option in Avast’s boot time scan would have done the equivalent of shift-delete to eradicate the nasties forever. I was surprised that the 500 odd files deleted by my boot time scan were still in recycle bin and showing delete date/time consistent with when the boot time scan deleted them.
Your previous post said, that yor boot-time scan “fell over”, which means it stopped erratically instead of ending normally?
In this case, that might be the reason why the files were found in the bin. Not sure about that, but seems to be the only logical reason. Like Boot-Time scan moves them to bin and deletes them when booting up Windows?
Move to Chest is never converted on move to Recycle bin in avast scannings.
Chest is an encrypted folder managed by avast and has nothing to do with Windows Recycle bin folder.
I bet the files were already there, deleted when you were into Windows.
Tech and Zyndstoff. Thanks for replies. In my first post “5000 High Risk items detected…” I detailed the sequence of events, to summarise I ran a Boot Time Scan just after receiving the dodgy VTS and after manualy deleting (not move to chest) about 10 I opted for “delete all”, a bit rash perhaps. After about 500 a file was encountered which couldn’t be deleted, moved, repaired or skipped (this is what I meant by “fell over”. In hindsight it was probably a lucky break! My only option was to escape to abort scanning entirely. I then booted to Vista and ran a full scan from there, 4500ish items detected but no action taken. After a full MBAM scan (40ish low risk items removed) and updating to Avast 6 (of course with a good VPS) the system was clean.
Concerned about the 500 original deletions I checked recycle bin and found to my surprise the 500 items all with deletion time and date consistent with when I ran the boot time scan.
Does escaping from a scan perhaps not allow avast to clear its deletions from the recycle bin?
It shouldn’t work like this.
I hope the programmers could drop some light here. It’s beyond of my knowledge.
I think he has some misconception that avast sends a file to recycle bin when it deletes a virus…
avast just delete the virus no moving to recycle bin is done…