"We are not aware of significant impact on consumer customers and believe we have significantly limited such occurrence." "The faulty update has been removed from McAfee download servers for corporate users, preventing any further impact on those customers," Evers said. Instead, users can reach the instructions and EXTRA.DAT file from elsewhere on McAfee's site. After applying the EXTRA.DAT, restore the affected files from Quarantine." Unfortunately, those instructions and the suppression EXTRA.DAT update file are not currently available, again because McAfee's support site has gone dark. "For systems that have already encountered this issue, start the computer in Safe Mode and apply the EXTRA.DAT. "Apply the EXTRA.DAT to all potentially affected systems as soon as possible," the company recommended. McAfee reacted by warning users not to download today's update if they haven't already, and by posting recovery instructions and a signature update to suppress the defective one seeded to users earlier. "Our initial investigation indicates that the error can result in moderate to significant performance issues on systems running Windows XP Service Pack 3," acknowledged Evers.Īffected PCs have displayed a shutdown error or blue error screen, then gone into an endless cycle of rebooting, users claimed. ![]() We apologize for any inconvenience this may cause."īoth users and McAfee said that the flawed update had crippled Windows XP Service Pack 3 (SP3) machines, but not PCs running Vista or Windows 7. ET, McAfee's support forum was offline, with a message reading "The McAfee Community is experiencing unusually large traffic which may cause slow page loads. "Great work McAfee! GRRRRRRRRRRR."Īs of 3:30 p.m. "This is goddamn ridiculous," added Gerard, who identified himself as a senior security administrator with Wawanesa Mutual Insurance Company of Winnipeg, Manitoba, in Canada. "HOW THE F*** do they put a DAT out that kills a *VITAL* system process?" asked Jeff Gerard on one thread. Much of this info is discussed within the ReadMe.txt file.According to users on McAfee's support forum, today's update flagged Windows' "svchost.exe" file, a generic host process for services that run from other DLLs (dynamic link libraries). Additionally, there is a ReadMe.txt associated with the. Most likely you don't need the scan engine re-installed, so XXXXxDat.exe is probably the easiest to use.Įach tab for Dat and SuperDAT lists the most recent available file. No particular reason to use SDatxxxxx.exe over the smaller XXXXxDat.exe file if the Scan Engine is installed. Sdatxxxx.exe is about 5.5 MB larger than XXXXxDat.exe because sdatxxxx.exe also contains the Scan Engine (v5400). Well, I am assuming you already have a base install of VSE.īoth files contain the Signature (DAT) files. What would be the best prefered DAT file to download? The SuperDAT (sdatXXXX) or the DAT (XXXXxdat) ? If I am offline, then what do I need to download? I would suggest reading the Readme.txt from McAfee's site for each download where many of these details are documented. The SuperDAT is useful if ever you encounter a situation where the signature files or the runtime has become corrupted, or the engine files have updated improperly, leaving the system unstable or unprotected. (That's if you initial VSE image is using an old version of the Scan Engine, which hopefully is not true.) Similarly, you could download the Scan Engine once, and periodically download the smaller xDat signature file, saving time and money (on both sides). ![]() So, after an image restore, you could update the signatures and engine in one download. ![]() The SuperDAT (sdatnnnn.exe) also contains the Scan Engine in addition to the Signature files, whereas the xDat (nnnnXDAT.exe) does not contain the Scan Engine.Ĭurrent SuperDAT files contain the 5400.exe ( ) scan engine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |