New
#11
Nope - for a while there I was getting the same thing - *immediately* after Avast! updated itself.
I think the update was FUBAR'd - happens from time to time.