Another Problem for Service Pack 3 - The Fun Just Doesn’t Stop!

Perusing ComputerWorld this afternoon, I immediately saw the headline stating that Windows XP Service Package 3 has now been accused of corrupting the registry on computers where it is installed. And there seems to be corroborating evidence.

Microsoft just keeps it coming lately…that Monkeyboy must be dancing his chinos off right about now!

Better than just one company being to blame, it also seems that some are blaming Symantec for some of the problem, coming from usage of Norton Internet Security, and Norton 360.

from the article

Symantec Corp. today denied that its consumer security software, including Norton Internet Security and Norton 360, is to blame for wreaking havoc on some users’ PCs after they upgraded to Windows XP Service Pack 3.

Microsoft Corp. declined to answer questions about the problem, which has emptied Windows’ Device Manager and deleted network connections, preventing some users from connecting to the Internet or to wireless networks.

According to reports posted the day after Microsoft launched Windows XP SP3 on Windows Update, some users found that their network cards and previously-crafted connections had mysteriously vanished from Windows after updating to the service pack.

"The Network Connections screen now does not show any of the NIC cards. I have three adapters that used to show up," said someone using "MRFREEZE61" as an alias on Microsoft’s XP SP3 support forum on May 7. "In an attempt to troubleshoot, I tried to bring up the Device Manager, and to my surprise it is now empty."

Oops! 

Numerous other users corroborated MRFREEZE61’s account on the same support thread.

Ooh, that is not good, now it can’t simply be in the imagination of one user.

MRFREEZE61 reported that he had found large numbers of corrupted entries in Windows Registry, a directory that stores settings and other critical information for Microsoft’s operating system. Those entries, said MRFREEEZE61, began with the characters "$%&"; once they were removed, the PC returned to normal.

Others chimed in to claim that the errant keys were located in sections of the registry devoted to settings for Symantec products, and they pinned blame on the security company’s consumer-grade software installed on their PCs. "I see parent keys that all seem to be Norton/Symantec product keys," said someone identified as "gfrost."

"This appears to be a Symantec-related problem according to the keys showing up," said another user, "datarimlens." "Is anyone from Symantec on this yet? Since SP3 has been distributed to at least one of my machines, am I to believe that this problem did not show up in testing? Really? For something as widely tested as SP3? Really? I mean seriously?"

"I upgraded three well-maintained laptop machines, one with NIS2008 [Norton Internet Security 2008] installed and running during the upgrade, one with NIS2008 installed but shut down during installation and one without NIS2008 installed," said "bighowie," yet another user posting to the forum. "As you guessed, the one without NIS2008 upgraded like a charm. No problems. The other two have the same mess as identified by all in this thread."

Today, Symantec said its initial investigation had uncovered no cause and effect between its software and the corrupted registry keys, which in some cases numbered in the thousands.

"While we’re seeing that this issue can affect Norton users, we don’t believe we’re the root cause," said Sondra Magness, a Symantec spokeswoman, in an e-mail. "In further searches on this issue, we found a number of users experiencing the problem but who do not have Norton software and/or are experiencing the issue on XP SP2."

In a follow-up telephone conversation, Dave Cole, Symantec’s senior director for product management of its consumer offerings, acknowledged that users running Norton titles were experiencing problems, but he said the numbers are small. "The support lines are not ringing off the hook," he said. Cole also said that Symantec had done "extensive testing" of its products with Windows XP SP3, but this issue hadn’t surfaced.

And he essentially blamed Microsoft for causing the problem. "This is related to XP SP3," he said, "and XP SP3 has already had other issues specific to some OEMs and some processors."

While ‘good buddies’ Symantec and Microsoft hash out who really is causing the problems, I certainly believe foregoing the installation of Windows XP Service Pack 3 would be wise.

I am not a conspiracy nut, but there is a thread I saw on one site stating that this is a move by Microsoft for Vista growth. The line goes like this - Well, Service Pack 3 already hosed my system, so I might as well try out Vista, how could it be any worse?

Famous last words.

[tags] Windows XP Service Pack 3, SP3, Microsoft, Vista, Symantec, registry errors [/tags]