KB954550-v5

we have windows 2003 server with sp1 and have a patch listed in add/remove
prgoram windows xp KB954550-v5. i am not sure what this patch is related to
and how this got installed. i cant find any article in MS site. Can anbody
let me know about this

Hi,

Based on my research, this is part of XPSEPSC component. .NET 3.0 included
an older version of the XPSEPSC components and is repackaged by .NET 3.5

Here's a list of the components in .NET framework 3.5
http://msdn.microsoft.com/en-us/library/cc160716.aspx

XPSEPSC-x86-en-US.exe and XPSEPSC-amd64-en-US.exe are distributed using the
kb954550 package for .NET 3.5 SP1.

Hope this helps.

Hi,

I am writing to see if you have any update on this issue. If you need
further assistance, please feel free to post here.

Have a good day.
Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security

We too run Windows Server 2003 with sp2 and one of our servers has an update named: "Hotfix for Windows XP (KB954550-v5)" in the Add or Remove Programs. It also states that "This update cannot be removed". We noticed abnormal spiking of our CPU by the w3wp.exe (IIS) and have reason to believe it may be due to this KB954550-v5. The reason we suspect it is because only the machine with the KB954550-v5 hotfix spikes its CPU at 50% to 100% when browsing to any aspx/asp.net page in our site. The symptoms correspond with the date this hotfix was installed. We do not know how it got there, although it is reasonable that it was installed with .Net 3.0 or 3.5. However, uninstalling .Net 3/3.5 does NOT remove this hotfix. It is obviously an unusual hotfix since it states it is for Windows XP while on a Windows Server 2003 machine.

We need to know a) how to uninstall it or b) at least how to install it on another machine so we can know if it is causing our servers to freeze up (with using up all available CPU).

OK, here's an update. Even though we still don't know what KB954550-v5 does, it does not seem to be the cause of our CPU spiking. The way I resolved our problem was to uninstall ALL the .Net frameworks that can be uninstalled (I uninstalled 3.5, then 3.0, then 2.0 sp1, then 1.1 compact and then 1.0 compact in that order). .Net 1.1 and 1.0 cannot be uninstalled (easily) according to information out there on the web, so I left them. Next, I installed .Net 3.5 from scratch, and that is it! We use .Net 2.0 and the .Net 3.5 installer installs previous versions also. Our CPU problem went away.