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 No 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 No comments

120 additional answers

Sort by: Oldest
  1. Anonymous
    2014-01-20T16:27:09+00:00

    There evidently exists more than one means by which the BITS can be made dysfuctional and it has been a widely reported issue for many years that the issue occurs but not having specific causes identified until recently a cause being identified with the faulty Fix it tools which is a matter that Microsoft owns completely.   Another faulty fix it has been reported.  I am not sure about the page from which it is linked or which Fix it number this is that is being reported. This is some really poor performance by Microsoft now actually hosting and sourcing what amounts to malware disguised as a troubleshooting utility.  Maybe next time a malware removal or repair tool is contemplated, Microsoft should do some self examination and patch some of its own patches.

    http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/background-intelligent-transfer-service/62418f22-4803-41a2-9e41-5f4616366d47?page=3&msgId=3aabcf41-82cc-4479-89bd-ed856eab2237

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-01-20T16:46:21+00:00

    Which specific fixits are doing this please?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-01-20T16:47:12+00:00

    Is the one referred to on the post the only one currently doing it?

    Let me see if I can repro the issue.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-01-20T16:56:08+00:00

    Susan, Which Fix it that is being reported as still breaking BITS I don't know.  It is a direct link for the exe that is provided and if it is the same Fix it as Doug identified 2 iterations and is mirrored somewhere that MS missed or if it is an entirely different exe file I don't know.  But it has been suspected and reported there are other things out there that have been in the past and still are causing BITS to become dysfunctional.  And in the older KB articles about troubleshooting BITS issues there were no causes of the issue identified.  So it may be unknown exactly what various causes of the issue exist in total.  But it is identified recently that Fix it tools can do the deed.  So when somebody reports a Fix it is a culprit then that should be checked to confirm.

    linked by nbMenagerie

    http://diagnostics.support.microsoft.com/diagprov/provision/MicrosoftFixit.WinSecurity.FISC.19631335317613077.4.2.Run.exe?_tenant=mats&diagid=WinSecurity&entrypointid=FISC&logsessionid=19631335317613077&eventseqno=4&buttonclickno=2&_ext=.exe

    Was this answer helpful?

    0 comments No comments