system
12
No BSODs here either with Win 7 x64 Professional, and Avast 8.0.1489.
Do we think this was caused by an engine update, or virus definitions update? Because I did notice that the latest virus definitions update I can get is 130626-1, from yesterday (June 26) at 6pm. Not sure if that’s my local time or not.
Usually when I boot up my PC I get an definitions update with a date matching that day’s date. So for instance this morning I should’ve gotten an update labeled 130627. Is it possible Avast rolled out a bad definitions update that caused the BSODs, realized what happened and pulled it back?
That would explain why some of us didn’t get any BSODs (because we never got the update), and why reinstalling/updating Avast fixed it for everyone else (because the bad update had been pulled back, so they wouldn’t have received it a second time).
No emergency update from Windows/Microsoft here either, for the record. Windows Update says my last updates were installed June 25, and it’s not showing any new updates that need to be installed either. (Outside some optional garbage like Bing Desktop. No thank you!)