SP2 clashes with more than 40 programs

SP2 clashes with more than 40 programs

Summary: The update for Windows XP makes a long list of programs appear to stop working, including Microsoft's own SQL and Visual Studio .Net

Microsoft has published the details of more than 40 programs that have conflicts with the newly released Windows XP SP2.

The list includes several widely used Microsoft products including SQL, Visual Studio .Net, and SMS 2003 Server.

The list can be found under the heading "Some programs that seem to stop working when you install Windows XP Service Pack 2" on Microsoft's website. XP SP2 has also created problems with Symantec's Antivirus Corporate Edition 8.0, MacAfee's NetShield 4.5 and CA's eTrust 7.0.

Some games that run on XP also come to grief following the installation of the service pack, including Scrabble 3.0 and two versions of Unreal Tournament. Microsoft doesn't give hints on how to resolve the conflict with the games but points users in the direction of the original vendor, with instructions to "see the documentation".

Some Microsoft programs "appear" to stop working but can be coaxed back into life if you follow the instructions given for each individual program on the Microsoft website. The conflicts mainly stem from the SP2 tendency to shut certain ports or block 'unsolicited connections' - often a sign of malware, spyware or other unwanted visitors.

There is one notable exception, however. Microsoft's CRM product won't work with a SP2-equipped machine, full stop. Microsoft has already issued a fix for the incompatibility.

It's such incompatibilities that have prompted IBM to advise its staff to not install the service pack for fear it might conflict with business-critical applications.

A complete list of the programs that conflict with XP SP2 and how to resolve the problems can be found on Microsoft's website, here.

Topic: Operating Systems

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Basically this shouldn't considered a clash. Any personal firewall installed in a pc should lead to similar issue.
    Good thing is that microsoft did not enable the ports by defualt to its own products.
    Its a bit of thing common pc user must! know.
  • If you actually read the Microsoft article that you link to, you will see that it is not a bug or a "clash" but security based. You just have to open ports manually. No big deal. It seems that your article has unfairly targeted Microsoft.
  • I had to rollback my install of sp2 because a very important program I use would not work with it. MS should have realized creating new conflicts for previously working software as unacceptable and at least provided a switch that would allow the existing programs to run and better troubleshooting help info as well. I wasted a day after the upgrade trying to get my program to work with it, trying to find info and solutions to resolve my problem.
    Of a certainty, if there was another operating system that had a windows emulator for my existing programs, I now would be looking at swicthing to it very closely.
    Overall a bad move on the part of Microsoft.
  • non-story. Of course as Microsoft is turning on the firewall apps that use ports are going to need to be tweaked. Not a bug.
  • It is ignorance even to publish an article like this not mentioning writing it.

    If any reader knows a bit of what happening, they know it is not Microsoft's mistake or fault.

    When they came out with DOS (for IBM, if anybody forgot) they were not told, the OS is not safe, etc. etc.
    They built a new file system for DOS (FAT) that they developed throughout the Windows lifecycle up until NTFS.

    The OS of course became more and more complicated with security features built in as required (or requested) by the market. Yes, it wasn't secure design, but it wasn't what the customer wanted either.

    But in the meantime, they took over everybody's desktop. And with Linux coming around talented young programmers were compelled to prove Linux supremacy over Windows. There was more and more invested energy on viruses.

    So by today, the demand is security and the business requirement is security. And since this became a factor at the store, Microsoft answers the challenge.

    Now obviously with all that said, developers for Windows also did not care about security, not even mentioning to be comparible with Win.
    So Microsoft made sure their crappy software will run on Windows. The funny thing is, this must be true internally for Microsoft, having so many independent development teams.

    So now the OS is safe and the applications are not. Guess what happens? The OS will not allow unsafe applications to run.

    Windows just arrived where UNIX always been. Welcome home, bro'.
  • Lazlo http://www.codeweavers.com crossover office is a windows software emulator for linux...
  • For the anonymous US exec, MS didn't make DOS or the FAT file system that it used, they bought them. MS-DOS was originally named QDOS (Quick and Dirty Operating System), and when Microsoft bought QDOS it was renamed MS-DOS.

    And your sentence about Linux programmers wanting to show how good Linux is compared to Windows seems to imply that Linux programmers created viruses to do this.

    And as for Microsoft making the Windows unsafe so that unsafe programs can run on it; stop smoking whatever it is that you're smoking, as it's seriously affecting your ability to think. Microsoft made Windows insecure by continually integrating programs into the kernel. Go to the Windows update site with a fresh install of Windows XP and you'll find a whole heap of patches that relate to IE vulnerabilities giving people control over the whole computer. With Microsoft, security has always been an afterthought next to things like profit and killing off the competition.
  • After installation of SP2, auto-update on Norton System Works 2003 (incl NAV 2004), refused to install the subscription and virus signature updates.

    Also the 512mb broadband connection started to go slow, and several web pages refused to work, stating that they could not load cookies (even after making these allowances in the firewall settings per M/S instructions).

    After uninstalling SP2, everything worked as normal.

    SP2 is therefore NOT fully compatible with standard, day to day PC installations, and should be further tested in the field by realistic and practical users before being sent to unsuspecting domestic PC users, with an expectation that this fix is a panecea for all things nasty!