WTH is wrong with Windows Update?

By JustGeorge
in Microsoft (Windows)

 Share

Recommended Posts

Grand Master

JustGeorge

Posted
Posted

I have tried all day to get Updates for our XP machines via Windows Update. When the downloads initiate, they all fail shortly after. I had to manually download the KBs and install them one at a time. Needledd to say, my day wasn't very productive. I made sure I was logged in as administrator and that my date and times were correct. All our Win98 machines updated without problem. This happened last month with two of our PCs and now its all our Xp computers.

Link to comment
https://www.neowin.net/forum/topic/283029-wth-is-wrong-with-windows-update/
Share on other sites
Experienced

Caledai

Posted
Posted

Windows XP Clients use a different version of windows update to windows 2000 machines.

How did you use windows update with windows 98 as it is no longer supported.

I noticed this problem once v5 of windows update came out. Once BITS2 is installed, no updates download.

As far as I have been able to determine, this is because BITS2 uses either a different protocol/port/address that is being blocked by a firewall I had no controll over.

Grand Master

JustGeorge

Posted
  • Author
Posted

I didn't change any of the service settings at all. No one else did either. I'm the only one doing maintenance on the computers except the contracted IT guy that comes every other week and he said no changes were made. I will check into it though. Will also check the windows update log too.

As for Win98, they use windows update version 4. They all had updates to download. Might've been older updates, though. Its been a couple of months since I've really done any computer work. I have several different jobs where I work.

Grand Master

cork1958

Posted
Posted (edited)

BITS does have to be enabled, but not necessarily on auto. None of my 4 XP boxes have it on auto, all are on manual, and I've gotten 3 of the 4 machines all updated. About to do this one as soon as I finish this post.

They are still supporting 98 as far as these updates anyway, but I thought the extended life was supposed to be over last month? Oh well, grab 'em while you can!!

I'm sure your problem is just due to overloaded servers. Everyone is grabbing the updates now. I'm about to find out.

Edit:

Nope, can't blame it on the MS servers. All 9 updates installed, rebooted and rockin' & rollin' again!!

Edited by cork1958
Grand Master

JustGeorge

Posted
  • Author
Posted

Here is the last portion of the Windows update log:

2005-02-09 11:11:11-0500 852 780 WU client finished Searching for update

2005-02-09 11:11:11-0500 852 780 WU client calls back to search call WindowsUpdate with code Call complete and error 0

2005-02-09 11:11:11-0500 852 780 WU client completed and deleted call {7ACBABD6-CDF7-4FDF-9C37-32B5B88ACC73}

2005-02-09 11:11:16-0500 852 780 REPORT EVENT: {28814899-C65A-45FB-ADE1-3C0979B5369B} 27 2005-02-09 11:11:11-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.

2005-02-09 11:11:16-0500 852 780 Reopened existing event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{763D54B6-6145-45DB-9E1A-6BC872338F62}.bin for writing.

2005-02-09 11:11:21-0500 852 454 ISusInternal API failed CClientCallRecorder::DisconnectCall with error 0x8024000c

2005-02-09 11:11:21-0500 1400 57c ISusInternal::DisconnectCall failed, hr=8024000C

2005-02-09 11:13:35-0500 852 358 Service received logoff notification

2005-02-09 11:16:12-0500 1376 56c Out of proc datastore is shutting down

2005-02-09 11:16:13-0500 1376 56c Out of proc datastore is now inactive

2005-02-09 12:49:40-0500 852 358 Service received logon notification

2005-02-09 13:07:49-0500 852 364 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{8FE6F2B1-7BC5-4C76-BF12-6627D6FC1D88}.bin for reading.

2005-02-09 13:07:50-0500 1872 2ec Trying to make out of proc datastore active

2005-02-09 13:07:51-0500 1872 2ec Out of proc datastore is now active

2005-02-09 13:07:51-0500 852 364 PT: Using serverID {9482F4B4-E343-43B6-B170-9A65BC822C77}

