Error in WDB2 When Updating

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

Guest

Looks like microsofts classes aren't installing properly... I assume this is
a mistake in a DLL somewhere, when I click update i get a little balloon from
the castle icon in the start bar saying,

"Windows Defender was unable to complete the update:
0x80040154. Class not registered"

I will try re-registering all of the WD DLL's, but if anyone has a fix
please post it...
-Leif902
 
I'd try a repair or update install--or you could try re-registering by hand.
I haven't seen this one on any XP or Windows 2000 pro or server machines.
 
yah i'm going to reregister by hand later... i was just hoping someone would
know exactly which dll i needed to reregister, just to make it easy :D Thanks
anyway -Leif902
 
Yours is the only post I've seen with this error, but I haven't read near
all of them (yet.)

--
 
lol wierd... but my computer is ancient, sometimes i think it's grown a brain
just because it does things i didn't think were possible :D... lol i
reinstalled twice and uninstalled and reinstalled and it didn't fix it... i
guess i'm just going to have to get off my but and go through and
reregister... i think i'll make a shell so i can just click on some dlls and
hit register :) That would be nice... -Leif902
 
Okay so i reregistered all the DLL's by hand and still get the same
message... any new ideas?
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;277964

I don't think you'll learn much from that article.

Have you checked the system event log entries to see whether this error is
logged? I wonder if the precise entity involved might be named.

I still think that the repair or update options in control panel add or
remove programs may help--start, control panel, add or remove programs

Windows Defender. Choose Change, then Update, or, choose the support info
link, and then choose repair. Your choice--I've no idea whether there's any
actual difference in functionality.

--
 
yah i did the update method... didn't work...

I'll try looking in the logs (didn't know WD kept logs) and see what it
says...

Thanx for the article btw, didn't learn alot from it but it was intersting
 
oh yah, i see, system event log entries not WD log entries :) nope nothing in
their relating to this...
-Leif902
 
Bill said:
Have you checked the system event log entries to see whether this error is
logged? I wonder if the precise entity involved might be named.
.............................
Bill

What are the steps to check the System Event Log? [I am using Win XP
SP2 Home]

Texas Handly
 
click start -> run -> and in run type "eventvwr.msc" w/o the quotes of course
:)
-Leif902

Texas Handly said:
Bill said:
Have you checked the system event log entries to see whether this error is
logged? I wonder if the precise entity involved might be named.
.............................
Bill

What are the steps to check the System Event Log? [I am using Win XP
SP2 Home]

Texas Handly
 
Leif902's given one method--here's another:

Right-click My Computer, and choose Manage. In the left column, click on
the + next to Event Viewer, then click on the System event log. You may
well want to click View, Filter, and choose "WinDefend" as the event source.

--

Texas Handly said:
Bill said:
Have you checked the system event log entries to see whether this error
is logged? I wonder if the precise entity involved might be named.
.............................
Bill

What are the steps to check the System Event Log? [I am using Win XP SP2
Home]

Texas Handly
 
lol okay anyway back on track, nothing in the logs about it and today windows
update gave me some updated definitions... (2 actually, one older one and one
newer one :?)... anyway so i can update that way, it's not a big problem
anymore... i just wish i knew why it was doing this
-Leif902

Bill Sanderson said:
Leif902's given one method--here's another:

Right-click My Computer, and choose Manage. In the left column, click on
the + next to Event Viewer, then click on the System event log. You may
well want to click View, Filter, and choose "WinDefend" as the event source.

--

Texas Handly said:
Bill said:
Have you checked the system event log entries to see whether this error
is logged? I wonder if the precise entity involved might be named.
.............................
Bill

What are the steps to check the System Event Log? [I am using Win XP SP2
Home]

Texas Handly
 
Do you have AutomaticUpdates enabled? If so, they should come in that way.
Some have reported that once updated via WindowsUpdate, further updates
worked normally.

--

Leif902 said:
lol okay anyway back on track, nothing in the logs about it and today
windows
update gave me some updated definitions... (2 actually, one older one and
one
newer one :?)... anyway so i can update that way, it's not a big problem
anymore... i just wish i knew why it was doing this
-Leif902

Bill Sanderson said:
Leif902's given one method--here's another:

Right-click My Computer, and choose Manage. In the left column, click on
the + next to Event Viewer, then click on the System event log. You may
well want to click View, Filter, and choose "WinDefend" as the event
source.

--

Texas Handly said:
Bill Sanderson wrote:


Have you checked the system event log entries to see whether this
error
is logged? I wonder if the precise entity involved might be named.
.............................


Bill

What are the steps to check the System Event Log? [I am using Win XP
SP2
Home]

Texas Handly
 
yup i got them from auto update :) -Leif902

Bill Sanderson said:
Do you have AutomaticUpdates enabled? If so, they should come in that way.
Some have reported that once updated via WindowsUpdate, further updates
worked normally.

--

Leif902 said:
lol okay anyway back on track, nothing in the logs about it and today
windows
update gave me some updated definitions... (2 actually, one older one and
one
newer one :?)... anyway so i can update that way, it's not a big problem
anymore... i just wish i knew why it was doing this
-Leif902

Bill Sanderson said:
Leif902's given one method--here's another:

Right-click My Computer, and choose Manage. In the left column, click on
the + next to Event Viewer, then click on the System event log. You may
well want to click View, Filter, and choose "WinDefend" as the event
source.

--

Bill Sanderson wrote:


Have you checked the system event log entries to see whether this
error
is logged? I wonder if the precise entity involved might be named.
.............................


Bill

What are the steps to check the System Event Log? [I am using Win XP
SP2
Home]

Texas Handly
 
Maybe time to start comparing notes, except I'm not sure what to suggest to
compare.

--
 
Back
Top