McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur.

According to the security provider, the file is detected during a scan of the main memory as a suspected pest. This will be the technology used, to prevent the so-called false positives actually bypassed. For the same reason the error was not discovered by quality assurance.

According to SANS Internet Storm Center McAfee update is causing the reboots and repeated cuts with the deletion of svchost.exe all network connections. In companies, it spread rapidly over ePolicyOrchestrator McAfee, distributed signature updates across networks.

Engadget quoted a statement from McAfee, according to which the problem occurs primarily at business customers and has little impact on consumers. According to an administrator of a U.S. university are unusable in its approximately 1,200 network PCs. Kentucky.com According to the police and school authorities in the U.S. state affected. Learned from an anonymous source as ZDNet, Intel are also tens of thousands of computer failed.

Meanwhile, McAfee has updated the signatures of its antivirus software to version 5959 DAT. Affected customers should update to one of the deleted file “svchost.exe” manually restore from quarantine. Alternatively, it is in the folders “C: \ Windows \ ServicePackFiles \ i386″ or “C: \ Windows \ System32 \ dllcache”. A detailed guide can be found in a Knowledge Base article, the security provider.

A faulty signature update from McAfee classifies the system file “svchost.exe” running Windows XP SP3 as a pest. Affected systems are then useless (Image: McAfee).

McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur. According to the security [...]

McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur. According to the security [...]

McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur. According to the security [...]

McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur. According to the security [...]

McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur. According to the security [...]

McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur. According to the security [...]

McAfee has warned of problems with a signature update released yesterday (version 5958 DAT). It classifies the Windows system file “svchost.exe” a mistake as the pest “W32/Wecorl.a”. This affects only users of Windows XP SP3. In Windows 2000, 2003, XP SP1, XP SP2, Vista and 7, the problem does not occur. According to the security [...]