2007-03-19

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

In the past, I've written about both high CPU utilization by SVCHOST.EXE as well as the 0x8ddd0009 Windows Update / Microsoft Update error, so I thought I would mention this...

MS KB 932494 (When you use Automatic Updates to scan for updates or to apply updates to applications that use Windows Installer, you experience issues that involve the Svchost.exe process) references problems that are addressed by MS KB 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) and MS KB 927891 (You receive an access violation when you try to install an update from Windows Update after you apply hotfix package 916089). However, even after applying the patch associated with 927891 (which replaces the patch associated with 916089), 932494 indicates that the following problems remain:

1) Certain 100 percent CPU issues are still present when you use the Svchost.exe process.
2) An access violation may occur in the Svchost.exe process.
I (as well as others) have speculated in the past that 916089 (and its succedent patches) can also help with the 0x8ddd0009 error message that one might receive from Windows Update / Microsoft Update.

»

8 comments:

brown705 said...

What seems to have fixed it for me (on multiple computers) is one of Microsoft's suggestions, taken from "Dan's" comment on another post (http://mygreenpaste.blogspot.com/2006/08/error-0x8ddd0009-with-microsoft-update.html#c6107742804442735758).

The particular item that worked for my computers was only the "Step 2" procedure, which I'll copy and paste here:

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.
--------------

I placed this batch file on my server and ran it on a few computers that were getting this blasted error. They now work with Microsoft Update.

Michael

DOSH said...

Hi all. I gues I have a solution. I have installed Win XP Pro CZ SP2 and MS Office 2003 Ent CZ and of course I have had the 0x8ddd0009 problem. I tried almost all advices from here and nothing has changed. I fixed the problem by uninstalling MS Office, making updates and then installing MS Office again.
May be this could be helpfull for someone.
DOSH

Christopher said...

I had to uninstall Office 2003 then reinstall Office 2003 and that worked for me.

Anonymous said...

I also had the same issue with SVC host running a high cpu percentage and getting the 0x8ddd0009 error while trying to run updates.

I uninstalled Office 2003, and updates ran good. I then reinstalled Office 2003 and everything if much normal, no more high cpu usage.

Hope this helps.

Anonymous said...

Unbelievable!!! Tried every suggestion and Yep, found that Office 2003 was causing this problem HOWEVER, when removed, updates worked, Re-installed Office '03, same damn problem. Being an IT Consultant, I'm now at the point of saying "Up yours Microsoft!!!" Absolute crap...

Anonymous said...

I've run into this issue on several Dell Latitude D600 workstations in my company. Even with a freshly installed copy of WinXP SP2 (directly from the Dell CD, not using an image), the Microsoft Update website would peg the CPU @ 100% for about 20 minutes, then produce error 0x8DDD0009.

I can verify that the Microsoft Update website works as normal prior to installing Office 2003 Pro (complete install selected). As soon as Office 2003 was installed, i rebooted and ran Microsoft Update again. I observed the following symptoms:

-CPU utilization remains a steady 100%

-perfmon.msc shows disk & ram utilization are very high for the 1st few minutes, but drop to near zero (and stay there) after about 4 minutes. cpu utilization remains @ 100% throughout.

-explorer.exe (the Windows UI, not the web browser) becomes unresponsive

-the clock in the system tray ceases to change at about 6 minutes into the update process. i started updating at 12:13. the clock worked as normal until 12:19. at 12:26, the clock still reads 12:19.

-Windows Update (_not_ the same as Microsoft Update) works as normal and exhibits none of the above symptoms. Windows Update applies patches only to the OS; Microsoft Update attempts to patch both Office and Windows.

-Office Update works as normal & exhibits none of the above symptoms.

-none of the above symptoms manifest if Office 2003 is not installed.

-none of the above symptoms manifest if Office 2002 (Office XP) is installed.

i have not yet attempted any of the various patches & fixes suggested; for now i am running Windows Update & Office Update separately. my workaround is simply to avoid Microsoft Update, & that seems to be working fine for now.

to turn off Microsoft Update (& revert back to Windows Update), try the following:

1. browse to http://update.microsoft.com

2. on the left browser pane, click the "change settings" link

3. scroll down to the bottom of the page

4. in the "To stop using Microsoft Update" section, tick the checkbox that reads "Disable Microsoft Update Software and let me use Windows Update only"

5. click the "Apply Changes Now" button

6. at the "Are you sure you want to continue?" prompt, click "Yes"

7. you should see "You have successfully disabled the Microsoft Update software on your computer"

8. browse to http://update.microsoft.com again to use Windows Update

hope this helps, and thanks to everyone who has posted before ;)

-a geek

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

Just want to say "Thanks!" to everyone that has taken the time to share their experiences, what worked, what didn't, etc., and their findings.

One comment that I might make is that while Office 2003 certainly seems to be a common factor in the equation, it is not necessarily always a factor. I've encountered several systems in the past that had this error, and many had an older version of Office installed. That said, if Office 2003 is installed, it could certainly be a part of the problem. Others have indicated that uninstalling and then reinstalling Office 2003 has worked for them, while for some the best solution seems to be going back to using Windows Update and Office Update rather than Microsoft Update. I know I've been a bit delinquent in this, and I hope to post more information on this in the coming days, but there are a few patches that the WSUS team indicates can help resolve some of the issues people have been experiencing with Microsoft Update and Automatic Updates. More details on the WSUS team blog @ http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx.

Anonymous said...

hey just wanted to say thanks for all the posts, had the same issue on two laptops. In the end removing Office worked for me too. Thanks!