Error 0x8ddd0009 with Microsoft Update / Windows Update - What's Going On?

[Added 2006-10-15: Another potential fix here...]
[Added 2006-09-19: Additional things to try here...]
[See other posts about 0x8ddd0009 here and here.]

It seems that a LOT of people are getting error 0x8ddd0009 with Microsoft Update or Windows Update, and are looking for fixes to the problem.

Previously, I had noted that I had gotten around the problem by correcting the system time on the affected computer. But apparently that's not the only "fix" for the problem. Given that it doesn't do the trick for everyone, here is a compilation of suggestions that I have run across. Note that I haven't tried all of them and I can't vouch for their accuracy. Some suggestions involve the use of a 3rd party program or utility. Use them at your own risk.

If you have gotten the 0x8ddd0009 error from Microsoft Update or Windows Update and something listed here fixes it, please chime in. Also, if you did something not listed here and it took care of the problem, please share your resolution with others.

I can't find any reference to 8ddd0009 OR 0x8ddd0009 in the Microsoft knowledge base, so we're pretty much going off of community references here.

While most of the people reporting 0x8ddd0009 seem to be running Windows 2000 with some recent service pack (3 or 4), some are running Windows XP SP2.

To restate, I fixed my problem by ensuring that the system time on the affected computer was accurate - it had been about 22 minutes off. Once I corrected the time, the problem went away.

Another thing to do is to make sure that the computer that is having problems has sufficient free space available on the disk. I'll grab 1 GB out of the air and toss it in here - make sure there's 1 GB of free space on the disk. Just to be safe...

Several people report that uninstalling Windows Installer 3.1 resolved the 0x8ddd0009 error. To uninstall Windows Installer 3.1, use the "Add or Remove Programs" applet in the Control Panel, and find "Windows Installer 3.1 (KB893803)" in the list, and click the "Remove" button. Alternatively, running "%WINDIR%\$MSI31Uninstall_KB893803v2$\spuninst\spuninst.exe" from Start --> Run may do the trick.

Running regsvr32 /u "%systemroot%\system32\mobsync.dll" has apparently worked for at least one individual; Microsoft Knowledge Base article "Event ID 4100 appears repeatedly in Event Viewer details this approach (not in the context of the 0x8ddd0009 error, though), and also the implications:

After you unregister Mobsync.dll, Client Side Caching (CSC) no longer works. The behavior described in the "Symptoms" section of this article does not affect CSC functionality, but unregistering Mobsync.dll does
If that doesn't do the trick, one should be able to UNDO the unregistration (???) of Mobsync.dll by running regsvr32 "%systemroot%\system32\mobsync.dll". Might be worth a shot...

Other people report that downloading / installing / running a program called "Dial-A-Fix" (apparently free) and using it to fix "Windows Update" (whatever that program considers "Windows Update") fixes the problem. The program can likely be found here. And here are extensive instructions for using the program to fix the problem.

