Windows Defender was unable to complete the update: 0x80072efd

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

Guest

Ok, this is really frustrating. I've already tried everything from
http://support.microsoft.com/kb/915105/.

I can get the Defender signature updates by going to windowsupdate.com, but
the Defender tool can never update itself. About ->Check for updates always
results in the above error.

Running fully patched XP SP2.

Here are some facts:
1) Windows anti-spyware was always able to update the signatures without
issue
2) windowsupdate works fine always
3) defender updates fail from my home network and work network
4) additionally, tried uninstalling Defender and re-installing, same crap

chris
 
So--is this a machine joined to a work domain?

Do a help, about, check for updates.

Then do Start, run, notepad %windir%\winlogon.log
and hit enter.

Scroll down to the end of the log file, then highlight back up to just that
most recent check for updates--copy and paste that back to this thread.

(or, save some time and effort--look for a "Server URL" line, and let's see
whether AutoUpdate is locked by group policy to a work server, which isn't
carrying Windows Defender definitions.)
 
More info from WindowsUpdate.log:

2006-05-23 13:44:36 1024 16a0 COMAPI -------------
2006-05-23 13:44:36 1024 16a0 COMAPI -- START -- COMAPI: Search [ClientId =
Windows Defender]
2006-05-23 13:44:36 1024 16a0 COMAPI ---------
2006-05-23 13:44:36 1024 16a0 COMAPI - Online = Yes; Ignore download
priority = No
2006-05-23 13:44:36 1024 16a0 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-05-23 13:44:36 1024 16a0 COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-05-23 13:44:36 1024 16a0 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-05-23 13:44:36 312 18c Agent *************
2006-05-23 13:44:36 312 18c Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-05-23 13:44:36 312 18c Agent *********
2006-05-23 13:44:40 312 18c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-05-23 13:44:40 312 18c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://10.25.108.253/ClientWebService/client.asmx
2006-05-23 13:45:16 312 18c Misc WARNING: Send failed with hr = 80072efd.
2006-05-23 13:45:16 312 18c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2006-05-23 13:45:16 312 18c PT + Last proxy send request failed with hr =
0x80072EFD, HTTP status code = 0
2006-05-23 13:45:16 312 18c PT + Caller provided credentials = No
2006-05-23 13:45:16 312 18c PT + Impersonate flags = 0
2006-05-23 13:45:16 312 18c PT + Possible authorization schemes used =
2006-05-23 13:45:16 312 18c PT WARNING: GetConfig failure, error =
0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
2006-05-23 13:45:16 312 18c PT WARNING: Sync of Updates: 0x80072efd
2006-05-23 13:45:16 312 18c Agent * WARNING: Failed to synchronize, error
= 0x80072EFD
2006-05-23 13:45:17 312 18c Agent * WARNING: Exit code = 0x80072EFD
2006-05-23 13:45:17 312 18c Agent *********
2006-05-23 13:45:17 312 18c Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-05-23 13:45:17 312 18c Agent *************
2006-05-23 13:45:17 312 18c Agent WARNING: WU client failed Searching for
update with error 0x80072efd
2006-05-23 13:45:17 1024 2e0 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-05-23 13:45:17 1024 2e0 COMAPI - Updates found = 0
2006-05-23 13:45:17 1024 2e0 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x80072EFD
2006-05-23 13:45:17 1024 2e0 COMAPI ---------
2006-05-23 13:45:17 1024 2e0 COMAPI -- END -- COMAPI: Search [ClientId =
Windows Defender]
2006-05-23 13:45:17 1024 2e0 COMAPI -------------
2006-05-23 13:45:17 1024 1ed8 COMAPI WARNING: Operation failed due to
earlier error, hr=80072EFD
2006-05-23 13:45:17 1024 1ed8 COMAPI FATAL: Unable to complete asynchronous
search. (hr=80072EFD)
2006-05-23 13:45:21 312 18c Report REPORT EVENT:
{5DF6369D-B7CB-4700-9197-95DC49B8567C} 2006-05-23 13:4
 
Thanks Bill.

My winlogon.log file is in \Windows\security\logs but hasn't been updated
since middle of last year.

Downloaded client diag tool, and here's the output:


WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect in use

Checking Connection to WSUS/SUS Server
WUServer = http://10.25.108.253
WUStatusServer = http://10.25.108.253
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS

VerifyWUServerURL() failed with hr=0x80072efd

A connection with the server could not be established


Press Enter to Complete
 
Bill,

Based on the windowsupdate log I sent you, it seems to be the case right?
Update is locked to a group server by work policy, and that server doesn't
have defender updates yet.

What a pain.

chris
 
OK - you've a domain with a WSUS server, and at present, you aren't
connected to that work network, and thus can't reach the WSUS server.

Even when you are at work and connected to the right network, it would
appear that the WSUS administrator hasn't enabled Windows Defender
definitions.

Within Windows Defender, the only update mechanism is AutoUpdate, which in
your case connects to WSUS, but a WSUS which appears not to have Defender
definitions authorized.

You can also obtain definitions via Windows Update---is that path also
locked down on your system? If so, the only alternative is hand carrying on
removable media from a machine which CAN reach Windows Update.



--
 
Yep!

--

chris said:
Bill,

Based on the windowsupdate log I sent you, it seems to be the case right?
Update is locked to a group server by work policy, and that server doesn't
have defender updates yet.

What a pain.

chris
Click to expand...
 
Yes--same story--10.25.108.253 is a private IP subnet, so this is a
corporate network. The other log was more revealing--I can't tell from this
one that it is a WSUS server, but then I haven't looked at very many of
these logs.

--

chris said:
More info from WindowsUpdate.log:

2006-05-23 13:44:36 1024 16a0 COMAPI -------------
2006-05-23 13:44:36 1024 16a0 COMAPI -- START -- COMAPI: Search [ClientId
=
Windows Defender]
2006-05-23 13:44:36 1024 16a0 COMAPI ---------
2006-05-23 13:44:36 1024 16a0 COMAPI - Online = Yes; Ignore download
priority = No
2006-05-23 13:44:36 1024 16a0 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-05-23 13:44:36 1024 16a0 COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-05-23 13:44:36 1024 16a0 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-05-23 13:44:36 312 18c Agent *************
2006-05-23 13:44:36 312 18c Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-05-23 13:44:36 312 18c Agent *********
2006-05-23 13:44:40 312 18c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-05-23 13:44:40 312 18c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://10.25.108.253/ClientWebService/client.asmx
2006-05-23 13:45:16 312 18c Misc WARNING: Send failed with hr = 80072efd.
2006-05-23 13:45:16 312 18c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth
Schemes
used : <>
2006-05-23 13:45:16 312 18c PT + Last proxy send request failed with hr
=
0x80072EFD, HTTP status code = 0
2006-05-23 13:45:16 312 18c PT + Caller provided credentials = No
2006-05-23 13:45:16 312 18c PT + Impersonate flags = 0
2006-05-23 13:45:16 312 18c PT + Possible authorization schemes used =
2006-05-23 13:45:16 312 18c PT WARNING: GetConfig failure, error =
0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code =
200
2006-05-23 13:45:16 312 18c PT WARNING: Sync of Updates: 0x80072efd
2006-05-23 13:45:16 312 18c Agent * WARNING: Failed to synchronize,
error
= 0x80072EFD
2006-05-23 13:45:17 312 18c Agent * WARNING: Exit code = 0x80072EFD
2006-05-23 13:45:17 312 18c Agent *********
2006-05-23 13:45:17 312 18c Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-05-23 13:45:17 312 18c Agent *************
2006-05-23 13:45:17 312 18c Agent WARNING: WU client failed Searching for
update with error 0x80072efd
2006-05-23 13:45:17 1024 2e0 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-05-23 13:45:17 1024 2e0 COMAPI - Updates found = 0
2006-05-23 13:45:17 1024 2e0 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x80072EFD
2006-05-23 13:45:17 1024 2e0 COMAPI ---------
2006-05-23 13:45:17 1024 2e0 COMAPI -- END -- COMAPI: Search [ClientId
=
Windows Defender]
2006-05-23 13:45:17 1024 2e0 COMAPI -------------
2006-05-23 13:45:17 1024 1ed8 COMAPI WARNING: Operation failed due to
earlier error, hr=80072EFD
2006-05-23 13:45:17 1024 1ed8 COMAPI FATAL: Unable to complete
asynchronous
search. (hr=80072EFD)
2006-05-23 13:45:21 312 18c Report REPORT EVENT:
{5DF6369D-B7CB-4700-9197-95DC49B8567C} 2006-05-23 13:4

chris said:
Ok, this is really frustrating. I've already tried everything from
http://support.microsoft.com/kb/915105/.

I can get the Defender signature updates by going to windowsupdate.com,
but
the Defender tool can never update itself. About ->Check for updates
always
results in the above error.

Running fully patched XP SP2.

Here are some facts:
1) Windows anti-spyware was always able to update the signatures without
issue
2) windowsupdate works fine always
3) defender updates fail from my home network and work network
4) additionally, tried uninstalling Defender and re-installing, same crap

chris
Click to expand...
Click to expand...
 
Back
Top