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

[Error number: 0x8DDD0009]

5 views
Skip to first unread message

EdC

unread,
May 18, 2006, 12:18:02 PM5/18/06
to
Windows Update starts checking for updates - then abruptly stops, displaying
the "website has a problem and can't display ...." along with [Error number:
0x8DDD0009].

Help??

EdC

MowGreen [MVP]

unread,
May 18, 2006, 1:38:21 PM5/18/06
to
EdC,

Open the Application Event log by going to Start, Run, and typing in
eventvwr.msc
Click OK.
Under Source, look for an error associated with MsiInstaller.
Double click it. If the error states that " MsiInstaller could not find
msxml3.dll ", then go to Start, Run, and type in
regsvr32 msxml3.dll
Click OK.
You should get a confirmation message that the .dll file was succesfully
registered.

If the MsiInstaller error is not in the Application Event log, then open
a Command Prompt by going to Start, Run, type in
cmd
Click OK
At the prompt type in, and press Enter after each line :

proxycfg -d
net stop wuauserv
net start wuauserv
exit

Restart the system. Visit Windows Update. Did that resolve the issue ?
If not, if there's a 3rd party firewall installed, suggest you
temporarily disable it and use the built in Windows firewall.
Now see if the system can access Windows Update.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============

idlexhandsxagain

unread,
May 24, 2006, 2:09:02 PM5/24/06
to
Well... it worked for me. I googled the error number that Windows Update gave
me and it brought me here... I tried the options he gave me and it worked...
I can install my updates again. I had to do the command prompt, start and
stop Automatic Updates before it would work for me... I did both just incase,
though. Anyway, thanks a lot for your advice. :)

MowGreen [MVP]

unread,
May 25, 2006, 2:52:07 PM5/25/06
to
That's great to hear. Glad the issue has been resolved.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============

denisbloud

unread,
Aug 10, 2006, 3:32:27 AM8/10/06
to

Dear GreenMower

I tried both of your solutions to get rid of this error but to no
avail! Could you help me further? Thank you very much for your
assistance. Best regards.
Denis Bloud (Geneva/CH)


--
denisbloud
------------------------------------------------------------------------
denisbloud's Profile: http://forums.techarena.in/member.php?userid=16811
View this thread: http://forums.techarena.in/showthread.php?t=514256

http://www.techarena.in

KSF

unread,
Aug 12, 2006, 5:10:02 PM8/12/06
to
MowGreen,

I did what you suggested (ran regsvr32 msxml3.dll) and it worked!!! Thanks
for the help. I wish it all ended up being this easy. Thanks again for
taking the time to respond and help others, I for one appreciate it.

Keith.

Matthe...@strath.ac.uk

unread,
Aug 18, 2006, 6:49:56 AM8/18/06
to

Denisbloud

Try this

Go into safe mode.

Click Start -> Run

Enter C:\windows\SoftwareDistribution\download (This is assuming
'windows' is your system directory. This should open the folder.)

Now delete everything in the folder

Reboot

Update and cross fingers

Matthew

thomas_ts67

unread,
Aug 22, 2006, 8:21:02 AM8/22/06
to
Go into safe mode to delete "C:\windows\SoftwareDistribution\download" is
overkill. All you need is to use "net stop wuauserv" command (OR select click
"services" from either "administrative tools" or "computer management" and
select "automatic update") to stop "automatic update" service. Remember to
restart the services after completion.

Dale Networkguy

unread,
Sep 7, 2006, 4:43:02 PM9/7/06
to
You can also just rename or delete the parent directory "Software
Distribution" entirely (you rename to preserve it as a safety net - when you
are satisfied then later delete it). You would do this to cover the full
spectrum of Update Services files contained under that folder tree. When the
service (Automatic Update) is restarted the entire directory is recreated and
repopulated fresh.

elsuchnsuch

unread,
Sep 10, 2006, 4:38:01 PM9/10/06
to

"Dale Networkguy" wrote:

> You can also just rename or delete the parent directory "Software
> Distribution" entirely (you rename to preserve it as a safety net - when you
> are satisfied then later delete it). You would do this to cover the full
> spectrum of Update Services files contained under that folder tree. When the
> service (Automatic Update) is restarted the entire directory is recreated and
> repopulated fresh.
>
> "thomas_ts67" wrote:
>
> > Go into safe mode to delete "C:\windows\SoftwareDistribution\download" is
> > overkill. All you need is to use "net stop wuauserv" command (OR select click
> > "services" from either "administrative tools" or "computer management" and
> > select "automatic update") to stop "automatic update" service. Remember to
> > restart the services after completion.
> >
> > "Matthe...@strath.ac.uk" wrote:
> >
> > >

...


> > >
> > > Denisbloud
> > >
> > > Try this
> > >
> > > Go into safe mode.
> > >
> > > Click Start -> Run
> > >
> > > Enter C:\windows\SoftwareDistribution\download (This is assuming
> > > 'windows' is your system directory. This should open the folder.)
> > >
> > > Now delete everything in the folder
> > >
> > > Reboot
> > >
> > > Update and cross fingers
> > >
> > > Matthew