2005-02-09 13:07:51-0500 852 364 PT: Using server URL https://v5.windowsupdate.microsoft.com/Clie...ice/client.asmx

2005-02-09 13:07:51-0500 852 364 PT: Using serverID {9482F4B4-E343-43B6-B170-9A65BC822C77}

2005-02-09 13:07:51-0500 852 364 PT: Using server URL https://v5.windowsupdate.microsoft.com/Clie...ice/client.asmx

2005-02-09 13:07:51-0500 852 364 URL for server is http://v5stats.windowsupdate.microsoft.com...WebService.asmx

2005-02-09 13:07:51-0500 852 364 Trying to upload 5 events using cached cookie.

2005-02-09 13:08:05-0500 852 364 DetectCompressionType returning type 0, hr=0x1

2005-02-09 13:08:05-0500 852 364 Failed to upload events to the server due to an unexpected client SOAP exception (code = 32669844). Giving up on this event batch.

2005-02-09 13:08:05-0500 852 364 Failed to upload events with hr = 8024400d.

2005-02-09 13:08:05-0500 852 364 Deleted event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{8FE6F2B1-7BC5-4C76-BF12-6627D6FC1D88}.bin.

2005-02-09 13:12:51-0500 1872 2ec Out of proc datastore is shutting down

2005-02-09 13:12:52-0500 1872 2ec Out of proc datastore is now inactive

2005-02-09 13:24:42-0500 852 358 Service received logoff notification

2005-02-10 07:50:43-0500 852 358 Service received logon notification

Mentor

andy2004

Posted
Posted

windows update fails for me as well. I have 4 xp pro machines all connected in a workgroup 2 of the machines will update fine the other 2 fail though.

update log :

2005-02-10 13:27:21-0000 964 1f4 WU client succeeds CClientCallRecorder::BeginFindUpdates from WindowsUpdate with call id {1A2F3561-CA6B-4062-90CD-A2EA8DE6835D}

2005-02-10 13:27:21-0000 964 6a8 WU client executing call {1A2F3561-CA6B-4062-90CD-A2EA8DE6835D} of type Search Call

2005-02-10 13:27:21-0000 964 6a8 PT: Using serverID {9482F4B4-E343-43B6-B170-9A65BC822C77}

2005-02-10 13:27:21-0000 964 6a8 PT: Using server URL https://v5.windowsupdate.microsoft.com/Clie...ice/client.asmx

2005-02-10 13:27:21-0000 964 6a8 Add header for accept-encoding: xpress succeeded

2005-02-10 13:27:22-0000 964 6a8 DetectCompressionType returning type 1, hr=0x0

2005-02-10 13:27:22-0000 964 6a8 Add header for accept-encoding: xpress succeeded

2005-02-10 13:27:24-0000 964 6a8 DetectCompressionType returning type 1, hr=0x0

2005-02-10 13:27:24-0000 964 6a8 PT: Using serverID {9482F4B4-E343-43B6-B170-9A65BC822C77}

2005-02-10 13:27:24-0000 964 6a8 PT: Using server URL https://v5.windowsupdate.microsoft.com/Clie...ice/client.asmx

2005-02-10 13:27:24-0000 964 6a8 Add header for accept-encoding: xpress succeeded

2005-02-10 13:27:24-0000 964 6a8 DetectCompressionType returning type 1, hr=0x0

2005-02-10 13:27:24-0000 964 6a8 WU client add update {DD8B510F-12CF-4244-B090-344A760D22E6}.100 to search result

2005-02-10 13:27:24-0000 964 6a8 DeviceStatus: 0x180600a, DeviceProblemNumber: 00000000

2005-02-10 13:27:24-0000 964 6a8 WU client add update {B64FC30C-46B6-455B-B083-92A67239E827}.100 to search result

2005-02-10 13:27:24-0000 964 6a8 WU client add update {F6EE8217-38C2-4490-ADD5-EF9E514544BF}.102 to search result

2005-02-10 13:27:24-0000 964 6a8 WU client add update {8A1423ED-CE96-42DC-84B3-C51CEC59EA87}.100 to search result

