Update: McAfee just sent us a statement -- they've pulled the update from their corporate download servers, and consumers shouldn't be affected.
Ouch -- that might be the understatement of the year. We've definitely hearing this affects SP2 as well, we'll keep looking for more.McAfee is aware that a number of customers have incurred a false positive error due to incorrect malware alerts on Wednesday, April 21. The problem occurs with the 5958 virus definition file (DAT) that was released on April 21 at 2.00 PM GMT+1 (6am Pacific Time).
Our initial investigation indicates that the error can result in moderate to significant performance issues on systems running Windows XP Service Pack 3.
The faulty update has been removed from McAfee download servers for corporate users, preventing any further impact on those customers. We are not aware of significant impact on consumer customers and believe we have effectively limited such occurrence.
McAfee teams are working with the highest priority to support impacted customers and plan to provide an update virus definition file shortly. McAfee apologizes for any inconvenience to our customers
Update 2: The anecdotal numbers keep rolling in, and they're not small -- 30,000 machines are knocked out here, 60,000 there. Given that the only fixes right now involve techs spending time with each affected machine individually, things could get seriously messy. We'll keep you updated if you keep us updated, okay?
Update 3: Here's an official McAfee fix, although like we said, it requires tech to hit each machine in person. We'll see what the story is for bigger institutions with tens of thousands of seats.
Update 4: We're told the official fix only helps those who haven't been hit with the bug yet, so there's obviously still issues to be sorted out. [Thanks, Tyler.]
[Thanks to everyone who sent this in]
Microsoft Windows XP