PC Review


Reply
Thread Tools Rate Thread

Unable to complete update

 
 
=?Utf-8?B?R2FyeQ==?=
Guest
Posts: n/a
 
      2nd Mar 2006
I am trying to update signatures of WD beta 2. I receive following message
"Windows defender was unable to compete the update. 0x8024002b"

Can some one explain what is going on.
 
Reply With Quote
 
 
 
 
=?Utf-8?B?UmljaCBIdWxs?=
Guest
Posts: n/a
 
      3rd Mar 2006
I have same problem with slightly different error number.
0x8024400b

Rich Hull

"Gary" wrote:

> I am trying to update signatures of WD beta 2. I receive following message
> "Windows defender was unable to compete the update. 0x8024002b"
>
> Can some one explain what is going on.

 
Reply With Quote
 
 
 
 
=?Utf-8?B?RW5nZWw=?=
Guest
Posts: n/a
 
      4th Mar 2006
Hello Gary

No one can help if you don't provide at least a modicum of informatiºn.
What version of Windows are you using? SP?? Anti=-virus. Are you on a large,
managed network, where access to AutoUpdate is restricted? Is there a WSUS
server on the network?

WD personal are patroling the NG. With more info, they can have a solution
sooner.
Rember this is a Beta with-out support.

Eиgel
--


"Gary" wrote:

> I am trying to update signatures of WD beta 2. I receive following message
> "Windows defender was unable to compete the update. 0x8024002b"
>
> Can some one explain what is going on.

 
Reply With Quote
 
=?Utf-8?B?R2FyeQ==?=
Guest
Posts: n/a
 
      4th Mar 2006
Valid point. Operating system is XP sp2. Anti virus is VirusScan Enteprise
edition 8.0. I am on a network, but there is no restrictio to autoupdate
access.


"Engel" wrote:

> Hello Gary
>
> No one can help if you don't provide at least a modicum of informatiºn.
> What version of Windows are you using? SP?? Anti=-virus. Are you on a large,
> managed network, where access to AutoUpdate is restricted? Is there a WSUS
> server on the network?
>
> WD personal are patroling the NG. With more info, they can have a solution
> sooner.
> Rember this is a Beta with-out support.
>
> Eиgel
> --
>
>
> "Gary" wrote:
>
> > I am trying to update signatures of WD beta 2. I receive following message
> > "Windows defender was unable to compete the update. 0x8024002b"
> >
> > Can some one explain what is going on.

 
Reply With Quote
 
Bill Sanderson
Guest
Posts: n/a
 
      7th Mar 2006
Can you try an update, via Help, About, check for updates, and post back the
corresponding (by time) section of \windows\windowsupdate.log?

Here's an example from my own system--where no update is available:

