11/14/2023 0 Comments What are mcafee superdat![]() ![]() There's also note in the VirusScan 8.7 Patch 3 update's Readme file that says the same thing. And a McAfee support document urges users to set the feature to off after updating VirusScan 8.7 to Patch 1. One user told Robert McMillan of the IDG News Service that his installation was on by default. The setting Price referred to, "Scan Processes on enable," is off by default in most installations of VirusScan 8.7.īut not all. "I've not seen any reports from customers who had left this setting disabled," said Samantha Price, a manager of McAfee's global threat response team, in a message on the firm's support forum for VirusScan Enterprise. If you're running an older version, including the earlier Enterprise 8.5, you were in the clear.Ī McAfee manager shed some additional light on why some Windows XP SP3 systems were clobbered, while others kept on running. Only machines running VirusScan 8.7 were affected, users reported and McAfee confirmed. Why were only some crippled? Good question. There are, however, scattered reports on the McAfee support forum of Vista machines also going down. McAfee also said even older editions - such as Windows 98 - were unaffected. Other version of Windows XP, including SP1 and SP2, were not nailed by the update, nor were systems running Windows 2000, Vista, Windows 7, Windows Server 2003 and Windows Server 2008. What machines were affected? Only PCs running Windows XP Service Pack 3 (SP3), says McAfee. Most also lost all network capability, and some were unable to "see" USB drives, a major problem since recovery may require the reinstallation of svchost.exe, something that could be done more easily by walking a flash drive from one crippled computer to the next. When users applied the update, then rebooted, they were toast: The machines crashed and rebooted repeatedly. Why did the PCs crash and burn after getting the bad update? Without svchost.exe - a generic host process for services that run from other Windows DLLs (dynamic link libraries) - a Windows PC won't boot properly. Think of the snafu as if the police pinned a crime on a suspect based on flawed DNA testing, only to find out they'd got the wrong guy. In some cases, the update actually deleted the file. Instead, it went rogue, wrongly fingered the critical "svchost.exe" file in Windows XP Service Pack 3 (SP3) as malware, and then quarantined it by removing it from its normal location. Wednesday's update - McAfee pushes daily updates to its corporate customers - was meant to detect and destroy a relatively minor threat, the "W32/wecorl.a" virus. For more information, Network Associates customer support can be reached at 001 (972) 308-9960.What happened? Short answer: McAfee screwed up. McAfee will post a standalone fix for customers with damaged NTFS master boot records. McAfee technicians have also had some success restoring the MBR by invoking the repair process on the Microsoft NT installation CD. Reinstalling the operating system will restore the MBR. McAfee's Alan Johansen emphasizes that even if the MBR is damaged, programs and data on the hard disk should be safe. Our tests also verified that the problem doesn't affect Windows 2000. We also installed VirusScan 4.0.3a and the SuperDat 4120/4111 upgrade and again encountered no hiccups with the OS or the MBR. We installed NetShield version 4.0.2 on an NTFS-formatted Windows NT Workstation 4.0 and upgraded to 4120/4111 without any problems. ![]() ![]() ![]() Testers at KeyLabs were able to verify the latest fixes. Network Associates also recommends that all VirusScan/NetShield users upgrade to the latest version, the 4.5 program executable, as soon as possible. The 4120/4111 SuperDAT utility currently posted on the McAfee Web site resolves the file-locking issue with VirusScan/NetShield 4.0.2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |