v6 fails with error 0x8007041D

I'm well into my second day of trying to get windows update to run. I've
tried all the various solutions offered here and on google's group.

I'm running XP SP2. This problem occurred under SP1 as well. I'm not
running the AV product that MS sites as a problem.

One of my problems is that the Automatic Updates Service will not start it
returns:

"Could not start the Automatic Updates service on Local Computer
Error 0x8024d007 : 0x8024d007 "

Following is my WindowsUpdate.log:

*************
2005-10-13 18:45:34 1040 6a0 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0400) ===========
2005-10-13 18:45:34 1040 6a0 Misc = Process: C:\WINDOWS\System32\svchost.exe
2005-10-13 18:45:34 1040 6a0 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2005-10-13 18:45:34 1040 6a0 Service *************
2005-10-13 18:45:34 1040 6a0 Service ** START ** Service: Service startup
2005-10-13 18:45:34 1040 6a0 Service *********
2005-10-13 18:45:34 1040 6a0 Setup Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s
"C:\WINDOWS\System32\SoftwareDistribution\Setup\Se rviceStartup\wuapi.dll\5.8.0.2469\wuapi.dll"
2005-10-13 18:45:34 1040 6a0 Setup Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s
"C:\WINDOWS\system32\SoftwareDistribution\Setup\Se rviceStartup\wups.dll\5.8.0.2469\wups.dll"
2005-10-13 18:45:34 1040 6a0 Setup FATAL: Self registration of
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wups.dll\5.8.0.2469\wups.dll failed, error = 0x8024D007
2005-10-13 18:45:34 1040 6a0 Setup FATAL: Failed to register
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wups.dll\5.8.0.2469\wups.dll in cache location: error 0x8024d007
2005-10-13 18:45:34 1040 6a0 Setup FATAL: ProcessDelayedCopies failed:
0x8024d007
2005-10-13 18:45:34 1040 6a0 Agent FATAL: Failed to fix up registration at
service startup: 0x8024d007
2005-10-13 18:45:34 1040 6a0 Service *********
2005-10-13 18:45:34 1040 6a0 Service ** END ** Service: Service exit
[Exit code = 0x8024d007]
2005-10-13 18:45:34 1040 6a0 Service *************
2005-10-13 18:51:05 1040 5f4 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0400) ===========
2005-10-13 18:51:05 1040 5f4 Misc = Process: C:\WINDOWS\System32\svchost.exe
2005-10-13 18:51:05 1040 5f4 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2005-10-13 18:51:05 1040 5f4 Service *************
2005-10-13 18:51:05 1040 5f4 Service ** START ** Service: Service startup
2005-10-13 18:51:05 1040 5f4 Service *********
2005-10-13 18:51:05 1040 5f4 Setup Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s
"C:\WINDOWS\System32\SoftwareDistribution\Setup\Se rviceStartup\wuapi.dll\5.8.0.2469\wuapi.dll"
2005-10-13 18:51:06 1040 5f4 Setup Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s
"C:\WINDOWS\system32\SoftwareDistribution\Setup\Se rviceStartup\wups.dll\5.8.0.2469\wups.dll"
2005-10-13 18:51:06 1040 5f4 Setup FATAL: Self registration of
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wups.dll\5.8.0.2469\wups.dll failed, error = 0x8024D007
2005-10-13 18:51:06 1040 5f4 Setup FATAL: Failed to register
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wups.dll\5.8.0.2469\wups.dll in cache location: error 0x8024d007
2005-10-13 18:51:06 1040 5f4 Setup FATAL: ProcessDelayedCopies failed:
0x8024d007
2005-10-13 18:51:06 1040 5f4 Agent FATAL: Failed to fix up registration at
service startup: 0x8024d007
2005-10-13 18:51:06 1040 5f4 Service *********
2005-10-13 18:51:06 1040 5f4 Service ** END ** Service: Service exit
[Exit code = 0x8024d007]
2005-10-13 18:51:06 1040 5f4 Service *************


Let me know what you think...

"PB" <> wrote in message
news:13857FDE-1470-444F-9191-
....
> 2005-10-13 18:45:34 1040 6a0 Setup FATAL: Self registration of
> C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wups.dll\5.8.0.2469\wups.dll failed, error = 0x8024D007


What happens if you try performing an equivalent regsvr32 command
(without the /s switch) yourself manually?

E.g. open a cmd window and enter:

cd /d %SystemRoot%\System32\SoftwareDistribution\Setup\S erviceStartup\wups.dll\5.8.0.2469

and then

regsvr32 wups.dll

I suggest you do that in a command window and don't use the /s
switch the log shows. That would just suppress any diagnostics
you might be generating by this procedure.


In the event that you got an error message from the regsvr32 command
you could get more information about the problem by using
DependencyWalker's Profiler. (You can find examples of others'
use of that tool by searching this newsgroup with those keywords.)


Good luck

Robert Aldwinckle
---