Background Intelligent Transfer Service is missing in XP

Doug, You should see this just posted in another thread as there could be some more faulty Fix its that are still doing the same thing as the 2 that you tagged. 

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/background-intelligent-transfer-service/62418f22-4803-41a2-9e41-5f4616366d47?page=2#LastReply

Hi there

It looks like you are almost there - just something is missing - without reviewing every single post and suggestion it is tricky to give a surgical answer. However just one quick tought:

Keith stated that: 

[QUOTE] My note to Gerd, you may skip this next step since you have already installed the cumulative security update for IE8 for December.

Go to this link and install the IE8 cumulative December update:

http://www.microsoft.com/en-gb/download/details.aspx?id=41404

[/QUOTE]

Now I assume you downloaded the IE8 Cumulative Update - but did you actually double click on the downloaded file and see it install?

Just a thought - sorry if this is just too obvious to be possible.

http://support.microsoft.com/kb/883822  shows a portion of the procedure for doing this manually

and the link I posted earlier

http://support.microsoft.com/kb/916251  shows some of the rest of the procedure for doing this manually

The portion of a post which you copied is not Dougs work but is done by Xircal.  See the linked thread and the post by Xircal marked Answer

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/win-xp-pro-sp3-update-does-not-start/a583105f-6a52-4d69-94ee-6fc3e2da3c8a

another example is linked here

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/windows-xp-updates-site-hangs/c83bb8d9-7e3f-40e0-b985-4d0ada0b54e5

To give some background on this issue see this thread also marked Answer where Jose Posada is providing some of the Microsoft source links

http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/error-0x80246008-windows-updates/6653041a-2f12-4edb-b610-c73c2699724c

For the past two months there have been an assortment of issues with windows updates which are often simple to fix as having the user turn off automatic updates in control panel and then to manually download and install the latest released cumulative security update for IE8 and this workaraound will fix the issue with CPU usage at 100% by svchost, IF the users computer is otherwise functioning correctly and has no corrupted files usually this would involve either the windows update agent or the BITS.  So an approach to troubleshooting goes through certain steps which have been found to fix the issues with windows updates without ever necessarily knowing for certain what was the cause of the entire problem.  For the scenario where a problem involves BITS there are different methods which can be used to partly repair the existing installation of BITS, or to go further and reinstall BITS entirely.

For example one method of reinstalling BITS is outlined by Xircal.  There are variations posted where even Xircal has amended the procedure to simplify it.  It was decided for example that creating the folder in system32 and naming it bits and pasting in the folder the qmgr.dll file is not necessary.  It doesn't hurt anything to create that folder but it doesn't actually do anything either.  And there is some overlap for that method of Xircal with other methods which involve less use of run commands and the typing of commands after a Run > cmd to get a command prompt.

The steps which you took would possibly have been accomplished by running the reg fix that Doug provided even though the fix was designed to target a specific different renaming error which causes an issue with BITS to stop working, the reg file could also fix other problems, such as missing parameters for BITS which is something that a command line will otherwise be required to fix.

There is some question about what can be done from the Run command and what must be done at a command prompt and this seems to vary in Microsoft's own descriptions. Whether the effect is the same either way or not is an unknown.  This tends to muddy the water about exactly which commands are effective and the desired changes actually made.

For example if you navigate in explorer to the C:\Windows\inf folder and right click a file named qmgr showing no extension there will be a menu on which you may click install and the installation of BITS will take place automatically and when prompted for the Windows CD and file path to the files needed for installation you may simply type in a new path to C:\Windows\system32 and this is the equivalent of having executed the same command as a run command. But next for the run commands must be done another command for the parameters and the same holds true for manually activating the install by right clicking on the qmgr.inf file.   Dougs reg fix would have taken care of the registry for the parameters and control set entries and possibly covered the first two commands also for which you used the run command . So what I was contemplating is an equivalent procedure which would involve less typing but end up accomplishing the same result.  When you chose not to use Dougs reg file then the procedure will revert to the entering of the command lines one by one and not shortcutting the process greatly.

Full disclosure is that some of the issues but not all have been identified for cause and effect and what is needed to fix.  But it is not yet an exact science.  Maybe 9 of 10 times the steps being followed will be successful but then 1 time in 10 it will not be successful and why is not known.  There can also be a delayed effect after subsequent reboots when a fix thought not to have worked suddenly just starts working, but there is no guarantee such luck will be yours.  Sometimes doing the exact same procedure twice is required.  Why it doesn't work the first time is also unknown.

Hello Keith,

fisrt HAPPY NEW YEAR to you and many thanks for the new advises you posted for me.

Following your recommendation entering

Reg add HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup

manually did not change the situation.

So I turned to the links you posted.

a) Dougs reg file fix could not be carrried out as a file named

@%SystemRoot%\system32\qmgr.dll - read the rest of this post

was not sitting under services.msc. So I did not follow up on this.

b)Then I followed the opther link and in this link I found another one to one of Dougs posts. He wrote:

SECTION 2 FOR LAPTOPS ONLY==========================If qmgr.dll is only present in C:\WINDOWS\system32, do the following.Open the system32 folder, locate qmgr.dll, then right click it and choose Copy.Stay in system32 folder and right click anywhere and choose New, then Folder. Rename the new folder tobits (in lowercase).Open the bits folder you just created, right click in the right hand pane and choose Paste. You should see the qmgr.dll file appear in there.Close Windows Explorer and then go to Start, Run and copy/paste: regsvr32 qmgr.dll and click OKDo the same with this file: regsvr32 qmgrprxy.dll

I created the new bits folder and executed the 2 dll files.

I rebooted and was happy that I could now put BITS to Automatic and start it w/o getting the error meassage. So Error 2: cannot find the file specified when trying to start BITS was removed by this activity. Happy to see that.

Then I started an XP update (search for new updates). The running bar flashed endlessly (20 min) without showing a search result and the CPU covery again turned to 100%. I was unable to cancel the page and finally this ended in a complete crash as also using the task manager to stop all activities died not work anymore. So I took the battery out.

Any further ideas?

Best regards

Gerd

.