---
2006-03-06 23:51:29 1936 fd4 COMAPI -------------
2006-03-06 23:51:29 1936 fd4 COMAPI -- START -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-06 23:51:29 1936 fd4 COMAPI ---------
2006-03-06 23:51:29 1936 fd4 COMAPI - Online = Yes; Ignore download
priority = No
2006-03-06 23:51:29 1936 fd4 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-06 23:51:29 1936 fd4 COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-03-06 23:51:31 1936 fd4 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-06 23:51:31 920 808 Agent *************
2006-03-06 23:51:31 920 808 Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-06 23:51:31 920 808 Agent *********
2006-03-06 23:51:50 920 808 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-06 23:51:50 920 808 PT + ServiceId =
{7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
https://update.microsoft.com/v6/Clie...ce/client.asmx
2006-03-06 23:52:19 920 808 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2006-03-06 23:52:19 920 808 PT + ServiceId =
{7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
https://update.microsoft.com/v6/Clie...ce/client.asmx
2006-03-06 23:52:23 920 808 Agent * Found 0 updates and 16 categories in
search
2006-03-06 23:52:23 920 808 Agent *********
2006-03-06 23:52:23 920 808 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-06 23:52:23 920 808 Agent *************
2006-03-06 23:52:23 1936 57c COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-06 23:52:23 1936 57c COMAPI - Updates found = 0
2006-03-06 23:52:23 1936 57c COMAPI ---------
2006-03-06 23:52:23 1936 57c COMAPI -- END -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-06 23:52:23 1936 57c COMAPI -------------
2006-03-06 23:52:28 920 40c Report REPORT EVENT:
{478E0FE5-1477-47A6-B56A-2489A5E3FECB} 2006-03-06 23:52:23-0500 1 147 101
{00000000-0000-0000-0000-000000000000} 0 0 Windows Defender Success Software
Synchronization Agent has finished detecting items.

--


 
Reply With Quote
 
=?Utf-8?B?Q2hyaXMgU3RyYXR0b24=?=
Guest
Posts: n/a
 
      8th Mar 2006
"Bill Sanderson" wrote:

> Can you try an update, via Help, About, check for updates, and post back the
> corresponding (by time) section of \windows\windowsupdate.log?
>
> Here's an example from my own system--where no update is available:
>


I am getting the same error as Gary. My system is XP SP2 with McAfee
VirusScan Enterprise 8. I am on a large corporate network and regularly use
Windows Update with no problems. Here is the appropriate section from
windowsupdate.log

2006-03-08 14:47:10 1448 96c COMAPI -------------
2006-03-08 14:47:10 1448 96c COMAPI -- START -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-08 14:47:10 1448 96c COMAPI ---------
2006-03-08 14:47:10 1448 96c COMAPI - Online = Yes; Ignore download
priority = No
2006-03-08 14:47:10 1448 96c 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-08 14:47:10 1448 96c COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-03-08 14:47:10 1448 96c COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-08 14:47:10 1124 adc Agent *************
2006-03-08 14:47:10 1124 adc Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-08 14:47:10 1124 adc Agent *********
2006-03-08 14:47:10 1124 adc PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-03-08 14:47:10 1124 adc PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://stlwolpat01/ClientWebService/client.asmx
2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80190194
2006-03-08 14:47:11 1124 adc PT SUS 1.0 server is detected
2006-03-08 14:47:11 1124 adc PT WARNING: Sync of Updates: 0x8024002b
2006-03-08 14:47:11 1124 adc Agent * WARNING: Failed to synchronize, error
= 0x8024002B
2006-03-08 14:47:11 1124 adc Agent * WARNING: Exit code = 0x8024002B
2006-03-08 14:47:11 1124 adc Agent *********
2006-03-08 14:47:11 1124 adc Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-03-08 14:47:11 1124 adc Agent *************
2006-03-08 14:47:11 1124 adc Agent WARNING: WU client failed Searching for
update with error 0x8024002b
2006-03-08 14:47:11 1448 6c8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-03-08 14:47:11 1448 6c8 COMAPI - Updates found = 0
2006-03-08 14:47:11 1448 6c8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x8024002B
2006-03-08 14:47:11 1448 6c8 COMAPI ---------
2006-03-08 14:47:11 1448 6c8 COMAPI -- END -- COMAPI: Search [ClientId =
Windows Defender]
2006-03-08 14:47:11 1448 6c8 COMAPI -------------
2006-03-08 14:47:11 1448 910 COMAPI WARNING: Operation failed due to earlier
error, hr=8024002B
2006-03-08 14:47:11 1448 910 COMAPI FATAL: Unable to complete asynchronous
search. (hr=8024002B)

 
Reply With Quote
 
=?Utf-8?B?Q2hyaXMgU3RyYXR0b24=?=
Guest
Posts: n/a
 
      8th Mar 2006


"Chris Stratton" wrote:

> "Bill Sanderson" wrote:
>
> > Can you try an update, via Help, About, check for updates, and post back the
> > corresponding (by time) section of \windows\windowsupdate.log?
> >
> > Here's an example from my own system--where no update is available:
> >

>
> I am getting the same error as Gary. My system is XP SP2 with McAfee
> VirusScan Enterprise 8. I am on a large corporate network and regularly use
> Windows Update with no problems. Here is the appropriate section from
> windowsupdate.log
>
>
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://stlwolpat01/ClientWebService/client.asmx


I noticed the server path in my log points to one of our local servers. I
searched the registry for that server name and found it in
HKLM\Software\Policies\Microsoft\Windows\Windows Update

I changed it to https://update.microsoft.com as in Bill's logfile but it
still doesn't work
 
Reply With Quote
 
Bill Sanderson
Guest
Posts: n/a
 
      8th Mar 2006
Windows Defender is designed to get signature updates via WSUS on a
corporate network. If your company is running WSUS, the WSUS administrators
will need to enable the new class of signature updates for Windows Defender.

If you can reach Microsofts Windows Update servers--via Start, Windows
Update--Defender Signature updates should be offered that way, but that will
be a manual process.

--

"Chris Stratton" <Chris (E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Bill Sanderson" wrote:
>
>> Can you try an update, via Help, About, check for updates, and post back
>> the
>> corresponding (by time) section of \windows\windowsupdate.log?
>>
>> Here's an example from my own system--where no update is available:
>>

>
> I am getting the same error as Gary. My system is XP SP2 with McAfee
> VirusScan Enterprise 8. I am on a large corporate network and regularly
> use
> Windows Update with no problems. Here is the appropriate section from
> windowsupdate.log
>
> 2006-03-08 14:47:10 1448 96c COMAPI -------------
> 2006-03-08 14:47:10 1448 96c COMAPI -- START -- COMAPI: Search [ClientId
> =
> Windows Defender]
> 2006-03-08 14:47:10 1448 96c COMAPI ---------
> 2006-03-08 14:47:10 1448 96c COMAPI - Online = Yes; Ignore download
> priority = No
> 2006-03-08 14:47:10 1448 96c 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-08 14:47:10 1448 96c COMAPI - ServiceID =
> {00000000-0000-0000-0000-000000000000}
> 2006-03-08 14:47:10 1448 96c COMAPI <<-- SUBMITTED -- COMAPI: Search
> [ClientId = Windows Defender]
> 2006-03-08 14:47:10 1124 adc Agent *************
> 2006-03-08 14:47:10 1124 adc Agent ** START ** Agent: Finding updates
> [CallerId = Windows Defender]
> 2006-03-08 14:47:10 1124 adc Agent *********
> 2006-03-08 14:47:10 1124 adc PT +++++++++++ PT: Synchronizing server
> updates +++++++++++
> 2006-03-08 14:47:10 1124 adc PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://stlwolpat01/ClientWebService/client.asmx
> 2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp:
> SendRequestToServerForFileInformation failed with 0x80190194
> 2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp: ShouldFileBeDownloaded
> failed with 0x80190194
> 2006-03-08 14:47:11 1124 adc PT SUS 1.0 server is detected
> 2006-03-08 14:47:11 1124 adc PT WARNING: Sync of Updates: 0x8024002b
> 2006-03-08 14:47:11 1124 adc Agent * WARNING: Failed to synchronize,
> error
> = 0x8024002B
> 2006-03-08 14:47:11 1124 adc Agent * WARNING: Exit code = 0x8024002B
> 2006-03-08 14:47:11 1124 adc Agent *********
> 2006-03-08 14:47:11 1124 adc Agent ** END ** Agent: Finding updates
> [CallerId = Windows Defender]
> 2006-03-08 14:47:11 1124 adc Agent *************
> 2006-03-08 14:47:11 1124 adc Agent WARNING: WU client failed Searching for
> update with error 0x8024002b
> 2006-03-08 14:47:11 1448 6c8 COMAPI >>-- RESUMED -- COMAPI: Search
> [ClientId = Windows Defender]
> 2006-03-08 14:47:11 1448 6c8 COMAPI - Updates found = 0
> 2006-03-08 14:47:11 1448 6c8 COMAPI - WARNING: Exit code = 0x00000000,
> Result code = 0x8024002B
> 2006-03-08 14:47:11 1448 6c8 COMAPI ---------
> 2006-03-08 14:47:11 1448 6c8 COMAPI -- END -- COMAPI: Search [ClientId
> =
> Windows Defender]
> 2006-03-08 14:47:11 1448 6c8 COMAPI -------------
> 2006-03-08 14:47:11 1448 910 COMAPI WARNING: Operation failed due to
> earlier
> error, hr=8024002B
> 2006-03-08 14:47:11 1448 910 COMAPI FATAL: Unable to complete asynchronous
> search. (hr=8024002B)
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Vista Complete Backup - First Complete Backup Tim Windows Vista General Discussion 6 15th Mar 2008 07:13 PM
how do I get Word to auto complete the complete date? Microsoft Word New Users 8 25th Sep 2007 02:26 PM
Automatic complete on cursor location (hover complete??) =?Utf-8?B?ZXBw?= Windows XP Basics 0 26th Feb 2006 02:27 PM
Page Not Complete In I.E. - Is Complete In Firefox and Netscape Dick Microsoft Frontpage 15 20th May 2005 05:44 AM
SP2 Download Complete or Not Complete geof Windows XP General 3 2nd Sep 2004 03:42 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 12:58 AM.