Thanks to both of you! Combining your suggestions got me out of a mess I've
been trying to fix (off and on) for more than a year. The machine was not
mine, so I couldn't just rebuild it, it needed to be "surgically" fixed.

The great thing about the renaming/moving the SoftwareDistribution
directory, you can move it back and prove that it was "evilness" in there
that was the root cause.

The machine in question was a Win2K SP4 machine, too under powered for XP.
More than a year ago Windows Update stopped working. I tried many different
things including certificate deleting and validation tweaking.

Moving the SoftwareDistribution directory did the trick!

Thanks again!

Rich

unread,
Dec 24, 2006, 3:53:00 PM12/24/06
to
Had same problem after clean install of W2k sp4...windows update successfully
dwnloaded and installed BITS 2.0 and Win Installer 3.1....then after
attempting Win update after restart got the 0x8ddd0009...chekd win update log
in WNNT folder saw fatal error looking for Win Installer 3.0...resolved by
uninstalling Win Installer 3.1...manually installing Win Installer 3.0...then
manually installing 3.1 on top of 3.0.......problem solved! Hope this helps,
Rich

J

unread,
Mar 8, 2007, 2:29:03 AM3/8/07
to
Thank you for your assist. The first part didn't work but the second secind
certainly did. Twelve hours and counting at this. The only problem is that
after restarting the computer I have to do it all over again. What in the
****? None of my other systems have this trouble (15+).

Normanm

unread,
May 12, 2007, 10:39:02 AM5/12/07
to
Yes, this combined method worked for me as well. Stopped the service, renamed
the whole folder using _old, restarted the service which created a new
folder, and updates worked quickly. More problematic is what caused the issue
in the first place. My latest suspect is Ccleaner, with its option to wipe
the latest download clean. Anyway, a second thank you.

mn

Sr. Bocadillo

unread,
May 15, 2007, 9:34:34 AM5/15/07
to

Today, when I try to update my
Windows XP Pro with sp2 (5.1 Build 2600)
it takes around 15 minutes of hammering my CPU
then I get [Error number: 0x8DDD0009]

The website has encountered a problem and cannot display the page you are
trying to view. Take the following steps to try solving the problem:
a.. Refresh the page.
b.. In Internet Explorer, delete your Temporary Internet Files by going to
the Tools menu and clicking Internet Options.
c.. Close and then re-open Internet Explorer.

I've tried all that, it's a circle.

anybody help me out here or is this a temporary Ms problem?


Robin Walker [MVP]

unread,
May 15, 2007, 10:37:24 AM5/15/07
to
Sr. Bocadillo <knee...@aton.com> wrote:

> Today, when I try to update my
> Windows XP Pro with sp2 (5.1 Build 2600)
> it takes around 15 minutes of hammering my CPU
> then I get [Error number: 0x8DDD0009]

For a fix to this problem, please do BOTH of the following:

1. For 32-bit systems, download and save to hard disk, and then install:
<http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe>

2. (not for Vista) Download and install update KB927891 version 3:
<http://support.microsoft.com/kb/927891>

If the first of these produces an error message about "Update agent already
installed", then execute the installer again manually, with parameter
/wuforce as in:

WindowsUpdateAgent30-x86.exe /wuforce

After the fixes have been installed, doing a Microsoft Update or Automatic
Update might still take some time (though not as much as before) and
processor and disk usage, but it should not lock out user-level interaction
with the system and applications, so it should not be such an inconvenience.

By the way, do you have Office 2003 installed on the problem PC?

--
Robin Walker [MVP Networking]
rd...@cam.ac.uk


iknowthis

unread,
May 15, 2007, 7:46:03 PM5/15/07
to
THANK YOU, THANK YOU
Been trying for a week to fix the custom windows update error 0x8DDD0009.
We have Windows XP Pro sp2 with all patches and after installing Office 2003
I could no longer
do manual updates. Your fix below worked after I had tried dozens of other
fixes on the web!

Robin Walker [MVP]

unread,
May 16, 2007, 6:03:47 AM5/16/07
to
iknowthis <ikno...@discussions.microsoft.com> wrote:

> THANK YOU, THANK YOU
> Been trying for a week to fix the custom windows update error
> 0x8DDD0009. We have Windows XP Pro sp2 with all patches and after
> installing Office 2003 I could no longer
> do manual updates. Your fix below worked after I had tried dozens of
> other fixes on the web!

Glad to hear it.

As a matter of interest in pinning down the cause of this problem, would you
mind posting a follow-up to tell us the size of the file:

C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb

texasjr

unread,
May 16, 2007, 10:21:00 AM5/16/07
to
I had this same problem and this was exactly the solution I needed!

THANK YOU VERY MUCH!!!!

iknowthis

unread,
May 16, 2007, 11:21:03 AM5/16/07
to
that file size is 38,920KB

Sr. Bocadillo

