If it was a issue with Mc Afee, why did I have to pay that money myself for the repairs?We have individual reports of other versions of Windows being affected as well.
The affected systems will enter a reboot loop and loose all network access.
This attack by the malware creators is quite insidious since many of the people searching for information about this problem are most likely already affected by the problem and are looking for a solution using another computer..." .
I had that issue back in 2010 with my then new Dell Inspiron Laptop running the new Windows 7 and I had to spend $600 with a Dell technical support agent for them to remotely remove a traces of Mc Afee from the laptop and install Norton 360.
I was lucky, but I am angry because Mc Afee never told that there was a problem, on the web site, Technical Support or other media. Do you have any suggestions for breaking out of the Windows XP Repair loop? We have seen poisoned search results since the problem first surfaced.
Search terms such as Mc Afee, 5958, or DAT are returning results that can lead to malicious and fake antivirus scan sites, resulting in the installation of malware...
The problem is a false positive which identifies a regular Windows binary, "svchost.exe", as "W32/Wecorl.a", a virus. Several readers reported that this procedure worked to recover: 1 - Boot the system in "Safe Mode" 2 - copy in c:/program files/common files/mcafee/engine 3 - reboot. I have contacted Technical Support by chat on another machine (without Mc Afee) and I have never been told that there was any problem with the latest update although I asked for directly. When the news broke, I was cringing waiting for the phone to start ringing off the hook.....silence IS golden! The repair made it to the Installing Devices portion and then rebooted. it wants to continue running the repair, but it can't.
If you are affected, you will see a message like: Mc Afee released an updated DAT file, and an "EXTRA. If you lost "svchost.exe", then you need to copy it back to c:/Windows/system32/while in safe mode. tstart=0 Mc Afee Knowledgebase Article: https://kc.mcafee.com/corporate/index? I finally found how to fix my computer through a blog. Now the system is stuck in an endless boot loop in the middle of the repair. Now that I know about the Mcafee problem, I could fix it if I could just get back to the desktop.
The bad DAT file may infect individual workstations as well as workstations connected to a domain. Please keep it coming using our contact page: Guy Bruneau IPSS Inc.
The use of "e Policy Orchestrator", which is used to update virus definitions across a network, appears to have lead to a faster spread of the bad DAT file. gbruneau at isc dot sans dot org We're seeing this issue as well. We were able to stop the spread of the bad DAT file with our e PO server and were able to push out the old DAT that helped some of our machines. There appears to be a 'safer' way to recover the svchost binary.
The e Policy Orchestrator is used to update "DAT" files throughout enterprises. We also had some laptop users get the DAT file from home or while coming into the office. We now have about 100 machines that are in a reboot loop. While it is a less convenient method, it is probably the best way. It is not like reported in thi blog, but the has been deleted and windows got in real problem.
It can not be used to undo this bad signature because affected system will lose network connectivity. Mc Afee's support web sites currently respond slowly and are down at times, likely due to the increased load caused by this issue. One fix is to delete the bad DAT file the client at "C:\Program Files\Common Files\Mc Afee\Engine". No reboot loop, no message, but about nothing was working. Application working with windows XP SP3 not running. We are currently sitting on version 5960 and use Sonicwall to push our updates out to the workstations. And so, when I discovered that one of our systems was missing its network connections, I attempted to repair the operating system using a Windows setup disk.