Download of Updates Fails - BITS Refuses to Start

[Mitch]

From what I can see this machine successfully downloaded and installed
updates prior to this batch (August updates approved last night on our WSUS
server). BITS is not running and complains when I attempt to restart it.
These are the two error messages in the System Log:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 24/09/2009
Time: 10:51:03 AM
User: NT AUTHORITY\SYSTEM
Computer: C7076
Description:
The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM
within the required timeout.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

and

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 24/09/2009
Time: 10:50:33 AM
User: N/A
Computer: C7076
Description:
The Background Intelligent Transfer Service service terminated with the
following error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I checked the windowsupdate.log and all appears normal until this series of
lines:

2009-09-23 18:48:52:724 1916 cc8 DnldMgr * Queueing update for download
handler request generation.
2009-09-23 18:48:52:724 1916 cc8 DnldMgr Generating download request for
update {3F633490-FCA8-4758-88F1-835D32EAD543}.100
2009-09-23 18:50:22:867 1916 cc8 DnldMgr FATAL: BITS service was not fixed
up and thus CCI was not reattempted. (hr = 80080005)
2009-09-23 18:50:22:867 1916 cc8 DnldMgr FATAL: Failed to connect to the
BITS service; unable to start new downloads or interact with existing
download jobs. (hr = 80080005)
2009-09-23 18:50:22:867 1916 cc8 DnldMgr FATAL:
DM:CAgentDownloadManager::GetDownloadDataAndHandler: GetBitsManager failed
with 0x80246008.
2009-09-23 18:50:22:867 1916 cc8 DnldMgr FATAL:
DM:CAgentDownloadManager::GenerateAllDownloadRequests:
GetDownloadDataAndHandler failed with 0x80246008.
2009-09-23 18:50:22:882 1916 cc8 DnldMgr Error 0x80246008 occurred while
downloading update; notifying dependent calls.
2009-09-23 18:50:22:992 1916 cc8 DnldMgr WARNING: Extended error for
reported error 80246008 = 80080005
2009-09-23 18:50:22:992 1916 cc8 DnldMgr WARNING: Extended error for
reported error 80246008 = 80080005
2009-09-23 18:50:23:007 1916 cc8 Agent *********
2009-09-23 18:50:23:007 1916 cc8 Agent ** END ** Agent: Downloading
updates [CallerId = AutomaticUpdates]
2009-09-23 18:50:23:007 1916 cc8 Agent *************
2009-09-23 18:50:23:007 1916 16b0 AU AU initiated download, updateId =
{EE69B39F-4DEE-4BD9-8FF2-D01B082E2C4A}.101, callId =
{AB6CFB1E-A61B-4A20-918D-51ACBC0BC3E9}
2009-09-23 18:50:23:007 1916 cc8 DnldMgr *************
2009-09-23 18:50:23:007 1916 cc8 DnldMgr ** START ** DnldMgr: Downloading
updates [CallerId = AutomaticUpdates]
2009-09-23 18:50:23:007 1916 cc8 DnldMgr *********
2009-09-23 18:50:23:007 1916 cc8 DnldMgr * Call ID =
{B238859D-5890-4EDE-9143-F720DFAE63EA}
2009-09-23 18:50:23:007 1916 cc8 DnldMgr * Priority = 2, Interactive = 0,
Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-09-23 18:50:23:007 1916 cc8 DnldMgr * Updates to download = 1
2009-09-23 18:50:23:007 1916 cc8 Agent * Title = Security Update for
Windows XP Service Pack 3 (KB973540)
2009-09-23 18:50:23:007 1916 cc8 Agent * UpdateId =
{FC7C3752-4C17-473C-8BFF-75EED375FD61}.101
2009-09-23 18:50:23:007 1916 16b0 AU AU initiated download, updateId =
{F2FD5FA8-ED91-46D1-8D1A-944DC783244C}.101, callId =
{CE63CC87-75C5-466A-8875-802DFE8C9639}
2009-09-23 18:50:23:007 1916 cc8 Agent * Bundles 1 updates:
2009-09-23 18:50:23:007 1916 cc8 Agent *
{F9B10375-898C-4D12-8722-B2F7F6E81521}.101
2009-09-23 18:50:23:039 1916 cc8 DnldMgr *********** DnldMgr: New download
job [UpdateId = {F9B10375-898C-4D12-8722-B2F7F6E81521}.101] ***********
2009-09-23 18:50:23:039 1916 cc8 DnldMgr * Queueing update for download
handler request generation.
2009-09-23 18:50:23:039 1916 cc8 DnldMgr Generating download request for
update {F9B10375-898C-4D12-8722-B2F7F6E81521}.101
2009-09-23 18:51:53:119 1916 cc8 DnldMgr FATAL: BITS service was not fixed
up and thus CCI was not reattempted. (hr = 80080005)
2009-09-23 18:51:53:119 1916 cc8 DnldMgr FATAL: Failed to connect to the
BITS service; unable to start new downloads or interact with existing
download jobs. (hr = 80080005)
2009-09-23 18:51:53:119 1916 cc8 DnldMgr FATAL:
DM:CAgentDownloadManager::GetDownloadDataAndHandler: GetBitsManager failed
with 0x80246008.
2009-09-23 18:51:53:119 1916 cc8 DnldMgr FATAL:
DM:CAgentDownloadManager::GenerateAllDownloadRequests:
GetDownloadDataAndHandler failed with 0x80246008.
2009-09-23 18:51:53:119 1916 cc8 DnldMgr Error 0x80246008 occurred while
downloading update; notifying dependent calls.
2009-09-23 18:51:53:119 1916 cc8 DnldMgr WARNING: Extended error for
reported error 80246008 = 80080005
2009-09-23 18:51:53:119 1916 cc8 DnldMgr WARNING: Extended error for
reported error 80246008 = 80080005
2009-09-23 18:51:53:135 1916 16b0 AU AU initiated download, updateId =
{8A146CAF-F475-45E0-A8C4-0B02DBF6ABC5}.101, callId =
{022A9DE9-C817-4FA9-AD69-AE78EC2A2348}
2009-09-23 18:51:53:135 1916 cc8 Agent *********
2009-09-23 18:51:53:135 1916 cc8 Agent ** END ** Agent: Downloading
updates [CallerId = AutomaticUpdates]
2009-09-23 18:51:53:135 1916 cc8 Agent *************

