RE: 0x8DDD0004 Error at windows update WEB

Tech-Archive recommends: Fix windows errors by optimizing your registry



I finally resolved this issue and thanks too all that posted here. I had to
do some of my own digging to finally resolve the issue as the steps mentioned
here only took me 90% of the way.

Basically Automatic Updates service would not start. This was because the
wuaueng.dll file could not be registered. This was because one of the DLL
files (SFC_OS.dll) that wuaueng.dll depends on was corrupt. I re-installed
SFC_OS.dll and hey prsto it all works.

I shall give a quick explanation of the further steps I took in case anyone
else comes accross this issue!

I'm using Windows XP Pro SP2
I received the error code 0x8DDD0004 on the Windows Update site.
I researched this error and performed the following actions:

I made sure Active X was able to run, switched off all firewalls (WIndows
Firewall & Zone Alarm)
I made sure the WUWebControllClass was enabled in the add-ons.
I manually deleted all files from folder C:\WINDOWS\Downloaded Program Files
so IE would re-install them.
I renamed the SoftwareDistribution folder but still got error!

I then found out that Windows Updates (automatic updates and also the
website) require that the Service: "Windows Updates" is up and running. The
WindowsUpdate.log file confirmed this: the log file
read2006-12-12 14:48:14 2452 dac COMAPI FATAL: Unable to connect to the
service (hr=80080005)
2006-12-12 14:48:14 2452 dac COMAPI WARNING: Unable to establish connection
to the service. (hr=80080005)

So, I checked if the service was indeed running and it's status was
"starting". It was set to start automatically. I changed the service to start
manually and restarted the PC. I tried to manually start it but again, it
just hung.

So I was sure if I could get this service running we would be back in
business. I then came accross this thread telling me to register the
following DLLs:

REGSVR32 C:\WINDOWS\system32\wuapi.dll
REGSVR32 C:\WINDOWS\system32\wuaueng.dll
REGSVR32 C:\WINDOWS\system32\atl.dll
REGSVR32 C:\WINDOWS\system32\wucltui.dll
REGSVR32 C:\WINDOWS\system32\wups.dll

They all succeeded except for wuaueng.dll. I receievd an "access denied"
error message.

I checked the services again and still it would not start, so I reckon I'd
narrowed it down to a problem with wuaueng.dll.

I tried to re-install the WindowsUpdate software manually by downloading
WindowsUpdateAgent20-x86.exe I attempted to install this but receievd an
error 0xc000007b

I opened the c:\WINDOWS\WindowUpdate.log and curiously the same error
(0xc000007b) was encountered on 2006-11-30 at 12.45pm. It mentioned an "Out
of proc datastore process exited with error 0xc000007b before signalling
ready event"

I decided to try and register the wuaueng.dll file again. I attempted
re-booting into safe mode etc but still no joy. I made sure all the
permission were set correctly and they were.

So I then found another thread recommending downloading Dependency Walker to
open the wuaueng.dll file and inspect it. So I did this and opened the
wuaueng.dll file. Dependency Walker had 3 errors about missing functions. I
was missing one DLL file called MSJAVA.dll. I downloaded this and registered
it succefully but still Dependency Walker had 1 error. I coudlnt find what
the error related to, but DW highlighted one of the dependant DLLs in red.
The file was called SFC_OS.dll. The Link Checksum on this file differed to
the Real Checksum and there was no version history. More importantly the File
Time Stamp was 12.15PM on 2006-11-30, half an hour prior to when Automatic
Updates receiving the error (0xc000007b). The Link Time Stamp was some date
in 2004. So, I inspected the SFC_OS.dll. It's file size in the system32
folder was 1KB...hmm. The version of this file in XP Pro should have a file
size of 137KB. So I downloaded this file again and tried to re-register
SFC_OS.dll. I receievd an error. This SFC_OS file apparently has something to
do with File SYstem protection. It is possible to turn it off (In the
registry, the key SFCDisable in the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
location must be set to FFFFFF9D to turn it off, or set to 0 to switch it
on). SO I set it to FFFFFF9D to switch it off and rebooted the computer.

I then attempted to register wuaueng.dll and it succeeded!!!!!! More
importantly, the Automatic Updates service was up and running and the Windows
Update site worked too.

NowI jst have to worry about switching SFC_OS.dll file on again.
.



Relevant Pages

  • Re: Reporting Hackers
    ... Have you patched the programs OTHER than Windows XP/Norton using their ... Patches and Updates! ... How to configure and use Automatic Updates in Windows XP ... are pay - some you can only download if you are registered - but it is best ...
    (microsoft.public.windowsxp.security_admin)
  • Re: When Automatic Updates can be harmful
    ... I was advised nearly 12 months ago by an MVP to be cautious of MS updates. ... For years I've been advising Windows consumers to disable Automatic ... Don't click the Automatic Updates bar at ... Microsoft pushes out the Patch Tuesday door. ...
    (microsoft.public.windowsxp.general)
  • Re: wuauclt.exe error message (Windows Update fix)
    ... I've been having a problem with my Windows XP operating system. ... Click the Automatic Updates tab. ... UN-check "Automatically restart", if it is checked, and click OK. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Turning off Auto Updates
    ... do your Manual Updates in both Windows Updates and Microsoft Office. ... to before the Windows and Office Updates can download and install properly. ... Click Properties then the Automatic Updates tab and choose "Turn off ... I deleted the Windows Update policy in HKEY_Loc_Machine as you suggested. ...
    (microsoft.public.windowsupdate)
  • Re: Windows Update / now asks for Registering ?
    ... Register MSXML3.dll ... | network every month or so I do the updates, Windows, AVG, AdAware and Spybot, ... | infact the windows updates I was notified almost immediately the laptop had ...
    (microsoft.public.windowsupdate)