McAfee problem
Apr 21, 2010 21:15:53 GMT
Post by CharlieChomper on Apr 21, 2010 21:15:53 GMT
This mainly appears to have affected corporate users versus consumers and there has been an update release to resolve this.
However, for those who were not aware, McAfee released an update which was flagging a legitimate and innocent Windows system file as supposedly being a virus and, in the process, was bringing Windows to a halt or causing it to freeze, amongst other "fun" problems that those unfortunate enough to have had it implemented were experiencing.
They had subsequently pulled the update after the bug was reported and appear to have fixed it. However, there are some questioning how something like that even made it past the testing stages or Q&A (Quality Assurance--which, in theory, is supposed to guarantee or avoid things like that from being released. However, in the working world and real world, too often it's the case of where more often than not--especially with software--of where things have slipped by. There are various theories into why...), as it's difficult not to notice something like that to have happen.
However, a number of hospitals (an estimated one-third in Rhode Island, which apparently had to turn away patients due to this problem), police forces and stations, universities, the National Science Foundation, Intel, amongst others were affected by this issue and were brought to a complete standstill where computer access was concerned
This makes the second incident in the past month or two involving an anti-virus/security company false flagging or attempting to even alter a Windows system file or component. The other major incident I actually had experienced.
Trend Micro had released an update (which has also long since been pulled and resolved) which was somehow interfering with or flagged or was attempting to modify a key component involving power management in Windows and resulted in a random and complete computer shutdown (and it sometimes required having to reset the switch in the back of the power supply and wait a few minutes before attempting to reset it again to turn the computer affected by it to turn on again). They caught it within a day of release and had issued a temporary workaround in the form of forcing the program to roll back to a prior update and restoring things so that it was not in any way interfering with that component to avoid shutdowns.
However, for those who were not aware, McAfee released an update which was flagging a legitimate and innocent Windows system file as supposedly being a virus and, in the process, was bringing Windows to a halt or causing it to freeze, amongst other "fun" problems that those unfortunate enough to have had it implemented were experiencing.
They had subsequently pulled the update after the bug was reported and appear to have fixed it. However, there are some questioning how something like that even made it past the testing stages or Q&A (Quality Assurance--which, in theory, is supposed to guarantee or avoid things like that from being released. However, in the working world and real world, too often it's the case of where more often than not--especially with software--of where things have slipped by. There are various theories into why...), as it's difficult not to notice something like that to have happen.
However, a number of hospitals (an estimated one-third in Rhode Island, which apparently had to turn away patients due to this problem), police forces and stations, universities, the National Science Foundation, Intel, amongst others were affected by this issue and were brought to a complete standstill where computer access was concerned
This makes the second incident in the past month or two involving an anti-virus/security company false flagging or attempting to even alter a Windows system file or component. The other major incident I actually had experienced.
Trend Micro had released an update (which has also long since been pulled and resolved) which was somehow interfering with or flagged or was attempting to modify a key component involving power management in Windows and resulted in a random and complete computer shutdown (and it sometimes required having to reset the switch in the back of the power supply and wait a few minutes before attempting to reset it again to turn the computer affected by it to turn on again). They caught it within a day of release and had issued a temporary workaround in the form of forcing the program to roll back to a prior update and restoring things so that it was not in any way interfering with that component to avoid shutdowns.
