Thanks for the explanation, NewScience.
I guess a manual install for the needed updates is better than nothing. Do
you notice any common thread between the users that have this same "failure
to install" problem from the windowsupdate site? Is there a fix so that
windowsupdate downloads and installs the updates successfully.
"NewScience" wrote:
> That is how it's suppose to work ... even though it takes a long time (on
> some connections).
>
> There are many variables involved:
>
> 1. Your connection speed
> 2. Your CPU
> 3. The load on MS server(s)
> 4. The number of servers you go thru to get there.
> 5. Modifications MS has made to the server software (they LUUUUUUUUV to
> tinker)!
>
> That's just the connection side. The communication side is just as
> involving:
>
> 1. Once you get connected up, svchost and wuaclt.exe talk with the other
> side and pass initial information back and forth. The basically use the
> information in your C:\Windows\SoftwareDistribution\DataStore\DataStor e.edb
> file. This is a multi-partitioned file ... to view it use esentutl and dump
> the meta-data.
>
> The information is basically history information that is compared with the
> info on MS. In this fashion, this is the only way MS determines what you
> have and don't have. It also initially determines if your Update software
> is up-to-date, in order to determine if it needs to update that first.
>
> This is the first 6-7 minutes ... the more updates you have the longer it
> takes.
>
> Once the history is determined, MS then determines of the updates available,
> which ones are pertinent to your system.
>
> Then it initializes the Installation procedure and goes thru a series of
> downloading packets to the C:\Windows\SoftwareDistribution\Download folder
> as well as keeping the DataStore.edb file up-to-date as it proceeds.
>
> Once everything is downloaded, it then proceeds to install. Each folder
> normally has a update folder that contains an update.exe and some *.inf
> file. The *.inf file contains the information on reboot instructions
> (whether the system should reboot after installation), and/or registry
> modifications. All this information is logged in a C:\Windows\KB*.log file
> as well as the C:\Windows\WindowsUpdate.log.
>
> Once all this is done, the notification that the installations have been
> performed and whether or not the system needs to be rebooted. If I'm doing
> a manual download/install, I normally chose the Close button, so that I can
> see the results of the downloads/installs. Then I manually reboot.
>
> The problem that arises is when DLLs are not re-registered (when in one of
> the packages), you run out of space, or you receive a partial download and
> the connection is broken.
>
> This really screws up the DataStore.edb file.
>
> Regardless, I have yet to see where the Download folder gets cleaned up
> after successful installs and you have these packages sitting around takeing
> up space. Supposedly, I believe I read somewhere, where these folders/files
> are removed after 45 days. Haven't seen it, but really haven't kept tabs.
>
> "Speedy G." <> wrote in message
> news:2C8CBA5F-B84E-48C1-9038-...
> > Hi all,
> > I've been having the installing updates problem like so many others.
> > First of all I am running an almost updated version of windows xp sp2.
> > When I
> > go to the windows update site it takes forever to check for the latest
> > updates (7 minutes). Not too long ago it would only take 30 seconds???
> > Once
> > all the latest updates are shown, I would choose the critical ones first.
> > I
> > would then choose to "download and install". The chosen updates download
> > fine, but fail to install and no errors are reported. I've tried numerous
> > troubleshooting techniques to no avail. I have tried renaming the catroot2
> > folder, deleting the contents of the softwaredistribtion folder and
> > deleting
> > all TIF files. None of these techniques have been successful as far as
> > installing updates from the windows update site.
> > The only way I was able to install the updates successfully was to
> > install them manually from the update.exe files from the downloaded
> > updates
> > (softwaredistribution>>download). My questions are: 1) Is it normal for
> > windows update, when scanning my pc for the latest updates, takes 7
> > minutes
> > (when it used to do it in 30 seconds). 2) How could I rectify the fact
> > that I
> > can't install the updates. Manual is fine and is a good bypass,
> > but.........???
>
>
>
|
Similar Threads
Linear Mode
