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
    2014-01-20T17:28:43+00:00

    There could be something specific about the users machine that triggers the undesirable Fix it action because not everybody got the same effect as the guaranteed result of running the Fix it which was known faulty if I recall correctly, there was a high probability of the registry corruption but not an absolute guarantee the registry corruption would occur.   The Fix it tool is apparently interactive and scans for various parameters, then decides what changes to make.  I am guessing if it finds a particular "tripwire" or trigger condition then it proceeds with some action that causes the registry corruption.   So it may not be definitive that on one computer the effect can't be reproduced, when the experience of next test on a different machine could be different.  Yeah I think you are on the right track digging deeper and trying to get nbMenagerie to elaborate on system configuration ect.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-20T21:42:30+00:00

    That Fix-it runs the scripts from the WinSecurity.diagcab - totally different from the Wu.diagcab of the faulty Fix-It I reported.  I unpacked the WinSecurity.diagcab file and did a file content search for any references to BITS - none of the scripts in WinSecurity modify or even read the BITS registry key. So I don't see how it could cause a corruption of that registry entry.

    I then ran the Fix-It just to check and it made no changes to the BITS registry on my system.

    Case of mistaken identity I think?

    P.S. Just did a file content search on the whole Fix-It library - that's 27 Diagcab files comprising 7.8MB of code - and only the WU.diagcab file contains scripts that access the BITS registry.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-01-24T14:44:12+00:00

    Hi Bernd,

    I have the same problem and hope that your answer could help me. but can you tell me where i can find the files to delete them?

    Many Thanks

    Colin

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-01-24T18:39:11+00:00

    Back on page 7 of this thread about the 5th  post on the page I link some other related threads which will show the location of the registry entries.  Dougs registry merge is sufficient to fix the issue, however unless you just want to do the fix manually through regedit.

    Was this answer helpful?

    0 comments