unread,
May 16, 2007, 12:57:02 PM5/16/07
to
Thank you Robin for your quick response.
caught me out there LOL

The action you suggested has worked as you said.
Yes, I do have office 2003 installed
my DataStore.edb is 38.0MB (38,920KB)

Thanks again
Sr Bocadillo


"iknowthis" <ikno...@discussions.microsoft.com> wrote in message
news:CC1F17F5-FDE9-47A5...@microsoft.com...

Dustin

unread,
May 18, 2007, 5:22:01 PM5/18/07
to
Thank you, you fix worked flawlessly for me.

One question though, if you don't mind. How did you figure this out?

Robin Walker [MVP]

unread,
May 18, 2007, 6:15:24 PM5/18/07
to
Dustin <Dus...@discussions.microsoft.com> wrote:

> Thank you, you fix worked flawlessly for me.
> One question though, if you don't mind. How did you figure this out?

I saw the entries on this issue on <http://blogs.technet.com/wsus/>

Sr. Bocadillo

unread,
May 25, 2007, 3:38:56 PM5/25/07
to
I did reply to this a while ago, strange it's not here!
here is a copy...

Thank you Robin for your quick response.
caught me out there LOL

The action you suggested has worked as you said.
Yes, I do have office 2003 installed
my DataStore.edb is 38.0MB (38,920KB)

Thanks again
Sr Bocadillo

"iknowthis" <ikno...@discussions.microsoft.com> wrote in message
news:CC1F17F5-FDE9-47A5...@microsoft.com...

Robert Aldwinckle

unread,
May 26, 2007, 12:23:46 PM5/26/07
to
"Sr. Bocadillo" <knee...@aton.com> wrote in message
news:OS1sWRwn...@TK2MSFTNGP06.phx.gbl
...

>I did reply to this a while ago, strange it's not here!


It is there. My guess is that you aren't downloading enough headers
at a time often enough to pick it up. This is a fairly active newsgroup
so unless you check frequently some old messages could be missed
by OE's default of Get 300 headers at a time.

E.g. notice the difference in Xref: number between your first reply and this one:

<previous msgid=" news:ut$O7s9lH...@TK2MSFTNGP02.phx.gbl ">
Date: Wed, 16 May 2007 17:57:02 +0100
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.windowsupdate:236019
</previous>

<this>
Date: Fri, 25 May 2007 20:38:56 +0100
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.windowsupdate:236945
</this>


BTW you can click on the above msgid if you want to see it. ; )


FYI

Robert Aldwinckle
---


Dan

unread,
May 30, 2007, 5:07:36 AM5/30/07
to
I received this from Microsoft:

Dear Dan,

Thank you for contacting Microsoft Windows Update Support. My name is
Winston and I am glad to work with you. For your reference, the case ID for
this service request is SRX1036382846. You can contact me directly by writing
an email to my account: v-30...@mssupport.microsoft.com with the Case ID in
the subject line.

From the problem description, I understand that, the error 0x8ddd0009 was
encountered when visiting the update site. We will work together to resolve
this specific issue through the course of the case. If there is any
misunderstanding, feel free to let me know.

I understand the inconvenience you have encountered. Please be assured that
I will try my best to help you.

This issue has been fixed by the newer version of the Windows Update Agent,
3.0 and a hot fix. I suggest we apply them to correct the issue:

Step 1: Manually download and install the new Windows Update Agent 3.0

=============================================

1. Visit the following link and download Windows Update Agent 3.0 to the
Desktop:

http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe

2. Refer to the Desktop and double-click the downloaded file to install it.

After installing Windows Update Agent 3.0, please check the issue again. If
the issue persists, we can try the next step.

Step 2: Download and install a hot fix for this issue.

================================

1. Visit the following link and download the hot fix to the Desktop:

Update for Windows XP (KB927891)

http://www.microsoft.com/downloads/details.aspx?familyid=7A81B0CD-A0B9-497E-8A89-404327772E5A&displaylang=en

2. Refer to the Desktop and double-click the downloaded file to install it.

For more information related to this issue, please refer to the following
Microsoft Knowledge Base articles:

FIX: When you run Windows Update to scan for updates that use Windows
Installer, including Office updates, CPU utilization may reach 100 percent
for prolonged periods

http://support.microsoft.com/kb/916089/en-us

You receive an access violation when you try to install an update from
Windows Update after you apply hotfix package 916089

http://support.microsoft.com/kb/927891

WSUS (Windows Server Update Services) Team Blog

http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx

Your feedback is very important to us. I would appreciate your confirmation
or a reply from you on the results for the suggestions above. If anything is
unclear, or if there are any questions about the steps, please do not
hesitate to let me know. I will be glad to help.

I look forward to hearing from you.

Best regards,

Winston Wu

v-30...@mssupport.microsoft.com

Microsoft Support Professional

----------------------------------------

Satisfied customers are my top priority. Please let either myself or my
manager know what you think of the level of service provided. You can send
feedback directly to my manager, Susan Xu at v-3...@mssupport.microsoft.com

0 new messages