Windows Automatic Updates Update Error 126 the module could not be found

When I try to start the service I get Error 126 cannot find the module.

 

I have  this problem. Now, Error 126 says it can't find the module. THAT is the problem.

 

I've run the 'fixits' and they detect no problems.

 

I've checked the paths in Services.msc

 

They are normal.

 

SO, any clues on this? I don't think I have any or HAD any viruses, since there's been no other problems but this.

 

But I cannot start the service..........what would stop a service from being unable to start in the first place. It has no depencencies.

 

The files exist in system32. The image path for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv is: %SystemRoot%\system32\svchost.exe -k netsvcs

 

Also, BITS has no problem starting..........fwiw

 

Anybody that has a meaningful answer, or wants me to check some values in the registry, or something else, pls respond

 

Thank YOU!!!

 

PS. This is an XP Pro system.........and fwiw, 'Reinstall Windows' is 1. NOT an answer to a problem. 2. Stupid. 3. NOT an option. 4. Any idiot can say, OH, just spend a little time and reinstall windows.....OH..yeah, and spend 2 weeks reinstalling all your programs....and don't forget to backup all your data or you will LOSE IT ALL (something they neglect to mention and give zero info on how to a. Do that. and b. Recopy it to your Documents, etc)..........z

 

Question Info


Last updated September 15, 2018 Views 2,969 Applies to:
Answer
Answer

I think I have a solution for this problem.

I had a similar problem which surfaced after we tried to run this:

regsvr32 /u wuaueng.dll /s
del /f /s /q %windir%\SoftwareDistribution\*.*
del /f /s /q %windir%\windowsupdate.log
regsvr32.exe wuaueng.dll /s

 

Basically it cleans up the windows update downloaded files etc.

However when starting the service it resulted an error:

net start wuauserv
The Automatic Updates service is starting.
The Automatic Updates service could not be started.

A system error has occurred.
System error 126 has occurred.
The specified module could not be found.

 

relevant log in the windowsupdate.log
2013-01-10          10:48:18:717       3876       d20         COMAPI               FATAL: Unable to connect to the service (hr=80080005)
2013-01-10          10:48:18:717       3876       d20         COMAPI               WARNING: Unable to establish connection to the service. (hr=80080005)

 

Tried to fix it via the windows update website, however that resulted in error: [Error number: 0x8007041D]

relevant log from windowsupdate.log

2013-01-10          10:51:25:678       3876       8e8         Setup    FATAL: Warning: Failed to restart wuauserv service: 0x8007041d
2013-01-10          10:51:25:678       3876       8e8         Setup      * WARNING: Exit code = 0x8007041D
2013-01-10          10:51:25:678       3876       8e8         Setup    *********
2013-01-10          10:51:25:678       3876       8e8         Setup    **  END  **  Setup: Installing client binaries
2013-01-10          10:51:25:678       3876       8e8         Setup    *************
2013-01-10          10:51:25:678       3876       8e8         Setup    FATAL: InstallUpdatedBinaries failed with error 0x8007041d
2013-01-10          10:51:25:678       3876       8e8         WUWeb               FATAL: InstallUpdatedBinaries failed with error:0x8007041d
2013-01-10          10:51:25:678       3876       8e8         WUWeb               FATAL: UpdateClientWorker failed: error 0x8007041d

 

In the event log, the only error was a DCOM error:
The server {9B1F122C-2982-4E91-AA8B-E071D54F2A4D} did not register with DCOM within the required timeout.


After a couple hour of poking around in the system, I was running a process monitor to see what’s going on.
I run a process monitor to see what happens when the system runs the command:
regsvr32.exe wuaueng.dll /s

 

Looking through the process Monitor logs, I have noticed that the regsvr32.exe was written in two different way, once its: REGSVR32.EXE the other is regsvr32.exe

 

I figured out that on the server, there was a second REGSVR32.exe in the path- which was under an oracle installation, and that file was really old, probably an NT4.0 version.
And during the dll registration it tried to use this old regsvr32, which naturally did not process correctly.
------------------------------
So the solution is, check your regsvr32.exe and make sure that it's up to date (ver: 5.2.3790.3959) - on a win2003 system - and check your machine, if there is maybe somewhere hidden an old version of the program.

 

In our case it was enough to call the regsvr32 with fixed path.
c:\WINDOWS\system32\regsvr32.exe wuaueng.dll /s

 

I hope it will help. :)

Joe - MCTIP:EA, MCSE, VCP

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.