BITS Error 1290: 0x50a following updates

I remember tracking issues with that patch.  I remember that folks having issues after that update, had servicing stack corruption problems.  The BITS issue could be just a symptom, not the effect of the patch.

BITS would be sensitive to servicing stack corruption.

http://www.ehow.com/how_7279980_microsoft-won_t-install-windows-xp.html

"It is also possible that the Component-Based Servicing (CBS) manifest is corrupt

Bottom line I need someone willing to open a case to prove cause and effect.  I have a test freshly built XP and I can't recreate the issue :-(

See the last post in this thread linked below, post dated December 16 by user name 8OY

He is reporting having identified KB956572 as an update which corrupts BITS in a similar way of changing the name of BITS as is the result of the Fix it tool that Doug reported.  It had been suspected that some of the BITS corruption being reported might have for a cause a particular update and this may be it.  The user reported trying the updates in small batches to narrow down which update was the issue and then narrowed it down to 1 which is  KB956572

Maybe somebody could check this, could be the same coder made the Fix it that Doug identified.

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/the-new-windows-update-site-for-xp-is-broken-can/9581a663-6289-40d5-a52d-13be6710640f

Evidently the update does change the Remote Procedure Call  which is involved with BITS and what else may be affected if this update is a potential issue is unknown,

Here is some more information from a user reporting that installing the update triggered a Zone Alarm warning

https://groups.google.com/forum/#!topic/microsoft.public.windowsupdate/BvkgqKJe5bg

Given the bureacracy of Microsoft until a human being tells me they know it was broken, they may not know it was broken or that people were impacted.  The files in the fixit are dated 12/3/2013 which indicates a more current build of the file and the article is posted 12/9/2013.  But given that Microsoft never documents versioning, it's hard to know what's what.

Very thoughtless of Microsoft not to make a prior version Fix it "unfixer" but hey, they can be trusted to fix you right up with the same tools linked from the very place where errors are being reported.  It is like once in a hole they just keep digging.  Full disclosure is what is missing there.

No problem with letting this whole mess sit and stew for awhile.  I need some down time for the holiday myself.  This windows update fiasco has been a business that has been simmering to a boil over the past two months, and I have other fish to fry setting up a Windows 7 machine that is a Christmas gift for the wife.  So I am taking a needed break. 

Have a Merry Christmas