Updating registry keys sp3

Rated 3.93/5 based on 689 customer reviews

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."People need to exercise caution before [updating to] XP SP3," said Cole.“This is related to XP SP3,” he said, “and XP SP3 has already had other issues specific to some OEMs and some processors.” Cole was referring to the “endless reboot” snafu that users began reporting after applying the service pack upgrade.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." Cole was referring to the "endless reboot" snafu that users began reporting after applying the service pack upgrade.

Microsoft limited its response to boilerplate language that it has used before in statements about XP SP3.

"Customers who experience a problem with Windows XP SP3 installation should contact Microsoft Customer Support Services, which can provide free assistance and troubleshooting for these issues," a company spokeswoman said in an e-mail Monday afternoon.

"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? "While we're seeing that this issue affect Norton users, we don't believe we're the root cause," said Sondra Magness, a Symantec spokeswoman, in an e-mail.

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? "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.

Leave a Reply