- #Registry repair windows xp sp3 update
- #Registry repair windows xp sp3 software
- #Registry repair windows xp sp3 Pc
"People need to exercise caution before XP SP3," said Cole.
#Registry repair windows xp sp3 update
Last week, Hewlett-Packard Co., whose AMD-powered machines were cited by most users as the only ones affected, confirmed the rebooting glitch, and Microsoft announced it would add a filter to Windows Update to prevent AMD-based PCs from obtaining XP SP3 via the update service's listings. "This is related to XP SP3," he said, "and XP SP3 has already had other issues specific to some OEMs and some processors."Ĭole was referring to the "endless reboot" snafu that users began reporting after applying the service pack upgrade. Cole also said that Symantec had done "extensive testing" of its products with Windows XP SP3, but this issue hadn't surfaced.Īnd he essentially blamed Microsoft for causing the problem. "The support lines are not ringing off the hook," he said.
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.
#Registry repair windows xp sp3 software
"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." "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. 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. The other two have the same mess as identified by all in this thread." "As you guessed, the one without NIS2008 upgraded like a charm. "I upgraded three well-maintained laptop machines, one with NIS2008 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. "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 see parent keys that all seem to be Norton/Symantec product keys," said someone identified as "gfrost."
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.
#Registry repair windows xp sp3 Pc
Those entries, said MRFREEEZE61, began with the characters "$%&" once they were removed, the PC returned to normal. 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. Numerous other users corroborated MRFREEZE61's account on the same support thread. "In an attempt to troubleshoot, I tried to bring up the Device Manager, and to my surprise it is now empty."
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. "The Network Connections screen now does not show any of the NIC cards.
0 kommentar(er)
