Not experiencing that issue here, GaryDean. There was an update to this
MSKB article on January 17th:
http://support.microsoft.com/kb/916089
It's a later version of msi.dll.
The article mentions the Cause as :
> This problem may occur when you have Microsoft Office installed and the Windows Update
> Agent tries to scan for Windows Installer updates.
Have you tried deleting the logs in SoftwareDistribution\DataStore\Logs
and the DataStor.edb ? First stop the Automatic Update service to be
able to delete them.
That's worked temporarily for some.
MS will work on this, but don't expect anything soon.
If nothing resolves it for your system, then just keep AU off and
subscribe to Microsoft Technical Security Notifications
http://www.microsoft.com/technet/sec...in/notify.mspx
What galls me over this is the fact that there are 2 KBs on similar
issues where one must contact MS for the fix. Problem is, finding the
phone number to contact them is not an easy task.
Check out the first KB link at the top of this post and this one:
http://support.microsoft.com/kb/914810
Click the link to contact Microsoft Product Support Services and see how
long it takes to find the proper phone number.
Good luck ! <w>
MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============
GaryDean wrote:
> Time to bring this up again...
>
> This bug has me and apparently many others fighting this problem all the
> time instead of getting any work done. It's seems that it is related to
> Windows Update.
>
> I have noted the conspicuous absence of replys from anyone at Microsoft when
> this problem gets posted - and it gets posted plenty everywhere.
>
> Time to fess up! Stand up, take responsibility, and fix the problem. (or
> maybe I'll buy a Mac next time)
>
> Latest Info: I stopped accepting any updates auto or not and the
> svchost32.exe problem stopped happening on my XP system. Recently I began
> running Server2003 image on VMWare. today I got the svchost32 error on that
> system.
>
> After reading all of the threads it sounds like Microsoft may be unable,
> thus far, to fix this problem. This could be the collapse of Windows.
> Anybody getting it on Vista?
>
> BTW - I never have ran defender.