Re-running the "Connection Setup Wizard" (presumably, in IE's Tools --> Internet Options --> Connections tab --> "Setup..." button; it can also be run by tossing "rundll32.exe netshell.dll,StartNCW" in the Start --> Run box) is reported to have resolved the 0x8ddd0009 error for several people.

Another thing that has worked in certain cases is running regsvr32 msxml3.dll from the Start --> Run box or a Command Prompt.

Something else to try is to run the following commands from a Command Prompt (Start --> Run --> Cmd):
proxycfg -d
net stop wuauserv
net start wuauserv

Disabling any firewalls might be another thing to try.

Some have indicated that following the instructions in Microsoft Knowledge Base article Error messages that you may receive when you try to download and install updates from the Windows Update Web site, from the Microsoft Update Web site, or from a WSUS server: "0x800704DD," "0x80240020," or both took care of the 0x8ddd0009 error for them.

Stopping the "Automatic Updates" service (from the Services management console snap-in - Start --> Run --> Services.msc, or by running net stop wuauserv), and deleting (renaming is less destructive, I suppose) the %windir%\SoftwareDistribution folder can also resolve various issues with Microsoft Update / Windows Update.

On a more drastic note, uninstalling Windows XP Service Pack 2 and then reinstalling it took care of the 0x8ddd0009 error for at least one person.

Again, if you have gotten the 0x8ddd0009 error from Microsoft Update or Windows Update and something listed here fixes it, please chime in. Also, if you did something not listed here and it took care of the problem, please share your resolution here so that others may benefit.


Anonymous said...

I seemed to fix WU with your help.
Sorry i don't know if it was the Dial-A-Fix or changing from summer to winter time that does it.

Anonymous said...

thx for this article. I tried all of the possible solutions but nothing worked.
After that I uninstalled .NET version 2.0. After a restart I was able to use windows update. May be this helps for other users.


Anonymous said...

Green Paste:
Keep up the good work, thanks for your website. Below is a post from MS's discussion group on this problem, just wanted to share what worked for me.

Hi TaurArian:
I just spent the last 8 hours trying to solve the dreaded Error # 0X8DDD0009
code when trying to use windows update on a toshiba laptop that had a a newly
installed Windows XP Pro os. I have tried numerous suggestions before
getting to your response. I ended up having to re-register the several files
you have list in your response and that is what solved my error message,
thank you for sharing, I hope MS can be more helpful in the future to the
large number of customers who undoubtitly will have the same errror code.

"TaurArian [MS-MVP]" wrote:

> Some have reported that simply re-registering the MSXML3.DLL seems to fix the
> problem.
> 1. Click Start.
> 2. Choose Run.
> 3. In the Run box, type: regsvr32 MSXML3.DLL
> Press okay
> If that hasn't helped you may need to re-registered some more files:
> 1. Click Start.
> 2. Choose Run.
> 3. In the Run box, type (pressing okay after each one) :-
> net stop wuauserv
> Repeat for the following:
> regsvr32 wuapi.dll
> regsvr32 wups.dll
> regsvr32 wuaueng.dll
> regsvr32 wuaueng1.dll
> regsvr32 wucltui.dll
> regsvr32 wuweb.dll
> regsvr32 MSXML3.dll
> regsvr32 qmgr.dll
> regsvr32 qmgrprxy.dll
> regsvr32 jscript.dll
> net start wuauserv

Anonymous said...

Stopping the "Automatic Updates" service (from the Services management console snap-in - Start --> Run --> Services.msc, or by running net stop wuauserv), and deleting (renaming is less destructive, I suppose) the %windir%\SoftwareDistribution folder can also resolve various issues with Microsoft Update / Windows Update.

The above worked for me. After one failed manual WU, the auto update kicked up in the background and DLed updates. Subsequent manual WUs worked fine.

Anonymous said...

WIN XP Home, SP2
What worked for me was to delete cookies, history, temp files (including off-line content) and, because I've always filtered cookies in IE, to make sure that "allow session cookies" was checked, which it wasn't. Have multi GB free on the boot partition so it's not a space issue.

Dale SBSorized said...

Dial-a-fix fixed the issue for me

Anonymous said...

I had the same error, but after I updated my internet browser to Windows Internet Explorer 7, everything is fine now.

Anonymous said...

clearing temporary internetfiles (as described at the windows update error page) did solve the problem

Anonymous said...

Click Start.
Choose Run.
In the Run box, type: (pressing okay after each one)

regsvr32 MSXML3.DLL

net stop wuauserv

regsvr32 wuapi.dll
regsvr32 wups.dll
regsvr32 wuaueng.dll
regsvr32 wuaueng1.dll
regsvr32 wucltui.dll
regsvr32 wuweb.dll
egsvr32 MSXML3.dll
regsvr32 qmgr.dll
regsvr32 qmgrprxy.dll
regsvr32 jscript.dll

net start wuauserv

Restart winxp sp2 and all it's ok


Anonymous said...

Here is what happened to myself. I recently rebuilt a pc XP SP2 ran
Windows Update (approximately 68 updates) and everything was fine. Rebooted.
I added some applications including MS Office so I wanted to run Microsoft Updates. Installed MS Updates and did a Custom and now cannot get anymore updates. Page cannot be displayed. The error code is 0x8DDD0009. I did a
search at MS Support and got no hits. So I googled the error code that led me here and read some of the comments and suggestions.
I removed Windows Installer 3.1, rebooted and ran Microsoft Updates again. It connected and of course the first update it wanted to install was Windows Installer 3.1. I downloaded and installed and rebooted. Crossing my fingers I again ran Microsoft updates and it now is working and am able to get my additional updates.

Anonymous said...

regsvr32 MSXML3.DLL

Solved my problem


Anonymous said...

For XP and 2003 Svr, you can install a new MSI.DLL from Microsoft to resolve this error.

«/\/\Ø|ö±ò\/»®© said...


Thanks. The article you linked to doesn't mention anything about addressing the 0x8ddd0009 errors, though it does pertain to an update for MS KB 916089, which I have previously indicated may help with the 0x8ddd0009 error because it contains a patch for MSI.DLL (Windows Installer, which plays a role in the updates process). The article (MS KB 927891) is titled "You receive an access violation when you try to install an update from Windows Update after you apply hotfix package 916089". MS KB 916089 itself is officially a patch for Windows Installer that is meant to address high CPU utilization and crashes in SVCHOST.EXE. (I've written before about how to make the high CPU utilization more bearable here and here.)

