Windows Defender won't update the definitions

[Guest]

(Beta 2) install went fine but when I go to update the program I get a pop up
on the sys tray saying "Windows Defender was unable to complete the update:
0x8024002b."

Any thoughts?

 

[Guest]

I found DCOM errors in the system errorlog which helped me figure out it was
the autoupdater service: any listings in the app/system logs? Why they
removed the functional beta 1 from downloads before beta 2 was barely out
there is nuts! Makes you feel kinda birdshot in the face, guess they won't
release details for some time...
;>) tim

 

[Guest]

I saw another thread posted that has a possible solution. It's titled Beta 2
updates problem... talks about a corrupt download during install and tells
how to manually remove the corrupt file, which uninstall doesn't do...Hmmm
FUBAR'd again ;>) tim

 

[Guest]

Just visit the Windows Update pages, and it will have that as an update for
you to download.

 

[Guest]

I just installed the new windows defender and was getting error cannot
install updates got a little balloon telling me "Windows Defender was unable
to complete the update: 0x8024402c

I found the fix for this is very simple just use your windows update in your
start menu or http://update.microsoft.com then download defender update + its
fixed.

 

[Guest]

In one of the posts of 2/21/2006 Engel wrote the helping link !

Go to this address : http://support.microsoft.com/Default.aspx?kbid=915105
Then look under RESOLUTION and follow the steps to remove the current
signature file via START, RUN and the long file name. It takes a while and
you will see different smal windows where you have to confirm YES to delete
the file. Afterwards you can start Windows Defender and ask for the
definition update.
It takes some seconds and the yellow shield is gone ... wish you succes !

This is the 100% solution and be sure not being in the process of installing
new update. RESOLUTION-RESOLUTION-RESOLUTION

 

[Guest]

I have tried this multiple times and still get the error "0x8024002b".
Defender Version 1.1.1051.0, engin version 1.1.1185.0, signature version
1.0.0.0

Does anyone else have the problem when following the resolution steps??

 

[Guest]

The solution by "neylamj" to do a auto windows update, solved my issue. There
was a Defender update included in the Windows express update check.

 

[Bill Sanderson]

If you are on a managed network where access to autoupdate is restricted by
policy, then this KB article won't help.

Can you go to WindowsUpdate?

--

 

[Guest]

This is exactly my problem Bill, "network policy settings prevent you from
using this website to get updates for your computer"

Shoret of getting out network guys to change the rules (which they almost
certainly won't) seems like I am stuffed

 

[Bill Sanderson]

Check message from Simon Zerafa in .install (?) dated February 25th for a
possible manual method.

--

 

[Guest]

Cannot find the file that Simon refers to - there is nothing at all recent in
the SoftwareDistribution folder (at least not in the one I could find in the
Windows directory). I am about to ask our IT people if they can allow the WD
updates.

 

[Bill Sanderson]

That is the best method--If they are running WSUS, there is a new category
for the updates which the admin must enable.

--

 

[Guest]

Problem solved:
I should have read further down the group postings (naughty me) as this
problem seems to fairly widespread. The Windows Update (WU) also seems to be
intergrated with this problem. So I tried the Winodws Update from an IE and
I got a message that I needed to install a "new version" of updater. I
thought I had the latest? Anyway I did this restarted Windows and the
Windows Update refused to work. I closd the IE window and opened again and
tried the WU again and bingo it worked and there appeared the "update to
Windws Defender definitions". I installed this and Windows Defender is now
operating with the updated defintions and currently scanning my PC as I type.

Good luck to everyone else expeirencing this problem

 

[Bill Sanderson]

Some details of WindowsUpdate changed on March 1st.
Glad it is working!

--