RE: How I solved the 0x8DDD0009 Problem

Thans alou.

This worked for me.

There was another post that suggested stoping the service and re-registering
several DLLs. Tried that but didn't work for me.

Your suggestion got me past the hang. One note though: the CatRoot2 folder
was locked, so I had to re-boot to be able to rename it.

Fuc_ing Microsoft. I hate being at the mercy of such a disorganized bunch of
fools.

Thanks again.

Mark Starr

"alou" wrote:

MicroSoft Replies To This issue Here is what they wrote me:

Try this advice I received from Micro soft help on this isue. It worked for
me , however it was only a Temporary fix for me and eventually went back to
the original error message. First I removed Norton from Add/Remove. (it had
been acting up).

MS advised to rename some folders. Do this:

Rename Windows Update Softwaredistribution folder
1. Click START, click RUN, and type: cmd
press enter. When prompted in new window at blinking cursor, Please type
this command to stop Auto Update Service, type in: "net stop WuAuServ"
(without the quotes) and press enter.
Make sure command window says that it was successfully stopped before
continuing.
2. Click Start, click Run, and type: %windir% and press enter
3. In the opened folder look for the folder named "Software Distribution"
4. Right click on the folder, select Rename and type: "SDold" (without
quotes). Press enter so changes are executed.
5. Click Start, click Run, and type: cmd and press enter.
type the command "net start WuAuServ (without quotes) this will restart the
Auto Updates service again.
Make sure you get the message this was successfully started before
continuing.

NEXT STEP
Rename CatRoot2 Folder
1.Close all open windows
2. Click, Start, click Run, type: %windir% and press Enter.
3.Locate and open the System32 folder.
4. Find the CatRoot2 folder, right click it, select Rename. Change the name
to CR2OLD. Make sure you press enter after typing the new name, so changes
are executed.

Now Please test the issue again via Windows Update website.

I hope this can help some. Seems like everybody has different results what
will work for them.
alou

"alou" wrote:

I have had this same error 0x8DDD0009 running for the past month. After
assistance from MS I removed Norton, & renamed some WU folders (Software
distribution folder and CatRoot2 Folder) re-booted and was able to use WU
manually on first attempt. However this was a "temporary fix" . Out of the
three downloads successfully completed, only two would install, MSOutlook
junk email filter would not install. Three more attempts at successful
donloads were completed this time with Free version AVG running, with same
error on junk mail filter. Second day, WU automatically starts on system
start-up. Runs downloads, is successful, and the Junk mail filter as well as
the Genuine Advantage update were installed. Third Day back to WU error
0x8DDD0009 again. Have created screenshots and Windows log files as requested
by MS and sent then in. No current advice has been sent back what to do.
Today still am unable to complete any WU scans manually or auto-run. I have
Disabled Automatic Updates, since the background scans slow my system to a
snail crawl, and even freeze programs, and browsers all together. This has
all happened with the Automatic update of IE7. It took about 4 months to
actually get to this point, though the sluggish behavior was noticed
immediately and only worsened. None of these problems existed while running
IE6. My Norton Security Suite had disabled or corrupted itself two times and
I re-installed after IE7 update, then the WU problems started after that, and
tus I totally removed Norton from Add/Remove. Being the resource HOG that
Norton is, I did not need any further agravation of slowness. Using AVG I
have been able to intermittently get a WU scan to complete, maybe one out of
30 attempts, each time.
My plan is to remove IE7, I have downloaded Firefox and have that ready to
use if IE6 does not come back. That way I can still gain access to download
IE6 if need be. If by going back to IE6 does not resolve my problems I will
then try a System Recovery from XP pro disk. If that fails....I will do a
complete Re-format, stick with IE6 until I read that these issues have been
patched or corrected in IE7. I have read way too many reports about these
problems coming from a variety of processor speeds, and other componets, so I
do not think it is reflected on wether you have an older running system as a
PIII, or PIV. I've not heard anyone I know complain that is running Core 2
Duo, but mine took about 4 months to reach this point of WU failures.

alou

"Ron" wrote:

I had the same problem. Unable to access the update site manually (after
waiting for 30 minutes for nothing to happen) followed by the 08xDDD0009
error. Even worse, the computer would periodically try to update
automatically and totally bog down. Even shutting it down and restarting
would not escape this trap - it would immediately bog down again.

After many frustrating attempts to access the Microsoft Update site I
remembered that I had at one time declined to accept the "Windows Genuine
Advantage Update" (KB905474). This is touted as being an optional update, but
I had my suspicions.

I ran the Windows XP reinstallation routine (using the Windows install disc)
which then enabled me to manually access the windows update site. This time I
accepted the "Windows Validation" update (along with 72 other security
updates) and now everything works again.

I know, Microsoft says that KB905474 is an optional update but it appears
that for this machine at least it was NOT an optional update...

Using Windows XP Pro
.