Did the patch from the 927891 article fix your 0x8ddd0009 error?

Of course, Windows 2000 users are still out of luck...

Anonymous said...

I fixed my Windows 2000 by Installing "Serice Pack + Post SP4 Rollup 1" http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=B54730CF-8850-4531-B52B-BF28B324C662&displaylang=en

«/\/\Ø|ö±ò\/»®© said...

Patch that Might Help with 0x8ddd0009 as well as high SVCHOST.EXE CPU Utilization?

Anonymous said...

I have a Win Ser 2003 Std SP1 server that had this problem. Instead of removing and re-installing Dot Net 2.0 I used the Repair option through Add/Remove programs on a to fix this problem.

Nice site - Thanks :)

Eddie said...

A big thank for helping out with a big head ache for me. 2 of our charity PCs came down with this problem. After 1 hour of searching (and swearing :-) ) our solution turned out to be your "re-registered some more files". Worked like a dream. Cheers from the Carers' Centre Hull

Jedi Mercer said...

I had this problem just recently and was able to use proxycfg to fix it. However, in my case I had to do:

proxycfg -u

Which took my proxy settings as configured in IE and stuck them in the registry. So apparently the IE browser is smart enough to use the proxy settings you specify but whatever Microsoft ActiveX component does the checking and downloading is too stupid to do so.

I've only encountered one other application that had a similar problem and that was Harris Stat Guardian. Everyone else either reads the settings from the IE configuration or lets you sepcify proxy settings explicitly.

Dan said...

Hi thanks for everyone who took the time to post. Since I had some successes and failures I'll post them too. (Though I don't typically post.)

Situation: I am updating Windows on 6 computers at work that are 665Mhz with 512MB Ram. I can't install IE7 on these computers. Previsously they had Microsoft update on them at one point when the updating worked. (Of which it seems to have forgotten and switched back to Windows update now that it's fixed.) And no we don't have virus protection or firewalls on the individual computers.

I tried the Microsoft support http://support.microsoft.com/kb/916089 (article ID: 916089 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) It updates the Msi31.dll to the current version, and this did not work for me. (though it has worked for some.)

I tried to empty the cookies and cache. This did not solve the problem. (though it has worked for some.)

