Error 0x8024402c

Installed WD this week and it told me my defs were 30 days old. Clicking the
update button on the home screen as well as going through help options,
about, check for updates had the same effect: dialog bubble from the tray
icon stating "WD connecting to the internet to check for updates" and then
"WD unabel to complete the update: 0x8024402c". I have followed the advice
on this message board to remove the signatures via cmd prompt, also tried
removing WD, then deleting signatures, then reinstalling, all to no avail.
Yellow warning shield remains in tray, updates still old (31 days now). Any
suggestions?

I am getting the same message on two different machine both WinXP Pro SP2

"Ben Ambrosino" wrote:

> Installed WD this week and it told me my defs were 30 days old. Clicking the
> update button on the home screen as well as going through help options,
> about, check for updates had the same effect: dialog bubble from the tray
> icon stating "WD connecting to the internet to check for updates" and then
> "WD unabel to complete the update: 0x8024402c". I have followed the advice
> on this message board to remove the signatures via cmd prompt, also tried
> removing WD, then deleting signatures, then reinstalling, all to no avail.
> Yellow warning shield remains in tray, updates still old (31 days now). Any
> suggestions?

Running winddows update updated defender and all is well now??? The update
process from defender is longer available so i don't know if this is fixed or
the windows just updated it so defender doesn't need to.

"Doug Salah" wrote:

> I am getting the same message on two different machine both WinXP Pro SP2
>
> "Ben Ambrosino" wrote:
>
> > Installed WD this week and it told me my defs were 30 days old. Clicking the
> > update button on the home screen as well as going through help options,
> > about, check for updates had the same effect: dialog bubble from the tray
> > icon stating "WD connecting to the internet to check for updates" and then
> > "WD unabel to complete the update: 0x8024402c". I have followed the advice
> > on this message board to remove the signatures via cmd prompt, also tried
> > removing WD, then deleting signatures, then reinstalling, all to no avail.
> > Yellow warning shield remains in tray, updates still old (31 days now). Any
> > suggestions?

I took this advice and it seems to have fixed it. Now the question is why XP
Pro is not automatically updating like it is set to. I will have to start a
new thread in the OS section

"Doug Salah" wrote:

> Running winddows update updated defender and all is well now??? The update
> process from defender is longer available so i don't know if this is fixed or
> the windows just updated it so defender doesn't need to.
>
> "Doug Salah" wrote:
>
> > I am getting the same message on two different machine both WinXP Pro SP2
> >
> > "Ben Ambrosino" wrote:
> >
> > > Installed WD this week and it told me my defs were 30 days old. Clicking the
> > > update button on the home screen as well as going through help options,
> > > about, check for updates had the same effect: dialog bubble from the tray
> > > icon stating "WD connecting to the internet to check for updates" and then
> > > "WD unabel to complete the update: 0x8024402c". I have followed the advice
> > > on this message board to remove the signatures via cmd prompt, also tried
> > > removing WD, then deleting signatures, then reinstalling, all to no avail.
> > > Yellow warning shield remains in tray, updates still old (31 days now). Any
> > > suggestions?

I'm having exactly the same error and not sitting behind ISA. At work, sit
behind ISA 2004 but at home am behind normal wireless router logged on as a
local administrator. Proxy settings are disabled at home. Other PC at home
works fine and downloads fine. Microsoft update does not include definition
files so the defender icon permanently has a yellow exclamation mark by it.
I'm very surprised that there is no way of reporting this to MS direct as
this is a BETA version and they need this sort of feedback.

"Ben Ambrosino" wrote:

> I took this advice and it seems to have fixed it. Now the question is why XP
> Pro is not automatically updating like it is set to. I will have to start a
> new thread in the OS section
>
> "Doug Salah" wrote:
>
> > Running winddows update updated defender and all is well now??? The update
> > process from defender is longer available so i don't know if this is fixed or
> > the windows just updated it so defender doesn't need to.
> >
> > "Doug Salah" wrote:
> >
> > > I am getting the same message on two different machine both WinXP Pro SP2
> > >
> > > "Ben Ambrosino" wrote:
> > >
> > > > Installed WD this week and it told me my defs were 30 days old. Clicking the
> > > > update button on the home screen as well as going through help options,
> > > > about, check for updates had the same effect: dialog bubble from the tray
> > > > icon stating "WD connecting to the internet to check for updates" and then
> > > > "WD unabel to complete the update: 0x8024402c". I have followed the advice
> > > > on this message board to remove the signatures via cmd prompt, also tried
> > > > removing WD, then deleting signatures, then reinstalling, all to no avail.
> > > > Yellow warning shield remains in tray, updates still old (31 days now). Any
> > > > suggestions?

You might be using a networked "My Documents" folder - I had this same issue
until I guessed that it was trying to write to that folder, which I was not
connected to (Adobe products used to have the same issue) - after I mapped
that folder, everything updated nicely.

"Paul" wrote:

> I'm having exactly the same error and not sitting behind ISA. At work, sit
> behind ISA 2004 but at home am behind normal wireless router logged on as a
> local administrator. Proxy settings are disabled at home. Other PC at home
> works fine and downloads fine. Microsoft update does not include definition
> files so the defender icon permanently has a yellow exclamation mark by it.
> I'm very surprised that there is no way of reporting this to MS direct as
> this is a BETA version and they need this sort of feedback.
>
> "Ben Ambrosino" wrote:
>
> > I took this advice and it seems to have fixed it. Now the question is why XP
> > Pro is not automatically updating like it is set to. I will have to start a
> > new thread in the OS section
> >
> > "Doug Salah" wrote:
> >
> > > Running winddows update updated defender and all is well now??? The update
> > > process from defender is longer available so i don't know if this is fixed or
> > > the windows just updated it so defender doesn't need to.
> > >
> > > "Doug Salah" wrote:
> > >
> > > > I am getting the same message on two different machine both WinXP Pro SP2
> > > >
> > > > "Ben Ambrosino" wrote:
> > > >
> > > > > Installed WD this week and it told me my defs were 30 days old. Clicking the
> > > > > update button on the home screen as well as going through help options,
> > > > > about, check for updates had the same effect: dialog bubble from the tray
> > > > > icon stating "WD connecting to the internet to check for updates" and then
> > > > > "WD unabel to complete the update: 0x8024402c". I have followed the advice
> > > > > on this message board to remove the signatures via cmd prompt, also tried
> > > > > removing WD, then deleting signatures, then reinstalling, all to no avail.
> > > > > Yellow warning shield remains in tray, updates still old (31 days now). Any
> > > > > suggestions?

Yes, I have the same, only my updates were first 68 days old and now 72 ( I
only installed WD 5 days ago for the first time, removed it and installed it
again yesterday)!! And WD says "Unable to complete update 0x8024400a, so
slightly different from other "complainers". Microsoft : HELP !

"Ben Ambrosino" wrote:


> Installed WD this week and it told me my defs were 30 days old. Clicking the
> update button on the home screen as well as going through help options,
> about, check for updates had the same effect: dialog bubble from the tray
> icon stating "WD connecting to the internet to check for updates" and then
> "WD unabel to complete the update: 0x8024402c". I have followed the advice
> on this message board to remove the signatures via cmd prompt, also tried
> removing WD, then deleting signatures, then reinstalling, all to no avail.
> Yellow warning shield remains in tray, updates still old (31 days now). Any
> suggestions?