Re: Windows Update - SVCHOST findings
- From: "Robert Aldwinckle" <robald@xxxxxxxxxxxxx>
- Date: Thu, 21 Sep 2006 00:42:09 -0400
"HKComputerServices" <Harlan.Koehn@xxxxxxxxx> wrote in message
news:1158766528.896548.317450@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
....
Concerning the MS's statement: "the Wininet.dll file may try to
unload the index file and fail with an access violation because the
pointer to the index file is NULL". Consider the fact that instead of
truly generating an error, Wininet.dll might simply end up in an
endless loop (generating errors but perhaps all errors are suppressed
and unrecorded), therefore we have processor problems (although it
really appears to be ntdll.dll instead). MS doesn't state that you'll
see any error in the event log, or that "and fail with an access
violation" means that Dr. Watson will record a problem.
There don't even have to be program errors for a loop to occur.
E.g. if the package is corrupt it's possible for a loop to occur
disassembling it. I haven't seen that case but a similar one
that I have seen involves BITS too. E.g. traces of that loop
showed up in the WindowsUpdate.log and the issue seemed to be
that the procedure for assembling the package during the download
phase was not robust enough to realize that it was in a loop.
(Actually that was a while ago, so perhaps they have fixed it;
e.g. instead of just relying on always creating perfect packages
to download.) Etc.
What actually fixed this computer I'm not sure. After much messing
around with it, (shutting down updates, reinstalling services, trying
to access Windows Updates website, etc.), I left the computer running
with the Automatic Updates service turned on over night. As I recall,
the processor was running high as usual when I last saw the computer at
6PM. The next morning it had downloaded 58 updates. I nearly had a
cow, first because it downloaded the updates, and second because there
were 58 of them.
Then you must have a clear indication in WindowsUpdate.log of how
many pieces and how many packages were involved in downloading
that mass of fixes. Another thing you can do during the download phase
is watch BITS at work, e.g. in a cmd window enter:
bitsadmin /monitor /allusers /wrap
HTH
Robert Aldwinckle
---
.
- References:
- Windows Update - SVCHOST findings
- From: NewScience
- Re: Windows Update - SVCHOST findings
- From: HKComputerServices
- Re: Windows Update - SVCHOST findings
- From: NewScience
- Re: Windows Update - SVCHOST findings
- From: antioch
- Re: Windows Update - SVCHOST findings
- From: HKComputerServices
- Windows Update - SVCHOST findings
- Prev by Date: Re: OUTLOOK EXPRESS SEND RECIEVE
- Next by Date: windows update wont run on windows server 2003 sp1
- Previous by thread: Re: Windows Update - SVCHOST findings
- Next by thread: Re: Windows Update - SVCHOST findings
- Index(es):
Relevant Pages
|