Windows/Microsoft Update Error

[ASG0856]

Problem with Windows update. Error 0x8DDD0009
This is an XP Home related problem, though web searches have shown it affects XP Pro and Win2K

Since August, when trying to use Windows/Microsoft Update, I get the stated error. I have tried various solutions found on the Web (re-registering various dll's with Regsvc32, disabling IE third pary extensions etc with limited success, but now nothing works. Anyone any ideas?

 

[bcastner]

See:

http://talkback.zdnet.com/5208-12354-0.html?forumID=1&threadID=24550&messageID=463235&start=71

I have written above about recent issues with the scanning algorithm of Windows Update overtaxing system resources. In your case you should reduce the scanning load.




____________________________
Users Helping Users

 

[ASG0856]

Thnx bcastner. I read your article. However, the computer in question is a Toshiba Laptop (S1800-921), with a 1Ghz PIII and 512 Meg of ram, and a brand new harddrive, and therefore new rebuild from restore disc. I had updated to SP2 and upto July and most of August releases. I ran Windows update with task manager running. At the time, the only processes consuming cpu resource where SVCHOST, IEEXPLORE and EXPLORER, with the range varying from 100% down to 75%.
However, I did see a post about downloading and running the MS Baseline Security Analyzer, and downloading any updates on an individual basis. This I did (only 3 Security updates) plus the Windows Genuine Advantage Tool. Post Reboot, I have run windowsupdate sucessfully twice (once express, once custom). This makes me wonder if the absence of the WGAT was causing the problem.
ASG

 

[bcastner]

Using the Baseline Analyzer is one way to reduce scanning load.

I do not see the Genuine Advantage tool as the issue. The issue is the algorithms used to scan the EDB, particularly if there are issues with the integrity of the EDB.

This appears to have some relationship with the load on ntdlll during Windows Defender definition updates. The issue remains somewhat mysterious but is being worked on by Microsoft. PSS is providing callers a hotfix (the unpublished KB article KB919537) that supposedly helps, but is not a complete answer.



____________________________
Users Helping Users