BITS Error 1290: 0x50a following updates

Anonymous

Hi,

I'm looking for some assistance.

I'm running Microsoft XP Pro and have completed the critical updates, however now my BITS service will not start at all.

It is producing the error [Error 1290: 0x50a].

I've ran the Microsoft Updates fix utility and it is still unable to start it.

Any Help is greatly appreciated.

James

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Hello.

Regarding this issue, it looks as follows:

a recent update for WIndows XP SP 3 seems to have accidentally added 2 flags into the BITS Service Registry entry which are, simply said, invalid there in that place on XP Clients.

The first key is "DelayedAutoStart". According to MS this is valid from Vista and newer only, so -> remove that from a WIndows XP machine since it is not functioning.

The second key (and mostly our cause of 1290 0x50a error for BITS where it appears)

is the flag "SIDVersionType".

On WIndows XP this is invalid for the BITS service also. -> Remove it.

After that, Reboot Windows XP.

Regards

Bernd

0 comments

120 additional answers

Anonymous

2013-12-13T11:20:38+00:00

Thanks Keith.

Yesterday I went through a complex procedure suggested elsewhere to reinstate BITS involving picking up a .reg file and merging it into the Registry etc (I have XP Pro with SP3).

Well, it did put BITS back in the services but when I ran MS FixIt, it still left me with no access to updates. I suspect the MS registration of the machine/software is not working because at the end of FixIt, when one can send the result to MS for specific advice after copying the code letters, this would not get through.

I shall try your suggestions when I have time, but as you say MS should really make an effort to solve this damn problem on which I have already spent a couple of fruitless days.
Was this answer helpful?

0 comments No comments
Anonymous

2013-12-13T12:01:11+00:00

Have you followed the steps that Xircal has detailed?

See this thread and my answer post to the OP which has the links you should see

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/win-xp/90153b86-8f5b-4a59-a43b-489e756ae0f6
Was this answer helpful?

0 comments No comments
Anonymous

2013-12-13T14:51:37+00:00

BITS is a key item needed to ensure updates get applied. Malware loves to ensure that updates do not get installed. If there was a rogue Microsoft server that was attacking XPs and causing BITS to fail I'd be seeing it on lots more XPs than we are seeing it on.

BITS should not be stopped, nor unregistered. Both smell like interaction with malware, not as a result of Microsoft updates causing issues.

If you've left the message in forums, I doubt this message gets to the right eyeballs. Lately some of the WU updates that you and I would consider reasonable can't (for whatever reason that they don't state) be posted. Case in point a download of the latest WU client engine update. It's a PAIN IN THE REAR to get a newly installed XP hooked back into WU.

My theory is (sorry yes, this is rumor that I don't like doing) is that if they expose the WU client engine attackers can reverse engineer it and find weaknesses and build more Stuxnet attacks.

Let me ask around on the BITS installer and see what the deal is on updated downloads.
Was this answer helpful?

0 comments No comments
Anonymous

2013-12-13T15:23:23+00:00

I left the BITS HOTFIX request message verbatim as copied above including the linked pages in the suggestion space provided on each of the linked KB pages so that Microsoft can't miss the message or the nexus.

The issue is NOT malware because it is occurring on fresh installs
Was this answer helpful?

0 comments No comments