2005-02-10 13:27:24-0000 964 6a8 WU client found 4 updates and 11 categories in search

2005-02-10 13:27:24-0000 964 6a8 WU client finished Searching for update

2005-02-10 13:27:24-0000 964 6a8 WU client calls back to search call WindowsUpdate with code Call complete and error 0

2005-02-10 13:27:24-0000 964 6a8 WU client completed and deleted call {1A2F3561-CA6B-4062-90CD-A2EA8DE6835D}

2005-02-10 13:27:29-0000 964 3e8 REPORT EVENT: {66DF17DF-188A-43E3-94E5-E9737939E496} 159 2005-02-10 13:27:24-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.

2005-02-10 13:27:35-0000 964 4f0 WU client persisted 1 download calls

2005-02-10 13:27:35-0000 964 4f0 WU client succeeds CClientCallRecorder::BeginDownloadUpdates from WindowsUpdate with call id {EE3A457E-55E6-478F-9C87-2020CFFE6517}

2005-02-10 13:27:35-0000 964 3e8 WU client executing call {EE3A457E-55E6-478F-9C87-2020CFFE6517} of type Download Call

2005-02-10 13:27:35-0000 964 3e8 Dumping out update 1 of 1

2005-02-10 13:27:35-0000 964 3e8 title = Windows Malicious Software Removal Tool - February 2005 (KB890830)

2005-02-10 13:27:35-0000 964 3e8 dumping updateId {8A1423ED-CE96-42DC-84B3-C51CEC59EA87}.100 bundling 1 updates

2005-02-10 13:27:35-0000 964 3e8 bundled update No. 1 is {9FB7A262-D213-4A39-98A6-6AE07962CC54}.100

2005-02-10 13:27:35-0000 964 3e8 DM: pDownloadJob->Init failed with 0x80246005.

2005-02-10 13:27:35-0000 964 3e8 Got error (hr = 80246005) starting update 0 in call 4. Notifying call.

2005-02-10 13:27:35-0000 964 3e8 Error 80246005 occurred while downloading update; notifying dependent calls.

2005-02-10 13:27:35-0000 964 3e8 WU client persisted 1 download calls

2005-02-10 13:27:35-0000 964 3e8 WU client persisted 1 download calls

2005-02-10 13:27:35-0000 964 3e8 WU client calls back to download call {EE3A457E-55E6-478F-9C87-2020CFFE6517} with code Call complete and error 0

2005-02-10 13:27:35-0000 964 3e8 WU client completed and deleted call {EE3A457E-55E6-478F-9C87-2020CFFE6517}

2005-02-10 13:27:35-0000 964 3e8 WU client persisted 0 download calls

2005-02-10 13:27:36-0000 964 fdc ISusInternal API failed CClientCallRecorder::DisconnectCall with error 0x8024000c

2005-02-10 13:27:36-0000 2312 d04 ISusInternal::DisconnectCall failed, hr=8024000C

2005-02-10 13:27:40-0000 964 3e8 REPORT EVENT: {AB1898D7-B0AA-41E0-AA9D-7BEA16CCCD9A} 160 2005-02-10 13:27:35-0000 1 161 101 {8A1423ED-CE96-42DC-84B3-C51CEC59EA87} 100 80246005 WindowsUpdate Failure Content Download Error: Download failed.

2005-02-10 13:27:40-0000 964 3e8 REPORT EVENT: {BEED8D3A-A85B-411C-8B58-9F86997A30E4} 161 2005-02-10 13:27:35-0000 1 161 101 {9FB7A262-D213-4A39-98A6-6AE07962CC54} 100 80246005 WindowsUpdate Failure Content Download Error: Download failed.

ive googled this ALOT and some of the work arounds work like stopping wuauserv deleting the contents of the SoftwareDistribution folder , then restarting wuauserv or doing regsvr wuaueng.dll but then going to windows update after a machine reboot causes windows update to fail again.

Ive tried looking for the bits update to uninstall but i cant find it so unless there is an answer i guess im stuck till wu v6 is released

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.