BITS service is missing, how can I get it back?

Anonymous
2013-11-04T01:30:12+00:00

Original Title - BITS service    

BITS service is missing in windows xp how can I get it back, i do not have the orginal cd, help.

Windows for home | Previous Windows versions | Performance and system failures

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-12-12T14:25:13+00:00

Hi Xircal,

The December Patch Tuesday has me plumbing depths of Windows XP I never want to see again.  While exploring the posts in the community, I've found your advice extremely helpful and have managed to get the BITS running again on my venerable Dell XP desktop followed by a successful update of all the security patches.  I've had less success with an installation of XP that I run on a Mac in a VMWare virtual machine.  Until Tuesday, it had run for a couple of years without any problems.  Now, however, BITS is balking.

At first, it didn't exist on the services list,  Employing ElderL's registry fix, I've been able to add BITS to the services list. When I try to start the service, I get an alert stating "Could not start BITS service on Local Computer.  Error 1290: 0x50a." Thinking I need to follow your script to register the service, I started by checking to see that the qmgr.dll file is in the three locations you've listed.  It's not.  Search finds the file only in C:\WINDOWS\system32.  In fact, the folders C:\WINDOWS\ServicePackFiles\i386 and C:\WINDOWS\system32\bits don't exist in my WINDOWS folder.  So I'm stopped when I hit your proviso, "Provided they're all present."  System Properties confirms that I have SP3 installed in a 2002 version of Microsoft Windows XP Professional.

Can you advise me how to proceed?  Thanks in advance.

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2013-11-23T23:50:45+00:00

Thank you for the link ElderL I actually found some help there :)

I was pointed to a Link

http://www.winhelponline.com/blog/misc-registry-fixes-for-windows-7-xp-vista/

and it pointed me down to #14 in the list which I did download and run

I did manually go back to the services from the administrative tools and right click to open the properties for BITS and click the start

I have now returned to my Windows Updater and it was able to start and is currently Downloading the updates :)  feeling very optomisic  ATM

Was this answer helpful?

0 comments

43 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-12-23T16:37:59+00:00

     

    If you still refuse to believe me that is your choice - all I can do is present the evidence - Report it to Microsoft Tech Support - and wait for others to confirm or refute my findings. That is the way science works - examine the evidence - put forward a theory - and wait for it to be tested by others. 

     

    Respectfully Doug,

    But no, I think you're barking up the wrong tree blaming Fixit(s) as the cause of the problem.

    I say that because when I experienced the issue myself back in October, I hadn't run any. My system was hanging on the WUD site in the same way as many have described.

    At that particular point in time, I started looking for answers and tried a few Fixits myself. One of these pointed me in the right direction because it contained the description "Service registration missing or corrupt".

    From there, it was simply a case of tracking down which Service was the culprit and addressing it accordingly.

    You seem to have gone off at a tangent because in your particular case you claim that a Fixit you ran caused a problem on your system. That may well be possible. On the other hand, you might have misinterpreted the result.

    Personally, I think it's always wise to err on the side of caution. If you think that a particular Fixit is to blame, then you need to accumulate the evidence to prove your point. In that particular respect, running your own tests isn't enough. You need to find at least ten other users who experienced exactly the same problem as yourself.

    Also, you mentioned in your post that one of the three registry entries - can't remember which one - causes the 1290 error. If that is indeed the case, how come the user called ScottZac didn't get that error after running the BITS-FIX in this thread? http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/xp-home-fails-to-download-updates-after-one-or-two/ccb059ff-3309-4a02-aaa7-dc3e333c8146

    I've seen a number of other posts where users claim that it worked. So I'm afraid it's not all cut and dried like you say.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-12-23T17:06:26+00:00

    Ten other users? Give me a break.  How about one user not illusioned or confused from frustration and fatigue sort of like battle fatigue from struggling with a dysfunctional XP computer?   I'll go look for one of those and if I find even one much less ten I'll get back to you on this next year :-)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-12-23T19:25:58+00:00

    Ten other users? Give me a break.  How about one user not illusioned or confused from frustration and fatigue sort of like battle fatigue from struggling with a dysfunctional XP computer?   I'll go look for one of those and if I find even one much less ten I'll get back to you on this next year :-)

    Keith,

    10 out of 500 million worldwide. Not so much to ask is it?

    Incidentally, the reg fix which started the ball rolling was this one I believe posted by TheWraith: http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/windows-update-died-tried-many-solutions-still/7d5ec39f-086f-471f-a713-b195d4c4b24d

    You'll note that it's also been marked as "Answer" in spite of containing references to "DelayedAutoStart" and "ServiceSidType" which, according to Doug is going to cause problems. That being the case, why have 13 other users also marked it as such?

    Actually, I don't think those additional entries will do anything because "DelayedAutoStart" wasn't introduced until Vista according to MSDN - BITS Startup Type

    That being the case, XP would likely ignore commands it wasn't programmed to perform.

    While I wish Doug all the best with his quest, I think there's a definite danger of jumping to conclusions especially in the light of the email which appeared not so long ago pointing to WUA as the likely culprit. You've all read that I assume, but for those who haven't, here it is again: http://marc.info/?l=patchmanagement&m=138696900324972&w=2

    Was this answer helpful?

    0 comments