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-13T07:51:40+00:00

I don't work for Microsoft. I'm a crazed volunteer here that will beat up on Microsoft when it's needed to, but really do not like rumors posted. I am a moderator on the Patchmanagement.org listserve as well. I read this whole feed and I know what I see with my own eyeballs on my own Windows XPs that do not have these issues.

We aren't really sure exactly what is the culprit that is making BITS dysfuctional

Take a look at these links and see if anything looks familiar

http://support.microsoft.com/kb/883614

http://support.microsoft.com/kb/916251

I have left multiple instances of the following message as a suggestion for Microsoft

An updated BITS installer should be made available for the file version number of qmgr.dll 6.7.2600.5512 that is otherwise only available included as part of SP3. It can happen that the BITS needs to be reinstalled and there is no way to do this easily since the standalone installer for the file version number 6.7.2600.5512 has not been made available. This should be made available as a high priority HOTFIX.

The HOTFIX should be then linked on this page

http://support.microsoft.com/kb/923845/en-us

as an UPDATE and on the related pages as follows

http://support.microsoft.com/kb/883614/en-us

http://support.microsoft.com/kb/916251/en-us
Was this answer helpful?

0 comments No comments
Anonymous

2013-12-13T01:49:47+00:00

Again, someone want to help us all out by letting me open up a free case, email me at susan-at-msmvps.com (change the -at- to @)
Was this answer helpful?

0 comments No comments
Anonymous

2013-12-13T01:48:40+00:00

I don't work for Microsoft. I'm a crazed volunteer here that will beat up on Microsoft when it's needed to, but really do not like rumors posted. I am a moderator on the Patchmanagement.org listserve as well. I read this whole feed and I know what I see with my own eyeballs on my own Windows XPs that do not have these issues.
Was this answer helpful?

0 comments No comments
Anonymous

2013-12-13T00:42:35+00:00

Virusese do not come from Microsoft update. Folks I have a working BITS here and not seeing what you guys are seeing. Would someone here be willing to let me open a case and see what's REALLY going on here? This feels like malware - not a bug in an update.

Email me at susan-at-msmvps.com (change the -at- to @)

if you read the whole feed you would not say this there server can be infected passing it on, otherwise there security is worthless, by the way do you work for Microsoft? My second computer was working fine until there updates, Have read the thread about the 2 flags being added not present in either.
Was this answer helpful?

0 comments No comments