bill - 8:33 am on May 25, 2012 (gmt 0)
Sorry for the confusion. I was parroting advice I'd heard elsewhere about this issue as I don't have any active XP installs to play with.
MS has really screwed this one up. I'm seeing reports all over about it, but no official word from MS.
The current advice if you're running Windows XP, is to take a pass on KB 2604092 [support.microsoft.com] (MS12-035) [technet.microsoft.com]
However, you now say that you have this installed and the problem has stopped?