Discussion in 'other anti-malware software' started by elapsed, Dec 2, 2010.
So much for protecting the users :/ Are companies really feeling so desperately pressured by malware now that they will skip proper QA?
More like desperate to fix bugs in the 2011 product line, that they won't even properly test the upgrades, which come out buggier. lol
Yeah. I was testing out AVG IS on my main PC when this came through. BSOD'd on reboot. To fix it I booted up in linux and renamed the AVG folder in program files. That let me boot my system and remove AVG.
Hmmm, updates again huh
It's a bad gaff though. A lot of people seem to be using AVG at the moment. There's no excuse for this dodgy update, it will have caused a lot of people serious grief.
Updates like this mean more money in my pocket. Thanks AVG
Last time it was NOD32, before it was Norton (I guess), I wonder, which AV is gonna to be the next in terminating Windows.
Avast destroyed Windows a few weeks/months ago (FP disaster) so I guess it will be Avira
I hear that.
I was contracted to a major financial institution and sitting at my desk when this one hit:
Time and a half over time: 17 hours!
I didn't hear from Norton, maybe you mean McAfee? They were the most recent that I know about, and Avast of course.
One more feather in avg's cap
Fixed it for ya
Just another reason I dont run an AV,for reasons such as this issue.
Moral value of the story: Sometimes, having the *latest* up-to-the-minute updates can bring more harm than good.
Back to topic - I'd think that AVG ought to have learnt something from their past mistake by now....they can't afford to screw up PCs by such repeated incidents. Not only does it bring grief to its users but it'll tarnish their image further...no matter what they say (explanation of why it occurred) or how many words of apologies they offer. Not even free licenses to Pro versions can repair the damage although that may calm down the situation by a small margin...
I don't know what others think but I'd rather swallow a few 'harmless' FPs that bring slight annoyances rather than a stupid update that messes up everything. All this is under the context for those using AVs.
This has happen to me twice recently with Avira where after receiving an update i got the infamous BSOD. Whats the deal that windows is so hard to work with now? Whats changed recently? Does it have anything to do with Windows anti patch guard?
This is one of the reasons I tend to trust MSE. You'd think MS would be careful with their own product. I hope anyway ...
There's only 4 certainties in life:
4. and one day your AV company will push out an update that nuke's your PC
As far as I'm aware since MSE doesn't root itself so deeply into your system with drivers and such, it shouldn't be capable of doing this. That's the good thing about it being a Microsoft product, they use they own API calls for MSE, which many vendors just ignore.
You'd also assume they wouldn't detect any critical system files either - though you never know.
Did I miss (or sleep through while it was corrected) something catastrophic?
Can you post a link?
Edit: Now I remember, an FP issue about a year ago. We "GMT+11" types did largely sleep through it and none of my clients were affected. I'm checking with W7 64-bit AVG 2011 users now.
Thank you AVG, McAfee etc.
Pretty embarrassing. And all this time I've been thinking the major FP incidents were bad.
I had this problem with AVG Internet Security. I did not get a bluescreen but the real-time antivirus component would not work and i had to do a fresh install of AVG. It was not a big deal for me
the ultimate security solution?
"if it don't work, it don't get infected!"
Well, there's the upside ...
& there's the downside ...
Separate names with a comma.