Getting error 8024002b when trying to do updates - can anyone help

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

Guest

Hi
I've downloaded, installed and updated Windows Defender at home fine. The
updates occured correctly.
However here at work, both logging in as local admin and as a regular user,
on my work PC I'm getting a error 8024002b when I try to update.
Can anyone clarify/offer a fix?
Mike
 
WinDefender is updated via Windows Update (and probably WSUS) service. I got
the error 0x8024002b baloon when I hit the manual update. IMHO, SUS doesn't
contain spam signatures.
pj
 
Hi paja - thanks for replying. Windows Defender updates fine on one of my
work PCs but not the other (which has the 0x8024002b balloon), and does work
fine on my home PC. So have you managed to do a update? Or will I only get an
update when I run Windows Update tomorrow to get the next round of Windows
patches?

Thanks
Mike
 
Manual windows update is working fine and WD is pathed to:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1185.0
Signature Version: 1.13.1272.4
 
I've seen the same exact problem on a windows 2000 advanced server sp4,
gdiplus.dll and all updates. Something about a form used was not the right
trust provider ? No clue how to fix.
 
I want to try to collect these errors--I'd love to see the precise number
and the error message. FWIW, these should be logged in the system
log--source will be something like windefend or windows defender--not sure.

--
 
that's easily done. there are several "information" events and even a
"warning" event. As follows :

The description for Event ID ( 1002 ) in Source ( WinDefend ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: %%826, 1.1.1051.0,
{8F8CFD30-592D-4D9A-81B2-9EB78816C524}, 2, %%801, 2, %%809, SERVER20,
Administrator, S-1-5-21-1202660629-854245398-1801674531-500, , .

The description for Event ID ( 1000 ) in Source ( WinDefend ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: %%826, 1.1.1051.0,
{AA060996-6818-4056-8F24-BC77EC52B7EB}, 2, %%801, 2, %%809, SERVER20,
Administrator, S-1-5-21-1202660629-854245398-1801674531-500, , .

The description for Event ID ( 5007 ) in Source ( WinDefend ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: %%826, 1.1.1051.0, N/A\Signature
Updates\EngineVersion = , HKLM\SOFTWARE\Microsoft\Windows Defender\Signature
Updates\EngineVersion = 1.1.1185.0, , .

The description for Event ID ( 1001 ) in Source ( WinDefend ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: %%826, 1.1.1051.0,
{AA060996-6818-4056-8F24-BC77EC52B7EB}, 2, %%801, 2, %%809, SERVER20,
Administrator, S-1-5-21-1202660629-854245398-1801674531-500, 0, 01, 42, , .
 
Thanks--I haven't even gotten around to looking at the event logs--I'll do
that when I get a breather--which won't be before Saturday.

I've now found, on different machines, that either checking, or
unchecking--the "automatically detect" checkbox for proxy servers may affect
an update issue--either that or there's coincidence involved, which is
equally possible--so far I've got one of each--machines on the same network.

--
 
I tried that, checked and unchecked, made no difference. I've seen this
problem on only one PC of 4 I've tried. the two XP SP2s had no problems,
neither did the other Windows 2000 Server SP4 + Rollup update. But this
advanced Server first didn't have GDIPLUS.DLL in the system32 dir and
wouldn't install, and then when it would install, it exhibits this update,
even after repeated uninstall, install attempts. The server is otherwise
functioning normally.
 
One user who had a machine that did not update reported that uninstalling,
and then reinstalling corrected it. I'd think this might be worth trying
with those errors. I haven't looked at the logs yet, myself, though--but I
don't think they'll be spewing stuff like the old errors.log file.

--
 
I solved the problem.

Go the the windows defender folder in program files, and manually execute
the AS_Sigs.msi package, which wasn't installed. I think on some machines
something is preventing this package from being installed with the main
install. Anyway, installing it corrected the problem for me on my machine.
 
Great--I see that has worked for a number of folks--but I don't have a feel
for who it works for and when it is appropriate to recommend.

--
 
Bill, I have tried all the solutions posted; updated windows, erased
signuture file, run AS_sigs.msi manually... Nothing has worked.. Any more
ideas?
 
Ken--the servers had eaten your message for a week or so, it appears. Are
you still stuck?

--
 
Back
Top