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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-01-20T17:20:56+00:00

    MSE is installed already.  At least with that fixit, I can't repro the problem :-(  Anyone else reading this, please email me at susan-at-msmvps.com (change the -at- to @) so we can see what is triggering this please?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-20T17:14:48+00:00

    All I have is what nbMenagerie posted there in the other thread.  Looking back there was something similar posted earlier about a download that was never identified.  A lot of these reports could be misidentifying damage done earlier by troubleshooting or by the known faulty Fix its.  I don't know.

    I haven't tested these reports either.  Somebody else reported MSE was a culprit. The only machines I have online and working I am not at liberty to deliberately try to cause to malfunction testing these bug reports.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-01-20T17:12:41+00:00

    Just tried to repro and and it didn't repro.  Asked him if he'd be willing to open a case.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-01-20T17:02:22+00:00

    I can't.  Is there any other info you can give me to help me repro this?  If I can't repro it, Microsoft won't be able to either.

    Was this answer helpful?

    0 comments