"Dustin"  wrote in message 
news:XnsA36C898311960C9X238BHEUFHHI5RJ791@94.75.214.90...
>
>Mark Warner  wrote in
>news:lq4j3a$n51$1@speranza.aioe.org:
>
>> On 07/15/2014 06:04 PM, Dustin wrote:
>>> "Buffalo"  wrote
>>>>
>>>> You sure jump to conclusions without the facts.
>>>> When she emails me the add-ons (that's what she called them) I will
>>>> post them here.
>>
>> My conclusions were based on the facts offered, and my experience
>> dealing with infected Windows computers in the field. With more
>> facts/evidence, those conclusions can change, no doubt.
>
>Okay. I still didn't see anything specific enough to make the determination
>that the Avast in question was a fake.
>
>>> Avast has done the same to a number of my clients.. It's also forced an
>>> image reload at one point, when it wrongly removed something.. I've
>>> seen what you described happen before is what I'm saying.. hence my
>>> question to Mark.. :)
>>
>> If you say so. Personally, I've never seen such behavior from Avast (or
>> any other AV for that matter), which in itself may not mean much as I
>> don't claim to have seen it all, but... this is the first time I've even
>
>I suppose you've never seen AV actually fuxor a mailbox file either...? I
>have. AV/AM, nice tools, but dangerous to let them make critical decisions
>without your input. One bad definition file can result in a hosed system.
>
>> *heard* of such behavior, and I'm plugged in to a lot of security
>> related groups, both public and private. If I'm wrong, I'm wrong, but it
>> sure struck me as a classic rogue that had snookered a clueless user.
>
>Well, as I said, I've had it do things. It's called a false positive and it
>acted on it; It was doing it's job, removing what it thought (incorrectly
>though) was malware. Malwarebytes sadly has done the same thing. As has
>Norton/Mcafee etc. This is nothing new.
>
>> I've had numerous machines described as acting exactly as the OP's, and
>> in every case what they were calling their anti-virus was actually the
>> rogue.
>
>I've seen those instances as well, but like I said, I didn't have enough
>information from the OP to make that determination. I've seen AV and AM
>####up and mistake good files for bad ones...it happens.
>
>
>
>
I realize it is very difficult to come to the proper conclusions without the 
proper facts.
I was just wondering if others here had similar problems with the free 
Avast.
I will post the items that Avast found as soon as I get her to send the 
names to me.  Hopefully.  :(
After she did the System Restore, Avast found the same items which she did 
ignore this time. She hasn't got back to me yet with the names she said she 
copied down and I think the part of Avast that detected them.
Sorry for the lack of info. Since she doesn't install new programs much, I 
just figured that perhaps Avast (I use it also) might have had a problem 
that affected a lot of users with their last updates.
-- 
Buffalo 

--- NewsGate v1.0 gamma 2