I've scoured the internets and I see all sorts of "fixes" but none seem
connected to what I'm seeing so I'm offering the details up here for your
input. FYI this is an XP Pro machine with SP3 installed. Any help would be
greatly appreciated.

Thanks!

[Mitch]

I think I posted this in the wrong category. Sorry about that chief.

[MowGreen]

You did the Steps listed here ?
http://support.microsoft.com/kb/916251

and then reinstalled BITS as described here ?
http://support.microsoft.com/kb/842773

MowGreen
===============
*-343-* FDNY
Never Forgotten
===============

banthecheck.com
"Security updates should *never* have *non-security content* prechecked"

[Mitch]

No, I don't receive an error message when I try to start BITS on the
offending machine. It just doesn't start. Is there an indicator that tells
me I should reinstall the BITS following the second kb article? Is this a
symptom of a known issue with BITS? Thanks.

[MowGreen]

> I've scoured the internets and I see all sorts of "fixes" but none seem
>> connected to what I'm seeing so I'm offering the details up here for your
>> input.

I suggested you try the Steps listed in KB916251, not that you received
an error message when trying to start BITS. It doesn't start because

> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7023
> Date: 24/09/2009
> Time: 10:50:33 AM
> User: N/A
> Computer: C7076
> Description:
> The Background Intelligent Transfer Service service terminated with the
> following error:
> The specified module could not be found.

Following the steps in KB916251 will repair BITS *except* in a situation
where the OS is infected with malware or, when certain antivirus
programs are installed that damage BITS.

Windows XP Update BITS Fix
http://www.philmorgan.net/techie-tools/windows-update-bits-background-intelligent-transfer-service-fix-batch-file-for-windows-xp

IF you are *certain* that the system is malware free and the installed
antivirus is not a Norton or McAfee product, then suggest you run
WinXP_BITS_Fix_v1.6. Instructions are available on Phil's web page.

IF you are not certain that the system is malware free, then download
the free version of Malwarebytes Anti-malware (MBAM):
http://www.malwarebytes.org

Click the Download free version button and *save* the download.
Once it completes close all open programs and browsers and install it.
Allow it to update it's definitions during the installation process.
Then open MBAM, ensure that the Quick scan option is checked, click the
Scan button.
When the scan is finished click the Show results button.
Ensure any detected objects are checked, then click the Show reults button.
Ensure that anything [IF anything] that was detected is checked and then
click the Remove selected button.

[Mitch]

Many thanks.

[matthe...@gmail.com]

Thanks so much for this. I hadn't been getting XP updates for two months and knew _something_ was wrong. I didn't see anything in the update logs until I let an "out of control" svchost.exe run to completion without killing it--wasn't admin at the time so couldn't. When I did let it run out I finally got the exact same update log message

FATAL: BITS service was not fixed up and thus CCI was not reattempted. (hr = 80080005)

FATAL: Failed to connect to the BITS service; unable to start new downloads or interact with existing download jobs. (hr = 80080005)

...

Error 0x80246008 occurred while downloading update; notifying dependent calls.

And googling led me here. I didn't even have a BITS service in the list (there was an odd "%sysroot%/.../qmgr.dll" service though.)

KB916251 (Method 1) did the trick. Had to do steps 1-8. KB842773 just told me that I was already on a later service pack and didn't do anything. I had updates within a few minutes--and a reboot or three.

[nonya...@gmail.com]

Found this searching for this error below, found in the
c:\windows\windowsupdate.log

FATAL: BITS service was not fixed up and thus CCI was not reattempted. (hr = 80080005)

FATAL: Failed to connect to the BITS service; unable to start new downloads or interact with existing download jobs. (hr = 80080005)

Error 0x80246008 occurred while downloading update; notifying dependent calls.

Fixit automated tool was giving: 0x80246008(2014-02-25-T-04_39_25P)

This post help me resolve a two month old problem with Windows Update (XP SP3), and Fixit. The update process would not initialize, or cancel.

KB916251 (Method 1) did the trick, stopped at Step 6. The directions are a bit ambiguous as to remaining steps if BITS starts successfully. Once it did, I changed the start type from Manual to Automatic. Then applied 21 critical items to get current.

Also, KB842773 mentioned in KB916251 was unhelpful, since it's dated, and wouldn't installed due to SP level.

Also ran a malware scan just to be sure there was no virus.

21 Critical Updates installed, and now current.

Also Security Essentials was not allowing updates, either. This fix resolved that issue, too.