Bill,
I already ensured that the proxy check box is unchecked. Also, I have
all
the latest updates from Windows Update.
The following is the excerpts from the log:
2006-05-11 00:19:20 836 14a0 COMAPI -------------
2006-05-11 00:19:20 836 14a0 COMAPI -- START -- COMAPI: Search
[ClientId
=
Windows Defender]
2006-05-11 00:19:20 836 14a0 COMAPI ---------
2006-05-11 00:19:20 836 14a0 COMAPI - Online = Yes; Ignore download
priority = No
2006-05-11 00:19:20 836 14a0 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-11 00:19:20 836 14a0 COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-05-11 00:19:20 836 14a0 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-05-11 00:19:20 840 53c Agent *************
2006-05-11 00:19:20 840 53c Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-05-11 00:19:20 840 53c Agent *********
2006-05-11 00:19:22 840 53c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-05-11 00:19:22 840 53c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://windowsupdate.nus.edu.sg/ClientWebService/client.asmx
2006-05-11 00:19:23 840 53c PT Initializing simple targeting cookie,
clientId = 6b93f336-2864-4718-b406-3fe9e389dbe0, target group = , DNS
name
=
tritont43
2006-05-11 00:19:23 840 53c PT Server URL =
http://windowsupdate.nus.edu.sg/SimpleAuthWebService/SimpleAuth.asmx
2006-05-11 00:19:24 840 53c PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP
status
code = 403
2006-05-11 00:19:25 840 53c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2006-05-11 00:19:25 840 53c Misc WARNING: WinHttp:
ShouldFileBeDownloaded
failed with 0x80190193
2006-05-11 00:19:26 840 53c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2006-05-11 00:19:26 840 53c Misc WARNING: WinHttp:
ShouldFileBeDownloaded
failed with 0x80190193
2006-05-11 00:19:27 840 53c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2006-05-11 00:19:27 840 53c Misc WARNING: WinHttp:
ShouldFileBeDownloaded
failed with 0x80190193
2006-05-11 00:19:29 840 53c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2006-05-11 00:19:29 840 53c Misc WARNING: WinHttp:
ShouldFileBeDownloaded
failed with 0x80190193
2006-05-11 00:19:29 840 53c PT WARNING: Sync of Updates: 0x80244018
2006-05-11 00:19:29 840 53c Agent * WARNING: Failed to synchronize,
error
= 0x80244018
2006-05-11 00:19:29 840 53c Agent * WARNING: Exit code = 0x80244018
2006-05-11 00:19:29 840 53c Agent *********
2006-05-11 00:19:29 840 53c Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-05-11 00:19:29 840 53c Agent *************
2006-05-11 00:19:29 840 53c Agent WARNING: WU client failed Searching
for
update with error 0x80244018
2006-05-11 00:19:29 836 f78 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-05-11 00:19:29 836 f78 COMAPI - Updates found = 0
2006-05-11 00:19:29 836 f78 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x80244018
2006-05-11 00:19:29 836 f78 COMAPI ---------
2006-05-11 00:19:29 836 f78 COMAPI -- END -- COMAPI: Search
[ClientId =
Windows Defender]
2006-05-11 00:19:29 836 f78 COMAPI -------------
2006-05-11 00:19:29 836 fd8 COMAPI WARNING: Operation failed due to
earlier
error, hr=80244018
2006-05-11 00:19:29 836 fd8 COMAPI FATAL: Unable to complete
asynchronous
search. (hr=80244018)
2006-05-11 00:19:34 840 53c Report REPORT EVENT:
{9ECCE606-7C2E-4628-86D1-B5550A46E4F5} 2006-05-11
00:19:29+0800 1 148 101 {00000000-0000-0000-0000-000000000000} 0
80244018
Windows
Defender Failure Software Synchronization Error: Agent failed detecting
with
reason: 0x80244018
Please help. Thanks.
Regards,
Eric
:
A home user shouldn't have problems with update within the program.
The first thing to do is go to Windows Update, and make sure that all
updates offered in an "express" scan are accepted. I think you can
safely
ignore the WGA notification update, but some of the others are
prerequisites
to updates within Windows Update working correctly--including Windows
Installer 3.1, for example.
If you've done that, you might try checking automatically detect in
the
proxy settings in IE--or, if it is already checked, unchecking it.
I've
seen positive results from both those changes, and on the same
network!
Can you attempt an update, via Help, About, check for updates--and
then
go
do start, run,
notepad %windir%\windowsupdate.log
scroll down to the end, then work back to the start of that update
attempt--and paste just that piece back here? Perhaps there's
additional
clues in the log records.
--
Bill,
I encountered the same problem as reported by Lig Reffej but I don't
have
a
proxy configured (it's a home pc). I did some of the recommended fix
as
done
by Lig but the error still remains.
I could manually go to Windows Update to download the latest
signatures,
however. Now that my signatures is installed (manually) that is
dated 2
May,
but if I click on the "Check Now" from Defender Home screen, the
error
will
still appear.
I guess that will mean that the next time if a new signature is
available,
I
have to use the Windows Update again? Would Defender behave
similarly
like
Microsoft AntiSpyware Beta that will install the definition
independently?
Please advise, thanks.
Eric
:
I think the issue is your proxy. You should be able to update for
an
initial time by going to Windows Update--do an express scan, and
apply
all
offered updates (with the possible exception of the WGA
notification
beta,
which is labelled not for production equipment.).
As I understand it AutoUpdate won't work through your proxy. The
workaround, if the proxy admin will make the changes, is to allow
access
only to the Windows Update servers without requiring
authentication.
--
I've installed Defender today (had Beta 1 before this). When I
attempt
to
update the definitions, I receive error 0x80244018. I have no
problems
running windows update, and the Beta 1 version had no problem
updating
either.
I've read the other threads and tried
- msiexec /x AS_Sigs.msi (no change)
- Troubleshooting Windows Update v.5 Authentication Issue (no
change)
- Letting WIndows Update install the definitions (it fails only
on
the
defender update)
Running XP SP2 with all ms updates, run through a proxy that uses
uid/pwd,
but not prompted for them with defender.
Is there a fix for this?
