> I know the above seems to be a bit stupid .. but in large organisations
> where every computer is mission critical and when solutions dont really seem
> to work.. those people blame the system admins.
No, it doesn't seem stupid at all. Which is why I'm no Sys admin <w>
I've been told that there will be a resolution for this issue. Just when
that will be ... but, MS is very well aware of the issue.
Have also been told that the issue stems from msi.dll. This has been
confirmed by someone who used a Sysinternal tool to monitor a system
when it first booted up. Not sure if it was ProcessExplorer or not.
And, yes, that is just a temp fix for the issue. I know of nothing that
will resolve this issue 100% of the time. Sometimes the fix that MS
offers, a more current version of msi.dll works, sometimes it doesn't.
What I would do for now would be to stay away from Microsoft Update for
now and just stay opted in to Windows Update. If you running WSUS in a
business environment this can be a HUGE PITA.
There are a number of Sys Admins who are not happy campers at the
present mowment, believe me.
MowGreen
===============
*-343-* FDNY
Never Forgotten
===============
ifanatic wrote:
> Thanks for the resolution MowGreen.
> Goes into my documentation
>
> But from all website it seems that there is only a temporary fix for this
> solution.
> Some solutions work on some computers having EXACTLY the same problem and
> some dont.
>
> Is there a permenant fix available?
> A patch?
> A software which detects that this problem exixts?
>
> I know the above seems to be a bit stupid .. but in large organisations
> where every computer is mission critical and when solutions dont really seem
> to work.. those people blame the system admins.
>
> Waiting for your feedback
>
>
> "MowGreen [MVP]" wrote:
>
>
>>Try this - show hidden files, folders, and system files
>>http://www.bleepingcomputer.com/tuto...l62.html#winxp
>>
>>Stop the Automatic Updates service from Start > Run > type in
>>
>>net stop wuauserv
>>Click OK
>>
>>Navigate to WINDOWS\SoftwareDistribution\DataStore
>>Delete ALL contents of DataStore
>>NOTE: This will remove the updating history that shows on
>>Windows/Microsoft Update
>>
>>Delete ALL contents of WINDOWS\SoftwareDistribution\Download
>>
>>In addition, you may clear the *contents* of the WindowsUpdate.log
>>located in %windir% but do *not* delete the log. There is also a
>>Windows Update.log [notice the space between Windows and Update]. Unless
>>it's grown to at least over 1 MB, just leave that alone. It it has, then
>>clear the contents of it.
>>
>>Empty the Recycle Bin
>>Restart Automatic Updates from Start > Run > type in
>>
>>net start wuauserv
>>Click OK
>>
>>That *should* temporarily resolve the issue.
>>
>>MowGreen [MVP 2003-2007]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>ifanatic wrote:
>>
>>
>>>Hello all,
>>>I am experiencing svchost error message on our HP machines while updating
>>>them.
>>>
>>>(Operating system : Microsoft Windows XP SP2 , HP Machines - DC7600 Small
>>>form factor , DC7700 Convertible minitower)
>>>
>>>Here is the exact error message:
>>>Application popup: svchost.exe - Application Error : The instruction at
>>>"0x745f2780" referenced memory at "0x00000000". The memory could not be
>>>"read".
>>>
>>>On Microsoft's website, there is a HOTFIX for users who are experieincing
>>>the following error message:
>>>
>>>Application popup: svchost.exe - Application Error : The instruction at
>>>"0x745f2780" referenced memory at "0x00000070". The memory could not be
>>>"read".
>>>
>>>Notice that the 2nd error message is different from the 1 which I am getting
>>>while updating the machine.
>>>
>>>So far I have tried the following:
>>>1.) Patched the machines with the hotfix supplied by Microsoft (DOESNT help).
>>>2.) Turned off automatic updates , scan the machine manually by going to
>>>windows update website. After updating turning back automatic updates ON.
>>>
>>>The second method works fine.
>>>
>>>I would loike to know if anyone here is in the same situation I am in and
>>>what steps you guys have used to resolve this issue.
>>>
>>>Awaiting for your reply,
>>>
>>>
>>>
>>
Similar Threads
Linear Mode
