2006-10-15

Yet Another Potential Resolution for Error 0x8ddd0009 from Windows Update / Microsoft Update

[See the sidebar at the right on the entry page for more links to information about error 0x8ddd0009 and Microsoft Update / Windows Update.]

Microsoft released Knowledge Base article 916089, FIX: The computer may stop responding for 40 or more seconds when you run a scan for updates or when you try to apply an update on Windows Server 2003, on Windows XP, or on Windows 2000. As many people report an unresponsive system and high CPU utilization prior to receiving the 0x8ddd0009 error from Microsoft Update / Windows Update, it stands to reason that applying the hotfix presented in the article may be of help to some people.

Unfortunately, the hotfix requires one to contact Product Support Services.

The culprit appears to be Windows Installer. Windows Installer 3.1 v2 is a prerequisite, and the only file included in the hotfix is MSI.DLL (dated October 2006).

The KB article states:

This update decreases the duration of a scan that uses the Windows Update Agent. However, a scan is still a CPU-intensive operation. The Svchost.exe process contains the Automatic Updates service. When you perform a scan, the Svchost.exe process can cause CPU utilization to reach 100 percent for a prolonged time. For example, Microsoft Office updates use Windows Installer. When Microsoft Office updates are detected, these updates can contribute to 100 percent CPU utilization for a prolonged time.
If you try this update and it helps, please post a comment about your experience!

3 comments:

david & mary grace said...

There is a newer article (927891) that replaces the one mentioned here.

However, it didn't solve the same error I was seeing on one of our Windows XP SP2 boxes today.

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

What fixed it for me was to stop the Automatic Updates service then rename the c:\windows\SoftwareDistribution\ folder to something else and restart the service. Then, visiting Microsoft Update again let it recreate the folder. *shrug*

david

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

Yes, 927891 does replace 916089, but neither may be the concrete fix for the 0x8ddd0009 error.

Glad to hear the "delete the Software Distribution folder" technique worked!

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

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