Can't download new signatures - getting code 8024002b

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am unable to obtain new signatures for Defender. My last ones were
downloaded as part of the normal Windows Update 2 weeks ago.

Reading another thread, someone said to check WindowsUpdate.log to see what
was really happening. Here are the messages from the log file:

2006-03-01 10:17:24 976 a40 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-01 10:17:24 976 a40 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://cwysus00.corp.acxiom.net/ClientWebService/client.asmx
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-01 10:17:27 976 a40 PT SUS 1.0 server is detected
2006-03-01 10:17:27 976 a40 PT WARNING: Sync of Updates: 0x8024002b
2006-03-01 10:17:27 976 a40 Agent * WARNING: Failed to synchronize, error
= 0x8024002B
2006-03-01 10:17:27 976 a40 Agent * WARNING: Exit code = 0x8024002B
2006-03-01 10:17:27 976 a40 Agent *********
2006-03-01 10:17:27 976 a40 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-01 10:17:27 976 a40 Agent *************
2006-03-01 10:17:27 976 a40 Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-01 10:17:27 3604 1d8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI - Updates found = 0
2006-03-01 10:17:28 3604 1d8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-01 10:17:28 3604 1d8 COMAPI ---------
2006-03-01 10:17:28 3604 1d8 COMAPI -- END -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI -------------
2006-03-01 10:17:28 3604 e44 COMAPI WARNING: Operation failed due to earlier
error, hr=8024002B
2006-03-01 10:17:28 3604 e44 COMAPI FATAL: Unable to complete asynchronous
search. (hr=8024002B)
 
Having the same problem - can't update after the update of 15/02/06. Does
anyone have a fix yet for this as this is making Defender pretty useless for
me!

Richard Clegg
 
Windows Defender can't get updates via autoupdate from SUS--the updates are
not published to SUS.

It CAN get updates via autoupdate from WSUS. Since SUS has an end of life
of December, 2006, I hope your company is on the way to implementing it.

Additionally, you can go to Windows Update and pick up the updates.

--
 
You probably are not having the same problem, unless you are also on a
corporate network with a SUS server involved.

Harley posted a pice of his WindowsUpdate.log file--maybe you could do the
same?

The file name is windowsupdate.log, and it is in \windows (or \winnt or
whatever)

The file will be very large--it might be best to just attempt and update,
then open the log in notepad and cut and paste just the tail end relating to
the failed update attempt, into a message in this thread.

--

RJ Clegg said:
Having the same problem - can't update after the update of 15/02/06. Does
anyone have a fix yet for this as this is making Defender pretty useless
for
me!

Richard Clegg

Harley said:
I am unable to obtain new signatures for Defender. My last ones were
downloaded as part of the normal Windows Update 2 weeks ago.

Reading another thread, someone said to check WindowsUpdate.log to see
what
was really happening. Here are the messages from the log file:

2006-03-01 10:17:24 976 a40 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-01 10:17:24 976 a40 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://cwysus00.corp.acxiom.net/ClientWebService/client.asmx
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-01 10:17:27 976 a40 PT SUS 1.0 server is detected
2006-03-01 10:17:27 976 a40 PT WARNING: Sync of Updates: 0x8024002b
2006-03-01 10:17:27 976 a40 Agent * WARNING: Failed to synchronize,
error
= 0x8024002B
2006-03-01 10:17:27 976 a40 Agent * WARNING: Exit code = 0x8024002B
2006-03-01 10:17:27 976 a40 Agent *********
2006-03-01 10:17:27 976 a40 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-01 10:17:27 976 a40 Agent *************
2006-03-01 10:17:27 976 a40 Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-01 10:17:27 3604 1d8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI - Updates found = 0
2006-03-01 10:17:28 3604 1d8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-01 10:17:28 3604 1d8 COMAPI ---------
2006-03-01 10:17:28 3604 1d8 COMAPI -- END -- COMAPI: Search [ClientId
=
Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI -------------
2006-03-01 10:17:28 3604 e44 COMAPI WARNING: Operation failed due to
earlier
error, hr=8024002B
2006-03-01 10:17:28 3604 e44 COMAPI FATAL: Unable to complete
asynchronous
search. (hr=8024002B)
Click to expand...
Click to expand...
 
I have the same problem and here is the last log from windowsupdate log
--------------
2006-03-02 12:34:26 3016 43c COMAPI -------------
2006-03-02 12:34:26 3016 43c COMAPI -- START -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-02 12:34:26 3016 43c COMAPI ---------
2006-03-02 12:34:26 3016 43c COMAPI - Online = Yes; Ignore download
priority = No
2006-03-02 12:34:26 3016 43c COMAPI - Criteria = "(IsInstalled = 0 and
IsHidden = 0 and CategoryIDs contains '0a487050-8b0f-4f81-b401-be4ceacd61cd')
or (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains
'8c3fcc84-7410-4a95-8b89-a166a0190486')"
2006-03-02 12:34:26 3016 43c COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-03-02 12:34:26 3016 43c COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-02 12:34:26 1376 61c Agent *************
2006-03-02 12:34:26 1376 61c Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-02 12:34:26 1376 61c Agent *********
2006-03-02 12:34:26 1376 61c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-02 12:34:26 1376 61c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://WindowsUpdate/ClientWebService/client.asmx
2006-03-02 12:34:27 1376 61c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-02 12:34:27 1376 61c Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-02 12:34:27 1376 61c PT SUS 1.0 server is detected
2006-03-02 12:34:27 1376 61c PT WARNING: Sync of Updates: 0x8024002b
2006-03-02 12:34:27 1376 61c Agent * WARNING: Failed to synchronize, error
= 0x8024002B
2006-03-02 12:34:27 1376 61c Agent * WARNING: Exit code = 0x8024002B
2006-03-02 12:34:27 1376 61c Agent *********
2006-03-02 12:34:27 1376 61c Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-02 12:34:27 1376 61c Agent *************
2006-03-02 12:34:27 1376 61c Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-02 12:34:27 3016 4f8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-02 12:34:27 3016 4f8 COMAPI - Updates found = 0
2006-03-02 12:34:27 3016 4f8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-02 12:34:27 3016 4f8 COMAPI ---------
2006-03-02 12:34:27 3016 4f8 COMAPI -- END -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-02 12:34:27 3016 4f8 COMAPI -------------
--------------------------

Bill Sanderson said:
You probably are not having the same problem, unless you are also on a
corporate network with a SUS server involved.

Harley posted a pice of his WindowsUpdate.log file--maybe you could do the
same?

The file name is windowsupdate.log, and it is in \windows (or \winnt or
whatever)

The file will be very large--it might be best to just attempt and update,
then open the log in notepad and cut and paste just the tail end relating to
the failed update attempt, into a message in this thread.

--

RJ Clegg said:
Having the same problem - can't update after the update of 15/02/06. Does
anyone have a fix yet for this as this is making Defender pretty useless
for
me!

Richard Clegg

Harley said:
I am unable to obtain new signatures for Defender. My last ones were
downloaded as part of the normal Windows Update 2 weeks ago.

Reading another thread, someone said to check WindowsUpdate.log to see
what
was really happening. Here are the messages from the log file:

