Post by JohnG
I have McAfee installed on all but two. I'm sure AV is not a factor
though, because one of those exceptions is my own brand new Dell
notebook (D820), which I ordered from Dell without AV, and on which I
have not yet installed any AV. The other is an OEM master with all
patches regularly applied, and no AV installed. These obviously have
very different origins, yet both have this problem.
On my notebook computer the Windows updates were applied August 13,
but included many older updates, since the image from Dell apparently
had not been updated in a long time. The next day I installed Office
2003 SP2, and then 9 updates. So the Office updates were not applied
at the same time as Windows, which some have suggested as a common
All other computers have McAfee installed, and have been updated on a
regular basis. The error began to occur after the August updates.
However, in case this is a common factor, it is possible that all the
computers affected, including the OEM master, had the July or earlier
updates applied at the same time as the August updates. I will have to
research this further if it becomes important.
To troubleshoot this I have deactivated all non-Microsoft startup
programs, services, drivers, handlers, components, BHOs, shell
extensions, toolbars, etc., as well as some 20 or so Microsoft
services that I don't need. I restarted and verified that none of
these were running. I then shut down allowing the update to install
and still got this error. I am therefore quite convinced that this is
purely a Microsoft problem unrelated to any third-party application.
After installing the 914810 MSI.DLL hotfix recommended by Lawrence,
the error changed to '0x476122d0'. I have now uninstalled that hotfix,
and the error has reverted to the original '0x745f2780'. This would
indicate to me that MSI.DLL is very much involved with this error.
This was, however, not replaced in any recent updates, so obviously
there is some interaction with another component that was replaced.
This problem is just so completely frustrating. The only thing I was able
to find that finally let me boot without the svchost.exe fault (0x745f2780)
was to disable the "Symantec SPBBCSvc" service and "Symantec AntiVirus
Definition Watcher" service, reboot, and the problem FINALLY went away. I
re-enabled those services, rebooted, and the problem has stayed away.
Before I had disabled those two services, however, I had also tried
disabling some other services, changed AU settings, anything I could think
of that I had or hadn't tried last week, and it wasn't until I disabled
those two Symantec services that things cleared up. Apparently that also
is a coincidence? Or maybe not, but that this is only the reason on my
Also, on most of my systems, the key to getting the svchost.exe fault to go
away is to get the pending updates installed manually. Most of the time
that has been the "solution", but not always. This system had no problems
with the September 12 updates, even though many of my other systems did.
However, this one computer then decided to choke on the VML patch from this
past week, while none of the others did that I've discovered.
Unbelievable. So, basically, starting in August 2006, every Patch Tuesday
is going to give me some random % of my systems that will have this error
and not even the same systems month to month, but apparently just
completely at random?
Oh, and I had specifically asked for the 914810 MSI.DLL hotfix, even
pasting in the URL to these discussions and releveant parts of these
various discussions, but Microsoft Support would not give it to me.
Unfortunately, adding SVCHOST.EXE to the DEP exclusion list did not help at
all, which was what they told me to do.
This had never been a problem for me, before the July patches were
released. After the July patches, though, the only change on all of my
systems is that the wua* program files (wuaueng.dll, wuauclt.exe, etc.)
were updated to the newer 22.214.171.12407 build (as part of the WSUS SP1 update
I assume, however, not everyone has that build, but that some systems are
also having the svchost fault with the common 126.96.36.1999 build? Yes?
Assuming the answer is yes, that only leaves system files modified with
the June 2006 patch set...