BITS Error 1290: 0x50a following updates

Anonymous
2013-10-03T10:56:25+00:00

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

Windows for home | Previous Windows versions | Apps

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
2013-11-02T13:35:05+00:00

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

Was this answer helpful?

2 people found this answer helpful.
0 comments

120 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-11-07T01:58:14+00:00

    Better yet, get a Microsoft Support tech to reinstall SP3 for you.

    1 800 Microsoft

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-11-07T09:31:43+00:00

    Thanks for the guidance Bernd.  I have deleted delayed auto start but cannot find SIDVersionType.  I do have ServiceSidType.  I have not deleted this entry and  will try a reboot,

    DH.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-11-14T10:23:17+00:00

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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-11-24T06:25:32+00:00

    Thanks Bernd, that solved the problem for me too.

    However, I do not like deleting things in case they have to be put back so I renamed the parameters by putting "XX" in front of them. I rebooted and Windows Update works again!!

    I will delete the 2 invalid parameters later.

    Was this answer helpful?

    0 comments