2006-03-01 10:17:24 976 a40 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-01 10:17:24 976 a40 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://cwysus00.corp.acxiom.net/ClientWebService/client.asmx
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-01 10:17:27 976 a40 PT SUS 1.0 server is detected
2006-03-01 10:17:27 976 a40 PT WARNING: Sync of Updates: 0x8024002b
2006-03-01 10:17:27 976 a40 Agent * WARNING: Failed to synchronize,
error
= 0x8024002B
2006-03-01 10:17:27 976 a40 Agent * WARNING: Exit code = 0x8024002B
2006-03-01 10:17:27 976 a40 Agent *********
2006-03-01 10:17:27 976 a40 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-01 10:17:27 976 a40 Agent *************
2006-03-01 10:17:27 976 a40 Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-01 10:17:27 3604 1d8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI - Updates found = 0
2006-03-01 10:17:28 3604 1d8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-01 10:17:28 3604 1d8 COMAPI ---------
2006-03-01 10:17:28 3604 1d8 COMAPI -- END -- COMAPI: Search [ClientId
=
Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI -------------
2006-03-01 10:17:28 3604 e44 COMAPI WARNING: Operation failed due to
earlier
error, hr=8024002B
2006-03-01 10:17:28 3604 e44 COMAPI FATAL: Unable to complete
asynchronous
search. (hr=8024002B)
Click to expand...
Click to expand...
Click to expand...
 
I'm not experienced at reading these things, but here's what I think may be
happening:

http://support.microsoft.com/?kbid=326596

indicates that the 0x80190194 is the equivalent of an HTTP 440 error--i.e.
file not found.

I believe this log indicates that you are on a managed network with a WSUS
server, but that the administrator has not enabled the class of updates that
would allow the Windows Defender signature updates to be available for
clients to grab.

That class of updates has been available since January 16th, but theres
somewhere in the admin interface to WSUS where the administrator has to
recognize the new class of updates and enable them

I might well be off the mark on this one, but that's what I'd guess from
reading this--does it make sense from what you know about your corporate
infrastructure?

--

anu said:
I have the same problem and here is the last log from windowsupdate log
--------------
2006-03-02 12:34:26 3016 43c COMAPI -------------
2006-03-02 12:34:26 3016 43c COMAPI -- START -- COMAPI: Search [ClientId
=
Windows Defender]
2006-03-02 12:34:26 3016 43c COMAPI ---------
2006-03-02 12:34:26 3016 43c COMAPI - Online = Yes; Ignore download
priority = No
2006-03-02 12:34:26 3016 43c COMAPI - Criteria = "(IsInstalled = 0 and
IsHidden = 0 and CategoryIDs contains
'0a487050-8b0f-4f81-b401-be4ceacd61cd')
or (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains
'8c3fcc84-7410-4a95-8b89-a166a0190486')"
2006-03-02 12:34:26 3016 43c COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-03-02 12:34:26 3016 43c COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-02 12:34:26 1376 61c Agent *************
2006-03-02 12:34:26 1376 61c Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-02 12:34:26 1376 61c Agent *********
2006-03-02 12:34:26 1376 61c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-02 12:34:26 1376 61c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://WindowsUpdate/ClientWebService/client.asmx
2006-03-02 12:34:27 1376 61c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-02 12:34:27 1376 61c Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-02 12:34:27 1376 61c PT SUS 1.0 server is detected
2006-03-02 12:34:27 1376 61c PT WARNING: Sync of Updates: 0x8024002b
2006-03-02 12:34:27 1376 61c Agent * WARNING: Failed to synchronize,
error
= 0x8024002B
2006-03-02 12:34:27 1376 61c Agent * WARNING: Exit code = 0x8024002B
2006-03-02 12:34:27 1376 61c Agent *********
2006-03-02 12:34:27 1376 61c Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-02 12:34:27 1376 61c Agent *************
2006-03-02 12:34:27 1376 61c Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-02 12:34:27 3016 4f8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-02 12:34:27 3016 4f8 COMAPI - Updates found = 0
2006-03-02 12:34:27 3016 4f8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-02 12:34:27 3016 4f8 COMAPI ---------
2006-03-02 12:34:27 3016 4f8 COMAPI -- END -- COMAPI: Search [ClientId
=
Windows Defender]
2006-03-02 12:34:27 3016 4f8 COMAPI -------------
--------------------------

Bill Sanderson said:
You probably are not having the same problem, unless you are also on a
corporate network with a SUS server involved.

Harley posted a pice of his WindowsUpdate.log file--maybe you could do
the
same?

The file name is windowsupdate.log, and it is in \windows (or \winnt or
whatever)

The file will be very large--it might be best to just attempt and update,
then open the log in notepad and cut and paste just the tail end relating
to
the failed update attempt, into a message in this thread.

--

RJ Clegg said:
Having the same problem - can't update after the update of 15/02/06.
Does
anyone have a fix yet for this as this is making Defender pretty
useless
for
me!

Richard Clegg

:

I am unable to obtain new signatures for Defender. My last ones were
downloaded as part of the normal Windows Update 2 weeks ago.

Reading another thread, someone said to check WindowsUpdate.log to see
what
was really happening. Here are the messages from the log file:

