Windows Update continues to fail for me..

I'll post the relevant section from my windowsupdate.log in the hopes that someone is able to understand whats going on and assist me.

2006-06-07 09:57:47 2124 cf4 COMAPI -------------
2006-06-07 09:57:47 2124 cf4 COMAPI -- START -- COMAPI: Search [ClientId = WindowsUpdate]
2006-06-07 09:57:47 2124 cf4 COMAPI ---------
2006-06-07 09:57:47 2124 cf4 COMAPI - Online = Yes; Ignore download priority = No
2006-06-07 09:57:47 2124 cf4 COMAPI - Criteria = "IsInstalled=0 and IsHidden=1"
2006-06-07 09:57:47 2124 cf4 COMAPI - ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77}
2006-06-07 09:57:47 2124 cf4 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = WindowsUpdate]
2006-06-07 09:57:48 1100 b0 Agent *************
2006-06-07 09:57:48 1100 b0 Agent ** START ** Agent: Finding updates [CallerId = WindowsUpdate]
2006-06-07 09:57:48 1100 b0 Agent *********
2006-06-07 09:57:49 1100 b0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2006-06-07 09:57:49 1100 b0 PT + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://update.microsoft.com/v6/ClientWebService/client.asmx
2006-06-07 09:57:49 1100 b0 EEHndlr FATAL: MSI DLL version is 2.0. Version 3.1 is required.
2006-06-07 09:57:49 1100 b0 Agent WARNING: Failed to evaluate Installed rule, updateId = {8C3FCC84-7410-4A95-8B89-A166A0190486}.102, error = 0x80241001
2006-06-07 09:57:50 1100 b0 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2006-06-07 09:57:50 1100 b0 PT WARNING: SOAP Fault: 0x00012c
2006-06-07 09:57:50 1100 b0 PT WARNING: faultstring:Fault occurred
2006-06-07 09:57:50 1100 b0 PT WARNING: ErrorCode:ConfigChanged(2)
2006-06-07 09:57:50 1100 b0 PT WARNING: Message:

2006-06-07 09:57:50 1100 b0 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2006-06-07 09:57:50 1100 b0 PT WARNING: ID:344d0ffe-1af5-409d-9480-de83d922cab1
2006-06-07 09:57:51 1100 b0 PT WARNING: GetConfig failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200
2006-06-07 09:57:51 1100 b0 PT WARNING: Sync of Updates: 0x8024400a
2006-06-07 09:57:51 1100 b0 Agent * WARNING: Failed to synchronize, error = 0x8024400A
2006-06-07 09:57:51 1100 b0 Agent * WARNING: Exit code = 0x8024400A
2006-06-07 09:57:51 1100 b0 Agent *********
2006-06-07 09:57:51 1100 b0 Agent ** END ** Agent: Finding updates [CallerId = WindowsUpdate]
2006-06-07 09:57:51 1100 b0 Agent *************
2006-06-07 09:57:51 1100 b0 Agent WARNING: WU client failed Searching for update with error 0x8024400a
2006-06-07 09:57:51 2124 d18 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = WindowsUpdate]
2006-06-07 09:57:51 2124 d18 COMAPI - Updates found = 0
2006-06-07 09:57:51 2124 d18 COMAPI - WARNING: Exit code = 0x00000000, Result code = 0x8024400A
2006-06-07 09:57:51 2124 d18 COMAPI ---------
2006-06-07 09:57:51 2124 d18 COMAPI -- END -- COMAPI: Search [ClientId = WindowsUpdate]
2006-06-07 09:57:51 2124 d18 COMAPI -------------
2006-06-07 09:57:51 2124 cf4 COMAPI WARNING: Operation failed due to earlier error, hr=8024400A
2006-06-07 09:57:51 2124 cf4 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024400A)
2006-06-07 09:57:56 1100 b0 Report REPORT EVENT: {7A36CEC5-C1B9-4609-A9AD-79EC0174051F} 2006-06-07 09:57:51+1000 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400a WindowsUpdate Failure Software Synchronization Error: Agent failed detecting with reason: 0x8024400a

Firefly! ~Keep Flying~

this is what i found

A client computer fails with a "0x8024400a" error code when it retrieves new updates from a WSUS server that is running Windows Server 2003 Service Pack 1
View products that this article applies to.
Article ID : 905422
Last Review : May 3, 2006
Revision : 2.1
SYMPTOMS
A client computer cannot receive new updates or does not appear in the Administration Console when the computer points to a Microsoft Windows Server Update Services (WSUS) server. The WSUS server is running on a Microsoft Windows Server 2003 Service Pack 1-based computer. The Windows Update log may indicate that the client computer's connection to the WSUS server fails with a "0x8024400a" error code.
Back to the top

CAUSE
When you send a POST request to a server that is running Microsoft Internet Information Services (IIS) 6.0, IIS may send an "HTTP 100 Continue" response in the middle of the response stream. Sometimes, IIS incorrectly sends the "HTTP 100 Continue" response after IIS has sent the “HTTP 200 OK” response.
Back to the top

RESOLUTION
To resolve this problem, install the hotfix that is described in the following Microsoft Knowledge Base article:
898708 (http://support.microsoft.com/kb/898708/) FIX: IIS 6.0 may send an "HTTP 100 Continue" response in the middle of the response stream when you send a POST request
Back to the top

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top

----------------------

APPLIES TO
• Microsoft Internet Information Services 6.0, when used with:
Microsoft Windows Server 2003, 64-Bit Datacenter Edition
Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Microsoft Windows Server 2003, Datacenter x64 Edition
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Microsoft Windows Server 2003, Enterprise x64 Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Standard x64 Edition
Microsoft Windows Server 2003, Web Edition

Kitty

Thanks for the response though it doesnt seem particularly relevant to me and my XP home OS.

Firefly! ~Keep Flying~

PROBLEM SOLVED!

I searched for a long time and very thoroughly and came across many suggested solutions all of which didnt work for me.. I found only one particular helpful post which I regretedly cant remember the link to.

The solution to this particular problem is as follows :

Start in "Safe Mode"

Search for the following files
wuapi.dll
wuauclt1.exe
wuauclt.exe
wuaucpl.cpl
wuaueng1.dll
wuaueng.dll
wuauserv.dll
wucltui.dll
wupdmgr.exe
wups2.dll
wups.dll
wuweb.dll

Rename all these files as ".old"

Reboot in Normal Mode and Bobs your uncle.

Firefly! ~Keep Flying~