Hi,
Could you please post the step-by-step directions you got?
Regards,
Torgeir
Rachel L wrote:
> Yuo are right - actually it's only 14. And I finally eked out the salient
> (apparently) error number too, which is 0x80246008, which, a MS tech
> explained to me is probably a currupted BITS. She sent me step-by-step
> directions, and I actually got to Step 2.4 in her response. I pasted a long
> line into the CMD line and hit run, and it returned a "this already exists:
> repleace it? (Y/N)" and I am waiting for her to write me back (over a day
> now) with the answer.
>
> ROFL. Ah well. We'll see what is in store should she reply.
>
> Thanks!
>
> "jaam" wrote:
>
>
>>I have the exact same problem as you. Slightly different error message, but
>>exact same description.
>>
>>PS - you don't have to download all 200 updates - in reality its probably
>>only around 30 that you would need to update. Time consuming but is a
>>possiblity if they never get around to fixing it. Almost wish I was back with
>>the blue screen of death.
>>
>>"Rachel L" wrote:
>>
>>
>>>Every day, windows update runs on my Sony VAIO Windows XP HOME desktop, and
>>>fails to download and install the updates. I now have at least 200 pages in
>>>my Windows Update History of failed installations. Each of the entries has
>>>white "x" in a red circle and a little yellow question mark.
>>>
>>>The MS Telephone "Help" suggested that the fix is to install them manually.
>>>All 200 pages. I don't think so. Any solution that involves locating and
>>>downloading 200 pages of a bazillion KBnnnnnn updates is not a solution. I
>>>think a solution would involve first locating and fixing the problem with the
>>>update process and then allowing the whole thing to proceed manually.
>>>Unfortunately, I am not a software engineer.
>>>
>>>Also, my Sony VAIO did not come with a WXP HOME CD, so I can't put the the
>>>installation CD in the disk drive, so any solution that starts with "Put your
>>>XP Home CD in the drive..." is not an option either. Sony has been such a
>>>non-help that I am seriously considering eschewing their entire product line
>>>for the rest of my life.
>>>
>>>I have a big log file of history of error failures. It contains helpful
>>>entries such as:
>>>
>>>2005-09-14 18:23:00 1104 554 DnldMgr FATAL: BITS service was not fixed up
>>>and thus CCI was not reattempted. (hr = 80080005)
>>>2005-09-14 18:23:00 1104 554 DnldMgr FATAL: Failed to connect to the BITS
>>>service; unable to start new downloads or interact with existing download
>>>jobs. (hr = 80080005)
>>>2005-09-14 18:23:00 1104 554 DnldMgr FATAL:
>>>DM:CAgentDownloadManager::GetDownloadDataAndHan dler: GetBitsManager failed
>>>with 0x80246008.
>>>2005-09-14 18:23:00 1104 554 DnldMgr FATAL:
>>>DM:CAgentDownloadManager::GenerateAllDownloadRe quests:
>>>GetDownloadDataAndHandler failed with 0x80246008.
>>>2005-09-14 18:23:00 1104 554 DnldMgr Error 0x80246008 occurred while
>>>downloading update; notifying dependent calls.
>>>2005-09-14 18:23:01 1104 554 DnldMgr WARNING: Extended error for reported
>>>error 80246008 = 80080005
>>>...
>>>[the log is many many many lines long as this has been going on for some
>>>time now]
>>>
>>>...
>>>2005-09-14 18:23:35 1104 5f8 AU <<## SUBMITTED ## AU: Download updates
>>>2005-09-14 18:23:35 1104 554 Report REPORT EVENT:
>>>{6323A123-5626-471A-93FB-FDB8253AD292} 2005-09-14
>>>18:23:01-0700 1 161 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 80246008 AutomaticUpdates Failure Content Download Error: Download failed.
>>>
>>>
--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx