Windows Defender will not update definitions

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

Guest

Error message is as follows:

Windows Defender was unable to complete the update: 0x8024402c.

Does anyone have any ideas on how to fix?

Regards,
 
What build of Windows Defender, and what version of Windows?

Is the "background intelligent transfer service" started?
 
I've now seen a similar message on one box.

I don't have an answer for this one yet, I'm afraid.
 
Hi Bill,

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1185.0
Signature Version: 1.0.0.0

Windows XP SP2 is the OS

Thank you!
Alan
 
You get credit for the first official bug report, maybe--have to check the
time on Bob Vanderveen's post in .announcements asking about the
prerequisite for Windows 2000 installs....
 
Since the build got out of the gate a little early, I'm wondering if new
defs have truly been posted. Seeing the same (non) behavior here also.

Ron Chamberlin
MS-MVP
 
Most of the machines I'm working with are picking up an initial update just
fine--I've only had the one failure. I've been doing mostly Windows 2000
servers, so far, though.

For Windows 2000, you need a GDI+ piece--I posted the link to Bob Vanderveen
in .announcements.

It has to go in \winnt\system32, it turns out.

--
 
I get the same problem.
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1185.0
Signature Version: 1.0.0.0

Windows XP SP2
Could it be because I use a proxy server?

Gareth Owen
 
I also get the same problem.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1185.0
Signature Version: 1.0.0.0
OS: Windows XP with SP2
 
I get a similar error, but a different error code: 0x80240016

Windows Defender was unable to complete the update:
0x80240016. The device does not recognize the command.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1185.0
Signature Version: 1.0.0.0

Windows XP MCE 2005 XP2 Fully Updated
 
The precise translation of that error is:

Winhttp SendRequest/ReceiveResponse failed with 0x2ee7 error. Either the
proxy server or target server name can not be resolved. Corresponding to
ERROR_WINHTTP_NAME_NOT_RESOLVED. Stop/Restart service or reboot the machine
if you see this error frequently.

Invariably there's a proxy issue, or ISA is getting in the way, or a
firewall issue.
 
I'm getting similar problems, but only on one of 2 my work PCs. Plus it's
working fine on my home PC.

XP SP2 Pro fully updated.

Trying to update Windows Defender gives:

Windows Defender was unable to complete the update: 0x8024002b.
 
Sweet!

I look forward to getting it fixed! Maybe they just haven't released the
updates for the new beta 2 version as of yet.

Thanks,
Alan
 
I'm also having similar porblems updating. The error I get is "0x800b0003 -
The form specified for the subject is not one supported or known by the
specified trust provider."

XP Pro SP2

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1185.0
Signature Version: 1.0.0.0
 
If AutoUpdate makes it through your proxy, WD definitions should. I think
the cause is elsewhere, but I don't have any clues yet.
--
 
Thanks--the one machine I've seen this on I won't be able to reach until
about 3:30 US Eastern standard time today. It is a laptop on a wireless lan
with a linksys router to Verizon DSL--shouldn't be any proxy involved, but I
will check the proxy settings.

It may be worth setting IE's connection settings to "automatically detect"
to see whether that clears this error.

--
 
Wow--that's a good one...I'm tempted to recommend a update or repair
install--via add or remove programs...

--
 
Back
Top