I tried to rename the c:\windows\SoftwareDistribution\Download folder to another name forcing the windows updater to recreate it. This did not work for me. (though it has worked for some.)

Visited this link http://forums.techarena.in/showthread.php?t=514256&page=1 And tried some of their suggestions. It did not work for me. (Though it did work for some.)

However someone there did post a wonderful list of what MS told them to do to fix the 0x8DDD0009 error and it did work for me. Here it is:

NOTE: Some third party programs can also affect the Windows Update service. If you are running any third party applications such as Spyblocker, Internet or Web accelerators (programs designed to boost the speed of an Internet connection), security or anti-virus programs (McAfee, Norton, etc.), I recommend we temporarily disable or shut them down and then try accessing the Windows Update site later. Please be sure to enable them again when completing the update process.

Step 1: Reset Internet Explorer settings, and disable third-party Internet Explorer plug-ins

================================================== ================
1. Click Start, Run, type: inetcpl.cpl and press Enter.
2. Select the General tab, and in the Temporary Internet files window, click Delete Cookies, and click OK.
3. In the same tab click Delete Files, check the "Delete all offline contents" box and click OK.

4. Click the Programs tab, and click "Reset Web Settings"
[Note: I couldn't do this because there was no such control, but the fix worked anyway].

5. Click the Advanced tab, and click "Restore Defaults".
[Note: I couldn't do this but there was "Restore Advanced Defaults" and I clicked that; the fix worked anyway].

6. Under the Advanced tab, uncheck Enable third-party browser extensions (requires restarting).
7. Click OK.

Step 2: Re-register system files
1. Click Start, Run, type: notepad C:\register.bat and press Enter. Choose Yes when prompted.
2. Copy the following commands and then paste them into the opened Notepad window.

net stop wuauserv
regsvr32 wuapi.dll /s
regsvr32 wups.dll /s
regsvr32 wuaueng.dll /s
regsvr32 wucltui.dll /s
regsvr32 wuweb.dll /s
regsvr32 msxml.dll /s
regsvr32 msxml2.dll /s
regsvr32 msxml3.dll /s
regsvr32 urlmon.dll /s
regsvr32 softpub.dll /s
regsvr32 initpki.dll /s
regsvr32 mssip32.dll /s
regsvr32 wintrust.dll /s
regsvr32 dssenh.dll /s
regsvr32 rsaenh.dll /s
regsvr32 gpkcsp.dll /s
regsvr32 sccbase.dll /s
regsvr32 slbcsp.dll /s
regsvr32 cryptdlg.dll /s
regsvr32 jscript.dll /s
net stop cryptsvc
ren %windir%\SoftwareDistribution sold
ren %windir%\System32\Catroot2 cat2old
net start cryptsvc
net start wuauserv

3. After you paste the above commands, please close the Notepad window. Choose Yes when prompted to save the file.
4. Click Start, Run, type: C:\register.bat and press Enter to run the commands we have pasted.

After we have finished the above steps, please restart the computer and try to update Windows again.

It worked wonderfully for me, I hope it helps you like it did for me.

Mephitus said...

going to http://www.windizupdate.com (yes thats how its spelled) with firefox (or opera... wont work with IE) works too... it uses a different system for updates entirely so if you are, like me, tired of fighting with IE you can still update...

Anonymous said...

I was getting this same error on a 2000 Server SP4 installation. It error several times, managed to download the BITS and Installed updates and then would not go further. I tried several fixes posted here and nothing worked until I did the SP4 Update Rollup 1. After that it is now working fine.

Anonymous said...

Courtesy of MVP Emeritus Ottmar Freudenberger:

First, install this fix: http://support.microsoft.com/kb/927891

Now install the newly released 'standalone' version of Windows Update Agent
3.0, v.
7.0.6000.374, for 32 bit machines (*not* Vista or any x64 version of

The MS update team believes that this solves all three svchost problems that
folks have been experiencing.

Anonymous said...

Following the release by Microsoft of the last lot of security updates on May 8/07, I downloaded the updates on 20 of our PCs, all of which have Windows XP Pro SP2 as their operating system and are set to receive updates via Microsoft Update. I got this error on one of them which prevented the updates from downloading. I did several things mentioned by various contributors on this site, e.g. I cleared the temporary files and cookies, corrected the time, and ran Dial-A-Fix, none of which cured the problem. (I did not uninstall Windows Installer 3.1, as I was fearful of the consequences it might have, should I not be able to download it again.) As it was getting very late, I did two things to this PC: 1. I changed back to Windows Update. 2. I set automatic update to download, but not install at 10 am the following morning. When I went into the office later that morning, the security updates were waiting to be installed. I installed them without any problem, and since then Windows Update has run normally. (I was able to download some hardware driver updates that had been released). I then used the Office Update site to download the Office 2003 updates.

The error message no longer appears, and I have been left wondering whether changing back to Windows Update, then reverting back to Microsoft Update would also have cured the problem, since it would have reinstalled some files which may have been corrupted and caused the error.

Setting security updates to be installed via the automatic update service has cured similar problems with Windows Update on at least three previous occasions without recourse to any other action. Best wishes, IT Consultant UK.

Chris said...

Dial-a-fix sorted it for me - the problem was on my son's PC, and he was already pitching for a new computer! ;-)

As someone else has commented, after I ran DF there was no improvement in using Update, but I enabled Automatic Updates - which worked. Then I found that Update worked too.

Thank you so much for solving my problem - I'm still waiting for Microsoft to get back to me!!

Tony said...

Hats off to Dan for his 4/9 advice. I ran into the 0x8ddd0009 error after spending some time "tuning up" my machine by installing/deinstalling Spybot (and having tinkered with Advanced mode which hits the registry), installing Net 2.0, deinstalling Norton (whose functionality had continued to get worse for some time now), testing out several "cleaner" packages, installing AVG, having to go through a bunch of restore points ... and I can't even remember what else now!

I recovered quite well from the error by following Dan's instructions with the following exceptions:

(1) I removed the /s silent-supress messages switches. Two of the DLLs were not found and the batch hung until I removed the switches. Then I ran the batch through a DOS window so I could "OK" each success/failure.

(2) Something in the system had a lock on the CatRoot2 folder so I rebooted in SafeMode (F8) to be able to rename the folder.

I did turn off all the virus shields and firewalls during the Windows Update process. As an added measure to ensure the browser would cooperate, I added *.microsoft.com to my list of trusted sites under IE "tools-internet options-security tab."

My best guess as to the root cause is that it was clicking off stuff in Spybot's advanced area which hit the registry, then deinstalling it before clicking everything back to the original state. The secondary suspect is the Net 2.0 installation (which was not deinstalled, but rather eradicated via a restore point).

Again, many thanks Dan!!!

Anonymous said...

I'm getting this a lot.

On this particular computer, uninstalling Windows Installer 3.1, rebooting, and letting Microsoft Update recover from that got me past the 0x8DDD0009 error. I previously tried the series of regsvr32 /s commands and that didn't help.


Anonymous said...

Windows XP SP2 - Uninstalling Windows Installer 3.1 did the trick! Thanks for the info!

Anonymous said...

just wanted to put my $.02 in; hope this will help. incorrect system time does seem to be one cause of this problem. what's interesting (based on the manifestations of this issue in my company's Dell Latitude D600 machines) is that the presence of MS Office 2003 seems to cause the system time to be wrong, but only while Microsoft Update is running.

without Office 2003 installed, everything is dandy. install Office 2003, run Microsoft Update, & CPU utilization escalates to a steady 100%. about 6 minutes into the update process, the system clock ceases to change. explorer.exe (the Windows UI, not the web browser) becomes unresponsive at about the same time, so it's possible the non-updating system clock & the unresponsive explorer.exe are related.

i'm assuming that somehow the presence of MS Office 2003 is preventing the system clock from updating while Microsoft Update runs. this leads to wrong system time, which leads to the 0x8DDD0009 error in Microsoft Update.

the workaround that has worked for me is to avoid Microsoft Update (patches both Office & Windows), & just use Windows Update (patches OS only) & Office Update separately. i haven't tried any of the suggested fixes yet.

Anonymous said...

Dan's instructions did help...thanks a lot~

Before I have tried to run dial-a-fix, re-registered some files and go to microsoft web site for MS KB 927891....all these didn't work for me. After following Dan's instructions, I solve the problem now.

«/\/\Ø|ö±ò\/»®© said...

I received the following email, and thought it might be helpful to post here so with Benjamin's permission...:

I am the supervisor for one of the Geek Squad Precincts. We had noticed this error on some PCs and I was trying to utilize your page to resolve it, unfortunately none of the suggestions worked. Eventually I did discover a new cause of this problem though. It appears that unactivated trial versions of microsoft office cause problems. This makes sense since the program isn't activated but microsoft detects it for updates. Hopefully this can help some other people with this error.

DCI Benjamin Grebner
Geek Squad Precinct #024

Following up with Benjamin yielded the following additional details:
--The system was trying to use Microsoft Update
--The Office version in question was a trial version of Office 2003
--The machine was running XP SP2
--Resolution was to uninstall the trial version of Office 2003, delete the %windir%\SoftwareDistribution folder, and reboot

«/\/\Ø|ö±ò\/»®© said...

As previously mentioned above, might be worth considering installing patch 927891 and Windows Update Agent 3.0...

Fix that Addresses Issues with SVCHOST.EXE and Windows Update / Microsoft Update

Anonymous said...

Had a new client to the area that started receiving this error "about the time" he moved here. Didn't take long to notice that the time-zone was wrong. Correcting that, then rebooting, sorted it out.

«/\/\Ø|ö±ò\/»®© said...

Thanks for sharing!

Incorrect time zone seems in line with some of the other reports, as well as my initial 0x8ddd0009 experience.

Anonymous said...

It took me a long time, but eventually it was fixed with "proxycfg -p ...". We use an automatic proxy script, and this doesn't seem to work. After this I still needed to do one "automatic update" before it started working.

Anonymous said...

-- uninstalled Office 2003, stopped automatic update service (net stop wuauserv), nuked the SoftwareDistribution directory, restarted wuauserv, forced a manual update with wuauclt /detectnow - working fine now.... freakin MS, been playing with this all day.

Anonymous said...

As long as I used windows update, I had no problems. When I used microsoft update, things went wrong.
I tried everything on this page and only one solution worked: install the new update agent: http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe

Sam said...

hi all, i've been trying all of your fixes in attempts to fix many machines encountering this problem at work. great effort to help one another. i found this which has solved the issue for me. its a two part fix involving the hotfix 927891 and then updating the windows update agent. has worked for me on several machines recently after a reboot. detection time for the updates is slow, but the machine is more responsive and it actually gets somewhere.

"That's a known problem, and the fix is on its way. It will be released through Windows Update in May/June, but can already download the components if you want to install them manually. You need to install two fixes:

You receive an access violation error and the system may appear to become unresponsive when you try to install an update from Windows Update or from Microsoft Update

Part two is here:

And the blog is here:
Update on svchost/msi performance issue and 3.0 Client distribution plan

«/\/\Ø|ö±ò\/»®© said...

Good to hear that the 927891 patch combined with the v3 Update Agent worked for you!
These fixes have been reported before (here and here) - sounds like they seem to be working!

Anonymous said...

This worked great for me - uninstalling WUA3.1.

Why can't MS be this helpful!

Many many many thanks


aalia lyon said...
This comment has been removed by a blog administrator.