BITS Error 1290: 0x50a following updates

Can someone who has a broken box email me at susan at msmvps.com

I really need someone in this condition to work with me please?

Hello all,

I fixed this problem on my XP (SP3) machine with this program:

http://www.tweaking.com/content/page/windows_repair_all_in_one.html

There is a specific 'fix windows update' checkbox but that didn't work for me. There is a 'repair essential windows services' (or something) checkbox which fixed the BITS service for me.

Best of luck to you all,

Daniel Antrobus

Hi Susan

I did email you on the 17th Dec - and you replied and said you would try and replicate the BITS problem - any luck? I did report it by phone to Microsoft on 16-Dec

This is how I corrupted BITS on two of my XP boxes:

Faulty MS-Fix-It KB971058 - How do I reset Windows Update components?

http://support.microsoft.com/kb/971058/en-gb

The Vista / XP Version of this Fix-It has a problem!!

When run on an XP-SP3 Pro system the BITS registry is "corrupted"

The BITS registry is incorrectly updated - it is using the Win7 / Vista format entries 

For example:

"DisplayName"="@%SystemRoot%\system32\qmgr.dll,-1000"

"Description"="@%SystemRoot%\system32\qmgr.dll,-1001"

instead of the correct XP format

"DisplayName"="Background Intelligent Transfer Service"

"Description"="Transfers files in the background using idle network bandwidth. If the service is stopped, features such as Windows Update, and MSN Explorer ..............................."

Other elements of the BITS registry are also incorrect

See this file compare screengrab http://www.stargateuk.info/images/MS-Fix-It_XP_BITS_Registry.png

This is my own server and image - its safe

I also have the exported BITS registries before and after running the Fix-It

Trying to start the renamed BITS service fails:

Could not start the @%SystemRoot%\system32\qmgr.dll,-1000 service on Local Computer

Error 1290: 0x50a

Also posted here on the issue

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/bits-changed-to-systemrootsystem32qmgrdll-1000/9e59259a-ce09-42f6-9954-bfb6bb0f4f37?page=2

Registry merges have been done by several people which has been in some cases the entire fix and in some cases has been part of the fix.  The linked thread here is one example and there are other similar threads where a registry merge has been marked Answer even though it may not be the guaranteed complete fix for every case.

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/bits-appears-corrupt-on-fresh-xp-install/29353b45-7cbc-4320-a42b-33885c46daa8

See also this thread

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/windows-update-failed-get-error-message-0x80246008/1fd3ce28-62b2-454c-922b-3130e9106328

I think it is possible a simplified alternative procedure based upon Xircal's 2 different procedures for desktops and laptops may be integrated and rolled into 1 easier procedure for reinstalling BITS.

What I am contemplating is to navigate to the C:\WINDOWS\inf\qmgr file and right click and select "install" and then subsequently run the registry merge and reboot......that may be all it takes

I'm not certain that the folder in system32 named bits is actually even required, it may be or it may not, and I can't recall exactly what I was thinking but speculating as did Xircal I believe do the same if the bits folder was needed it could be created, which then became part of a procedure which worked, but I still have no certain idea that the creation of the bits folder was actually required and it may not be required at all.  I simply observed that folder was present in my own normally operating configuration and thought it might help for that folder to be there in case its absence was part of the problem on systems where BITS was broken.  However that bits folder could just be a redundant backup copy of qmgr.dll which is a spectator folder not involved in the installation of BITS or the subsequent operation of the BITS program.

If you have a machine with broken BITS then you may want to try some of these alternatives as possible less complicated to execute fixes.