Error number: 0x8024D007

[Jeff LeBlanc]

Hi All,

I just updated a Windows Server 2003 (RTM) system to the new Microsoft
Update and now get an error "Error number: 0x8024D007". I saw another thread
on here where others have run into this with no resolution. Can someone from
Microsoft provide steps to resolve this? I searched the Microsoft site and
Google, also tried clearing temp Internet files and Cookies (just incase) but
no luck.

Thanks,
-Jeff

[Jeff LeBlanc]

More info from the WindowsUpdate.log file (from where the errors start)

2005-06-14 13:17:09 1552 434 Setup Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
2005-06-14 13:17:09 1552 434 Setup FATAL: Self registration of
C:\WINDOWS\system32\wuaueng.dll failed, error = 0x8024D007
2005-06-14 13:17:09 1552 434 Setup Completed registration operations for
section wuaueng_WebSetup: status 0x8024d007
2005-06-14 13:17:09 1552 434 Setup WARNING: Setup failed while processing
registry operations, error = 0x8024D007. Rolling back changes.
2005-06-14 13:17:09 1552 434 Setup Rollback: Successfully copied
C:\WINDOWS\system32\cdm.dll.wusetup.623437.bak back to
C:\WINDOWS\system32\cdm.dll
2005-06-14 13:17:09 1552 434 Setup Rollback: Successfully copied
C:\WINDOWS\system32\iuengine.dll.wusetup.623625.bak back to
C:\WINDOWS\system32\iuengine.dll
2005-06-14 13:17:09 1552 434 Setup Rollback: Successfully copied
C:\WINDOWS\system32\wuauclt.exe.wusetup.623703.bak back to
C:\WINDOWS\system32\wuauclt.exe
2005-06-14 13:17:09 1552 434 Setup Rollback: Successfully copied
C:\WINDOWS\system32\wuaueng.dll.wusetup.623843.bak back to
C:\WINDOWS\system32\wuaueng.dll
2005-06-14 13:17:09 1552 434 Setup Rollback: Successfully copied
C:\WINDOWS\help\wuauhelp.chm.wusetup.623937.bak back to
C:\WINDOWS\help\wuauhelp.chm
2005-06-14 13:17:09 1552 434 Setup Rollback: Successfully copied
C:\WINDOWS\INF\wuau.adm.wusetup.623968.bak back to C:\WINDOWS\INF\wuau.adm
2005-06-14 13:17:09 1552 434 Setup FATAL: Warning: Failed to restart
wuauserv service: 0x80070424
2005-06-14 13:17:09 1552 434 Setup * WARNING: Exit code = 0x8024D007
2005-06-14 13:17:09 1552 434 Setup *********
2005-06-14 13:17:09 1552 434 Setup ** END ** Setup: Installing client
binaries
2005-06-14 13:17:09 1552 434 Setup *************
2005-06-14 13:17:09 1552 434 Setup FATAL: InstallUpdatedBinaries failed with
error 0x8024d007
2005-06-14 13:17:09 1552 434 WUWeb FATAL: InstallUpdatedBinaries failed with
error:0x8024d007
2005-06-14 13:17:09 1552 434 WUWeb FATAL: UpdateClientWorker failed: error
0x8024d007

I was able to register the wuaueng.dll manually without any problems...

[Jeff LeBlanc]

Ok, I know I'm talking to myself here but maybe it will help someone else in
the future so here goes...

I didn't get to the root cause, but my system seems to be in working order
now.

When I first tried going to WindowsUpdate on this Win2K3 system I was
getting the Time error described in another thread at
http://support.microsoft.com/newsgroups/newsReader.aspx?dg=microsoft.public.windowsupdate&mid=2cdb89ef-21b9-469c-9cff-3252f78c84b6.
Rather than troubleshooting that error I decided to go to the new Microsoft
Update site and upgrade to the latest software instead. That's where the fun
began and I started getting the errors I posted earlier.

From there I tried removing the Program Files\Windows update folder and also
the Windows\Sftware Distribution\WebSetup and WuReDir folders to no avail.
The system would still keep re-directing to the MU v6 site and erroring at
0x8024D007. Looking in the WindowsUpdate.log it appeared to be a problem
registering wuaueng.dll but I was able to run the same command line manually
without any problems. From the error it looked to be a possible Registry
permissions error so I tried REGMON but wasn't able to narrow down any
specific key with a problem.

***!!! FOLLOW THESE STEPS AT YOUR OWN RISK !!!***

Finally, since this wasn't a production system I just removed all of the
WU*.* files out of Windows\System32 and then went back to WindowsUpdate and
it loaded up at v4 rather than re-directing me to the v6 site. Now I was
back to the Time error from the thread linked above. Following the
resolution in that thread (turning off the "Check for server certificate
revocation) I was able to download all of the latest updates for my system
and in the process the WindowsUpdate engine got successfully upgraded to v6.
After all of the updates were applied I then went back to the new Microsoft
Update site and everything is working as you'd expect it to even with the
"Check for server certificate revocation" turned on.

So there's my fun troubleshooting for the day. Hope it helps someone else
and don't forget to backup any files before you delete them!

-Jeff

[felixkat]

Hi All,

Though I would add my RESOLUTION to this issue. Using Google only brings up
a few English sites sites with this error so there may still be people out
there struggling. Obviously this may not work for you but I guess when your
pulling your hair out anything is worth a go.

To start with I wa shaving this problem with Windows 2000 at Service Pack 4.
This may also work still with other versions including XP.

I tried all other suggestions on this page kindly donated from others. This
was the removal of all files beggining with wu*.* in c:\windows\system32 or
in my case on windows 2000 c:\winnt\system32. This unfortuently didn't work.
There was also mention about removing the tick in the Internet Options,
Advanced, Security and then server revocation. (I can't find the link at the
mo but I'm sure a google search will let you find it).

I'm telling you what I tried before I finally resolved the issue in case
this contributes to the resolution. I would recommend trying the following
and if it doesn't resolve the issue then try the others suggestions and then
mine again.

Okay it's very very simple. I checked the logs for windows update and it
seemed to have a problem registering a DLL file in the c:\winnt\system32
directory. (This may be c:\windows\system32 on WinXP). I loaded up a DOS box,
(cmd box), and typed regsvr32 and then the dll file. Nothing happened. I
then typed regsvr32 /? which should bring up the options. Again nothing
happened. I suspected that the regsvr32.exe file may be corrupted.

I downloaded a file called regsvr32a.exe from here:-

http://support.microsoft.com/default.aspx?scid=kb;en-us;267279

This is a self extractable file. I used my prefered method of downloading
the file into an empty directory. Running the file and then manually copying
the new regsvr32.exe into my SYSTEM32 directory. I then confirmed that I
wanted to overwrite the existing version. I then rebooted just to keep
things clean and hey presto everything worked again.

I hope this is of some help to somebody. I know I've probably done an
overkill on the details but hopefully this will help people of all levels.

Regards

felixkat

[Dean]

CONFIRMED THIS FIX WORKS

[YAD]

You can also try updating to the latest service pack for the system. Using a
w2k machine w/ sp3 that kept giving me this error after trying everything
that was listed here nothing worked but once the sp was installed it now
works like a charm. go figure.