News

Symantec App Suspect in XP SP3 Registry Problem

Symantec officials described a workaround to a problem that has affected some users upgrading to Windows XP Service Pack 3 who also use Symantec's security solutions. Users can avoid a registry corruption problem by disabling a specific Symantec application before installing XP SP3, Symantec officials said this week.

On Wednesday, the security software company backtracked from its initial statements that placed the blame on Microsoft for a glitch in XP SP3. Symantec's reassessment came as the company discovered that its SymProtect Tamper Protection, associated with the company's Norton Antivirus products, could be the culprit.

In a post on a Symantec support forum, a Symantec official indicated that those using the SymProtect program would be better safe than sorry by turning the function off during installation of XP's latest service pack.

"For those who have already applied the upgrade and are running into problems, we're working on a stand-alone tool that would delete the extraneous registry keys," wrote Symantec's Senior Manager Reese Anschultz, in the blog posting.

Users that had installed XP SP3 reported seeing garbled and nonsensical system entries clogging up the Windows registry. The registry stores settings and options for Windows, including software settings for all of the hardware in a given PC.

SymProtect users who haven't installed XP SP3 can try Symantec's workaround. SymProtect is associated with Norton Internet Security 2008 and Norton AntiVirus 2008 products.

The registry corruption problem was publicized about two weeks ago after XP SP3's release on Windows Update. Scores of users complained to Microsoft and third-party vendors that their network cards and previously set connections had inexplicably disappeared from Windows after installing XP SP3.

Symantec researchers initially had blamed Microsoft's backend code. They pointed to a file named fixccs.exe in the XP SP3 upgrade as the reason for Windows Device Manager malfunctions. Microsoft, in turn, issued denials on May 20.

About the Author

Jabulani Leffall is an award-winning journalist whose work has appeared in the Financial Times of London, Investor's Business Daily, The Economist and CFO Magazine, among others.

comments powered by Disqus

Featured

  • Windows Community Toolkit v8.2 Adds Native AOT Support

    Microsoft shipped Windows Community Toolkit v8.2, an incremental update to the open-source collection of helper functions and other resources designed to simplify the development of Windows applications. The main new feature is support for native ahead-of-time (AOT) compilation.

  • New 'Visual Studio Hub' 1-Stop-Shop for GitHub Copilot Resources, More

    Unsurprisingly, GitHub Copilot resources are front-and-center in Microsoft's new Visual Studio Hub, a one-stop-shop for all things concerning your favorite IDE.

  • Mastering Blazor Authentication and Authorization

    At the Visual Studio Live! @ Microsoft HQ developer conference set for August, Rockford Lhotka will explain the ins and outs of authentication across Blazor Server, WebAssembly, and .NET MAUI Hybrid apps, and show how to use identity and claims to customize application behavior through fine-grained authorization.

  • Linear Support Vector Regression from Scratch Using C# with Evolutionary Training

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the linear support vector regression (linear SVR) technique, where the goal is to predict a single numeric value. A linear SVR model uses an unusual error/loss function and cannot be trained using standard simple techniques, and so evolutionary optimization training is used.

  • Low-Code Report Says AI Will Enhance, Not Replace DIY Dev Tools

    Along with replacing software developers and possibly killing humanity, advanced AI is seen by many as a death knell for the do-it-yourself, low-code/no-code tooling industry, but a new report belies that notion.

Subscribe on YouTube