LHearold
Fri May 09 17:58:00 PDT 2008
OK, I still don't know the solution for the problem on already configured
systems, however, after playing around with SP3 for the last day or so here
is what I have and it works for me. On the machines I am having problems
with, on a newly installed version of XP, either Home or Pro, that is
providfd on a restore CD by an OEM (Dell, Gateway, etc.), if you install the
OS then do SP3 updae BEFORE you install ANY drivers then it goes with out a
problem. If any drivers are installed, and by that I mean ANY (Chipset
included which should be the first in the driver install) then the install
will boot back to a BSOD with the error in this thread. The numbers inclosed
may be different but the STOP error will be the same. It may also come up to
the Welcome screen and hang with no HD activity, etc. I have to assume that
there is a problem when the SP does the 3rd party driver inventory. Its
reading something wrong, or whatever, I am not a programmer. After the SP has
been installed dirvers may be installed with no adverse effects. My next test
is to download the original drivers for the devices from their manufacturer
(Intel, etc.) rather than use the drivers provided by the OEM to see if this
changes the equation any. I have also found that on a system that is up and
running with no problems, if the Genuine Advantage check program is installed
it will cause the SP to not install. On one machine it gave an error that it
could not install because Windows XP was not installed. On one other one it
installed and on reboot stated that the SP could not complete because XP was
not installed. But a real surprise was that I had 2 old PCs sitting in the
corner that still had SP1 installed. SP3 went on without a hitch on both. It
seems as though I read that SP3 only included those updates from SP2 and up.
As for the ease of trouble-shooting a failed update. To a person that is
home, with their one PC and the update just crashed it, being able to access
the info to do as you suggested is the problem. Not everyone has a multitude
of PCs sitting around to just jump on a different one to find the answer.
Reading and following sdirections isn't the problem, its access to the
knowledge. If the update was more bug-free then the problem wouldn't exist.
Also, you don't need drivers to install the update unless you require access
to a LAN or internet to acquire it. As a matter of fact, some drivers will
not install unles the latest service pack is installed first. Win2K is a good
example of that with many of the drivers. SP4 was required before the
display, NIC, or many of the RAID controller drivers could be installed.
Naturally reinatalling the OS isn't always an alternative to most users.
Larry Hearold
"Shenan Stanley" wrote:
> LHearold wrote:
> <snipped>
> > installed XP Pro SP2 from the Dell restore CD.
> > NO DRIVERS installed, then run the SP3 update and had
> > 2 of the 4 crash after the install. The one other installed SP3
> > but then, after all drivers were installed, would not install
> > updates from the Windows update site. Could
> > download them but not install. There is a fix for that error also
> > but for the average person trying to update his or her machine, its
> > beyond them.
>
> No drivers?
>
> One of the first things I would recommend doing before trying to install any
> service packs is to update the hardware drivers from the hardware
> manufacturer(s) website. (Your case seems to be Dell.)
>
> As for the updates not installing and that process being 'complicated' (even
> for the average person) - I couldn't disagree more. Most people using a
> computer can type (or have some way of importing letters/words into the
> computer) - so, to me...
>
> -----
> - Click on the Start button, click RUN (or press the Windows-Key+R) and in
> the text entry area, type the following:
>
> net stop wuauserv
>
> - Click OK.
> - Click on the Start button, click RUN (or press the Windows-Key+R) and in
> the text entry area, type the following:
>
> regsvr32 %windir%\system32\wups2.dll
>
> - Click OK.
> - Click on the Start button, click RUN (or press the Windows-Key+R) and in
> the text entry area, type the following:
>
> net start wuauserv
>
> - Click OK.
> - Reboot for good measure and try your updates again.
> -----
>
> Does not seem difficult or 'beyond the average user'. Unnecessary,
> shouldn't have happened, etc - okay - but beyond them? I'd hope not.
>
> This seems to happen with most large releases. More often than not - the
> number of machines that have no trouble (in my experience) greatly
> out-number those that do. It is usually an issue with some software or some
> hardware driver (which is software) on the specific machines - for which the
> manufacturer of said software/hardware usually has to fix. This is not
> obvious - people without trouble have little reason to come here and tell
> everyone.
>
> Also - something else that helps is when someone has trouble and gets a fix
> helps out others by posting what they did to fix the problem they were
> having. This will speed up the process of resolving the similar issues as
> they come in. The more the solution is posted, the more likely someone
> using a search engine will stumble across it. I notice that you say you
> resolved the issue in another thread (referenced in this thread) but you did
> not take the time to go back and let everyone else in on your resolution.
>
>
http://groups.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/8f94e74893773827
>
> I know I would be interested - just because I might be able to use your
> resolution to help others... If it comes up. So far - in all my SP3
> installs - I have had only one issue and a reboot resolved that.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
>
http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>