2006-03-01 10:17:24 976 a40 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-01 10:17:24 976 a40 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://cwysus00.corp.acxiom.net/ClientWebService/client.asmx
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
ShouldFileBeDownloaded
failed with 0x80190194
2006-03-01 10:17:27 976 a40 PT SUS 1.0 server is detected
2006-03-01 10:17:27 976 a40 PT WARNING: Sync of Updates: 0x8024002b
2006-03-01 10:17:27 976 a40 Agent * WARNING: Failed to synchronize,
error
= 0x8024002B
2006-03-01 10:17:27 976 a40 Agent * WARNING: Exit code = 0x8024002B
2006-03-01 10:17:27 976 a40 Agent *********
2006-03-01 10:17:27 976 a40 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-01 10:17:27 976 a40 Agent *************
2006-03-01 10:17:27 976 a40 Agent WARNING: WU client failed Searching
for
update with error 0x8024002b
2006-03-01 10:17:27 3604 1d8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI - Updates found = 0
2006-03-01 10:17:28 3604 1d8 COMAPI - WARNING: Exit code =
0x00000000,
Result code = 0x8024002B
2006-03-01 10:17:28 3604 1d8 COMAPI ---------
2006-03-01 10:17:28 3604 1d8 COMAPI -- END -- COMAPI: Search
[ClientId
=
Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI -------------
2006-03-01 10:17:28 3604 e44 COMAPI WARNING: Operation failed due to
earlier
error, hr=8024002B
2006-03-01 10:17:28 3604 e44 COMAPI FATAL: Unable to complete
asynchronous
search. (hr=8024002B)
Click to expand...
Click to expand...
Click to expand...
 
Here's another post from this group:
-----
It could be the same problem I just had.

If you are using a local WSUS Server, then Defender tries to get the
definion updates from that server only. So you have to set up the local WSUS
server to get the definion files via WSUS updates from Microsoft.
There are two additional synchronisation settings:
- Products: Windows Defender
- Classifications: Definition Updates.

Wolfgang
-----

--

anu said:
I have the same problem and here is the last log from windowsupdate log
--------------
2006-03-02 12:34:26 3016 43c COMAPI -------------
2006-03-02 12:34:26 3016 43c COMAPI -- START -- COMAPI: Search [ClientId
=
Windows Defender]
2006-03-02 12:34:26 3016 43c COMAPI ---------
2006-03-02 12:34:26 3016 43c COMAPI - Online = Yes; Ignore download
priority = No
2006-03-02 12:34:26 3016 43c COMAPI - Criteria = "(IsInstalled = 0 and
IsHidden = 0 and CategoryIDs contains
'0a487050-8b0f-4f81-b401-be4ceacd61cd')
or (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains
'8c3fcc84-7410-4a95-8b89-a166a0190486')"
2006-03-02 12:34:26 3016 43c COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-03-02 12:34:26 3016 43c COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-02 12:34:26 1376 61c Agent *************
2006-03-02 12:34:26 1376 61c Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-02 12:34:26 1376 61c Agent *********
2006-03-02 12:34:26 1376 61c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-02 12:34:26 1376 61c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://WindowsUpdate/ClientWebService/client.asmx
2006-03-02 12:34:27 1376 61c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-02 12:34:27 1376 61c Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-02 12:34:27 1376 61c PT SUS 1.0 server is detected
2006-03-02 12:34:27 1376 61c PT WARNING: Sync of Updates: 0x8024002b
2006-03-02 12:34:27 1376 61c Agent * WARNING: Failed to synchronize,
error
= 0x8024002B
2006-03-02 12:34:27 1376 61c Agent * WARNING: Exit code = 0x8024002B
2006-03-02 12:34:27 1376 61c Agent *********
2006-03-02 12:34:27 1376 61c Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-02 12:34:27 1376 61c Agent *************
2006-03-02 12:34:27 1376 61c Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-02 12:34:27 3016 4f8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-02 12:34:27 3016 4f8 COMAPI - Updates found = 0
2006-03-02 12:34:27 3016 4f8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-02 12:34:27 3016 4f8 COMAPI ---------
2006-03-02 12:34:27 3016 4f8 COMAPI -- END -- COMAPI: Search [ClientId
=
Windows Defender]
2006-03-02 12:34:27 3016 4f8 COMAPI -------------
--------------------------

Bill Sanderson said:
You probably are not having the same problem, unless you are also on a
corporate network with a SUS server involved.

Harley posted a pice of his WindowsUpdate.log file--maybe you could do
the
same?

The file name is windowsupdate.log, and it is in \windows (or \winnt or
whatever)

