Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error 0x8024D007

41 views
Skip to first unread message

Bruce Kovacs

unread,
Nov 13, 2009, 12:01:02 PM11/13/09
to

I am running Windows XP Professional SP 3.

I am getting Error 0x8024D007 when attempting to use Microsoft Update. I
have already reviewed a number of the questions posted here and have done the
following:

Article ID: 956701 - Performed Method 1: Register the Windows Update files

Article ID: 943144 - Performed Method 1: Register the Wups2.dll file in
Windows

Article ID: 949104 - Downloaded file windowsupdateagent30-x86.exe

When I run windowsupdateagent30-x86.exe, I still get error 0x8024D007. Any
other suggestions?

MowGreen

unread,
Nov 13, 2009, 7:24:30 PM11/13/09
to
Bruce,


0x8024D007 WU_E_SETUP_REGISTRATION_FAILED
Windows Update Agent could not be updated because regsvr32.exe returned
an error.

Go here and click the Fixit button:

How do I reset Windows Update components?
http://support.microsoft.com/kb/971058

When you're prompted to run or save the file, choose *save*.
Once MicrosoftFixit50202.msi finishes downloading, close all open
programs and browsers.

With the system connected to the internet, run MicrosoftFixit50202.msi
and choose the Aggressive mode. All of the operations it carries out are
listed in the KB article under " Let me fix it myself " heading.
The regsvr32 error referred to in the error explanation could be caused
by improper Permissions, which will be reset to their Default settings
when the Fixit is run, amongst other possible causes. One of those
causes may be due to malware. Please note the word may.

When the Fixit is done running you should be prompted to restart the
system. Do so even if not prompted to.

Did that resolve the error ?


MowGreen
===============
*-343-* FDNY
Never Forgotten
===============

banthecheck.com
"Security updates should *never* have *non-security content* prechecked"

Bruce Kovacs

unread,
Nov 17, 2009, 12:24:03 AM11/17/09
to
No, I am sorry to say that this suggestion did not fix the problem.
Everything appeared to run OK, and I restarted the computer. I went to
Microsoft Update and was again presented with the "Update Windows" button. I
clicked that and the computer went through the Downloading, Copying, and
Registering series. Just after “Registering 100%” appeared, I again received
the Error 0x8024D007 notification.

"MowGreen" wrote:

> .
>

Bruce Kovacs

unread,
Nov 17, 2009, 12:34:36 AM11/17/09
to
No, I am sorry to say that this suggestion did not fix the problem.
Everything appeared to run OK, and I restarted the computer. I went to
Microsoft Update and was again presented with the "Update Windows" button. I
clicked that and the computer went through the Downloading, Copying, and
Registering series. Just after “Registering 100%” appeared, I again received
the Error 0x8024D007 notification.


"MowGreen" wrote:

> .
>

Bruce Kovacs

unread,
Nov 17, 2009, 12:54:01 AM11/17/09
to

No, I am sorry to say that this suggestion did not fix the problem.
Everything appeared to run OK, and I restarted the computer. I went to
Microsoft Update and was again presented with the "Update Windows" button. I
clicked that and the computer went through the Downloading, Copying, and
Registering series. Just after “Registering 100%” appeared, I again received
the Error 0x8024D007 notification.


"MowGreen" wrote:

> .
>

PA Bear [MS MVP]

unread,
Nov 17, 2009, 2:23:44 AM11/17/09
to
[We saw your first two replies]

Bruce Kovacs

unread,
Nov 17, 2009, 7:56:06 AM11/17/09
to
Sorry about the multiple posts, but yesterday each time I hit the Post
button, I got an error message saying the site was temporarily unavailable.
I thought the message did not go through.

> .
>

MowGreen

unread,
Nov 17, 2009, 12:23:53 PM11/17/09
to
I'm not sure which post to reply to. Maybe one of these days MS will fix
the NNTP to web-based forums to social.answer forums "bridge" ?

Suggest you clean boot the system to rule out interference from 3rd
party software (antivirus/security suite/firewall/etc):

How to configure Windows XP to start in a "clean boot" state
http://support.microsoft.com/kb/310353

If you feel comfortable doing the steps yourself, do
'Method 2: Manually starting XP with a clean boot (advanced user only)'.
Otherwise, use the Guided Help.
Once the system is in the clean boot state, ensure that the native XP
firewall is Enabled and revisit Microsoft Update to see if the system
can opt into it now.
If it can, then the installed security software was causing the regsvr32
issue.

0 new messages