BITS Error 1290: 0x50a following updates

I dont know how to remove that. Where do I go first ? Slavica

The only "update" that has been proved to make those registry changes was a faulty Microsoft Fix-It for Windows Update problems. See my various posts on page 9 of this thread. 

Removing the extra registry "keys" (values) is critical - but it is very likely other registry values have been altered - so a more complete fix is recommended. If you are not familiar with using the registry editor it is safer to automate the process by using a clean copy of the BITS registry which includes the extra commands to remove these invalid registry "keys" (actually they are registry values).

The first post on this page by Ron W Hardy used my fix for this problem from page 9 of this thread - and fixed his problem.

Click on the link - "In reply to DougCuk_42 post on December 25" at the top of that post.  

You will see my analysis of the problem and details of my quick fix to return the BITS registry to standard settings - which including eliminating the extra registry entries. 

You may already have fixed some of the BITS corruption - so you may not see the "odd" name in the services list - but this is not a problem. You can run the fix anyway - as it states it can do no harm if you are running XP as all it does is restore the standard BITS registry - remember to reboot after applying the fix - or it will not be active.

Thank you Doug, for your concise description of the issue, and your registry fix. Now I can clean up the hair I tore out following MS topics.

Indeed, I had both the svchost lag and the broken BITS bugs... I had last week managed to find a solution to my flavor of the svchost problem, which cured the lock-up and fixed BITS at the same time, allowing me to finally update Windows. *SOMEHOW* in the last round of updates (since Dec 27) the problem with BITS being renamed as you mention surfaced, breaking Update once again (it's worthy of mention that I had NOT used a Fix-It since repairing the previous break!) which finally led me to discover this thread. It disturbs me no end that there appears not to be just a single vector for this dysfunction, and that it persists as it does. I would hate to subscribe to the notion I read elsewhere that MS is "accidentally on-purpose" un-fixing Update functionality in a bid to wean users of mature, stable XP systems off to the Next Big Thing. However, I must also observe that as the support phase of XP comes to eclipse, the quality of updates has gone downhill.

Anyway, thanks again, you helped extend the life of a worthy machine.

Thank you very much for your post regarding the BITS error.  I used your solution and it worked great!

Got the same problem. After deleting the "DelayedAutoStart" and "ServiceSidType" + reboot it began to work. Thanks!

Ah - that worked for me too.  Thanks Bernd for the initial find and Soren_S for the spelling :-)