The file will be very large--it might be best to just attempt and update,
then open the log in notepad and cut and paste just the tail end relating
to
the failed update attempt, into a message in this thread.

--

RJ Clegg said:
Having the same problem - can't update after the update of 15/02/06.
Does
anyone have a fix yet for this as this is making Defender pretty
useless
for
me!

Richard Clegg

:

I am unable to obtain new signatures for Defender. My last ones were
downloaded as part of the normal Windows Update 2 weeks ago.

Reading another thread, someone said to check WindowsUpdate.log to see
what
was really happening. Here are the messages from the log file:

2006-03-01 10:17:24 976 a40 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-01 10:17:24 976 a40 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://cwysus00.corp.acxiom.net/ClientWebService/client.asmx
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
ShouldFileBeDownloaded
failed with 0x80190194
2006-03-01 10:17:27 976 a40 PT SUS 1.0 server is detected
2006-03-01 10:17:27 976 a40 PT WARNING: Sync of Updates: 0x8024002b
2006-03-01 10:17:27 976 a40 Agent * WARNING: Failed to synchronize,
error
= 0x8024002B
2006-03-01 10:17:27 976 a40 Agent * WARNING: Exit code = 0x8024002B
2006-03-01 10:17:27 976 a40 Agent *********
2006-03-01 10:17:27 976 a40 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-01 10:17:27 976 a40 Agent *************
2006-03-01 10:17:27 976 a40 Agent WARNING: WU client failed Searching
for
update with error 0x8024002b
2006-03-01 10:17:27 3604 1d8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI - Updates found = 0
2006-03-01 10:17:28 3604 1d8 COMAPI - WARNING: Exit code =
0x00000000,
Result code = 0x8024002B
2006-03-01 10:17:28 3604 1d8 COMAPI ---------
2006-03-01 10:17:28 3604 1d8 COMAPI -- END -- COMAPI: Search
[ClientId
=
Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI -------------
2006-03-01 10:17:28 3604 e44 COMAPI WARNING: Operation failed due to
earlier
error, hr=8024002B
2006-03-01 10:17:28 3604 e44 COMAPI FATAL: Unable to complete
asynchronous
search. (hr=8024002B)
Click to expand...
Click to expand...
Click to expand...
 
I had same problem & error code on a corporate network.

As also recommended by Bill Sanderson above, I suggest you try using Windows
Update instead of the Defender Update tool as a workaround.


Thanks for the suggestion, Bill,

JSB



RJ Clegg said:
Having the same problem - can't update after the update of 15/02/06. Does
anyone have a fix yet for this as this is making Defender pretty useless for
me!

Richard Clegg

Harley said:
I am unable to obtain new signatures for Defender. My last ones were
downloaded as part of the normal Windows Update 2 weeks ago.

Reading another thread, someone said to check WindowsUpdate.log to see what
was really happening. Here are the messages from the log file:

2006-03-01 10:17:24 976 a40 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-01 10:17:24 976 a40 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://cwysus00.corp.acxiom.net/ClientWebService/client.asmx
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-01 10:17:27 976 a40 Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-01 10:17:27 976 a40 PT SUS 1.0 server is detected
2006-03-01 10:17:27 976 a40 PT WARNING: Sync of Updates: 0x8024002b
2006-03-01 10:17:27 976 a40 Agent * WARNING: Failed to synchronize, error
= 0x8024002B
2006-03-01 10:17:27 976 a40 Agent * WARNING: Exit code = 0x8024002B
2006-03-01 10:17:27 976 a40 Agent *********
2006-03-01 10:17:27 976 a40 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-01 10:17:27 976 a40 Agent *************
2006-03-01 10:17:27 976 a40 Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-01 10:17:27 3604 1d8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI - Updates found = 0
2006-03-01 10:17:28 3604 1d8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-01 10:17:28 3604 1d8 COMAPI ---------
2006-03-01 10:17:28 3604 1d8 COMAPI -- END -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-01 10:17:28 3604 1d8 COMAPI -------------
2006-03-01 10:17:28 3604 e44 COMAPI WARNING: Operation failed due to earlier
error, hr=8024002B
2006-03-01 10:17:28 3604 e44 COMAPI FATAL: Unable to complete asynchronous
search. (hr=8024002B)
Click to expand...
Click to expand...
 
Back
Top