Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The combination of Windows XP SP2 and SQL Server Express 2005 SP3 can causes the machine to blue screen during the installation of SQL Server Express. One of the Windows Updates that you can apply to Windows XP SP2 fixes the problem. Unfortunately, if you install Windows XP SP2 and run Windows Update, it will tell you that it needs to install about 118 updates. I would like to know which of the 118 updates fixes the problem. I know that the fix involves updating SXS.DLL to version 5.1.2600.3019.

Other than installing each update one at a time and checking the version of SXS.DLL after each update, is there an easier way of determining which update fixes the problem?

share|improve this question
up vote 1 down vote accepted

The specific version of sxs.dll that you refer is from Microsoft Security Bulletin MS06-075.

How do you know that the bsod is fixed in that specific version?

Update to comment: I think that its not so simple. As explained in kb824994 there are two branches in windows fix/update land. except from the usual one. There is the quick fix engineering one. Maybe the fix you need is on that branch. So installing only the security bulleting wont install the fix you need. If you really want to update sxs.dll just look for the latest hot fix including it you can find. I have found kb943232.

share|improve this answer
Just through testing. It's actually fixed by an earlier downloadable 'hot fix' but it appears that it is also fixed by a later 'Windows Update'. – jmatthias Sep 28 '09 at 20:08
The Windows Update referenced in the article Microsoft Security Bulletin MS06-075 does fix the SQL Server 2005 SP3 blue screen issue. The Windows Update is number is 926255 and is only applicable to XP SP2 (XP SP3 updates SXS.DLL). – jmatthias Sep 28 '09 at 21:38

Yes: put it into Google. Every Microsoft KB article about a hotfix shows the version numbers of replaced files, so it's quite easy to found the article referencing the update you're looking for.

About those 118 updates: why don't you want to install them? And why not install SP3? Updates are released for a reason (fix bugs, close security holes, etc.), you shouldn't run a plain Windows XP SP2 system in the year 2009.

Unless you have a really good reason for doing that, of course (like incompatible software); but if you are one of those people who just don't want to "lose time" installing updates, I strongly advise you against this; it's a really good way to look for troubles.

share|improve this answer
Rather than tell the customer they have to install ALL the updates or Windows XP SP3, we would like to tell them which specific update that they need to install. It's about minimal machine impact. – jmatthias Sep 28 '09 at 20:07
Agreed on the minimal impact issue, but I'm still heavily convinced that running an obsolete and unpatched O.S. release is just asking for much more impact in the long term. – Massimo Sep 28 '09 at 21:13

After posting this question I decided that I could probably determine which updates, update this file (SXS.DLL) by grep'ing the .log files in the C:\Windows folder after installing all of the updates. These log files list which DLLs are being updated along with version information.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.