You have just got to feel so, so sorry for those using Bit-Defender (also Bullguard and F-secure I think also use the same bit-defender definitions)
An definition update went crazy flagging just about every file on folks computers as a trojan. Many pages last night of anger and anguish
Massive fail.
More reason for me to stick with MBAM and AVG.
It was a massive fail of epic proportions. I hope Avast and MBAM will never get those problems.
"We are sorry for the inconvenience" (post#38), has to be a prizewinning understatement.
The ultimate public relations response. Love it.
Popcorn please.
Richard S.
It was a massive fail of epic proportions. I hope Avast and MBAM will never get those problems.
Avast already had that problem just months ago back in the v4.8 era, it was completely useless until the next definition update.
Avast already had that problem just months ago back in the v4.8 era, it was completely useless until the next definition update.
Bit of a difference here Andavari, some of the Bit Defender users have no working computers now.
The last time an AV had a FP in Windows's own files was AVG, I think. But it was only one FP.
hazelnut >> I'd rather say "Nearly all x64 BitDefender users"
There is even a compensation thread as well
For some people without the knowledge of how to boot into safe mode, do repair installs etc when they have just a black screen must be very distressing indeed.
Some folk will not even know about this issue and just assume that the Fake Alert trojan killed their computer.
The only 'positive' thing to come out of this seems to be the number of people who have praised Windows 7's ability to repair itself, not appreciated I guess until a situation like this occurs.
And some people will think "hey, I've got the new Windows 7 but my friend who has Windows XP and BitDefender too didn't have any problems !", since nearly all XP users are x86 users.
Bit of a difference here Andavari, some of the Bit Defender users have no working computers now.
Yeah that could be a difference although what Avast was detecting back then would've wiped out Windows if a user let it clean up the "infections" because it detected just about everything imaginable. AVG already did the dead PC trick a few years back themselves. That's why I don't let any AV software automatically do anything related to detections without me being in the decision making loop.
El Reg's short article ... http://www.theregister.co.uk/2010/03/22/bi...r_dodgy_update/
El Reg's short article ... http://www.theregister.co.uk/2010/03/22/bi...r_dodgy_update/
That was a good read, and indeed it was the problem Avast had once had too.