I get no error codes, and nothing in Windows Update.log. Anyone have any
idea as to why they fail? Should I just put Vista on this machine?
Vista - no.
Windows XP is fine.
(Try both methods - ignore the title of the article.)
Search using Google!
http://www.google.com/
(How-to: http://www.google.com/intl/en/help/basics.html )
Examples (phrases to use):
Windows XP updates will not install
updates not installing on Windows XP
my updates download but do not install on Windows XP
why won't my updates install on Windows XP
updates fail to install with Windows XP
The answer to that question has been posted many many times over - all one
has to do is search.
Updates are not installed successfully from Windows Update, from Microsoft
Update, or by using Automatic Updates after you repair a Windows XP
installation
http://support.microsoft.com/kb/943144
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
I ended up fixing it after I reregistered Wups2.dll in the registry.
~Brett
Shenan Stanley wrote:
> Vista - no.
> Windows XP is fine.
>
> (Try both methods - ignore the title of the article.)
>
> Search using Google!
> http://www.google.com/
> (How-to: http://www.google.com/intl/en/help/basics.html )
>
> Examples (phrases to use):
>
> Windows XP updates will not install
> updates not installing on Windows XP
> my updates download but do not install on Windows XP
> why won't my updates install on Windows XP
> updates fail to install with Windows XP
>
> The answer to that question has been posted many many times over -
> all one has to do is search.
>
> Updates are not installed successfully from Windows Update, from
> Microsoft Update, or by using Automatic Updates after you repair a
> Windows XP installation
> http://support.microsoft.com/kb/943144
Brett wrote:
> See, now there's no reason to be cocky about this. I did google
> for the problem; however, without error codes or any key phrases to
> search on, I didn't return anything of interest. Plus I also
> searched the newgroup here before posting. So please don't
> insinuate that I didn't do it.
>
> I ended up fixing it after I reregistered Wups2.dll in the registry.
Nothing "cocky" in my answer. You asked a question so I proceded not only
to give you the answer - but hopefully teach you how to obtain the answer
and probably make it even more likely someone using google would use some of
the same words and thus find the answer I have given you.
Anything else you read into it - that's all you. ;-)
I could have just handed you a fish - instead I taught you to fish and gave
you a taste of the fish in question.
Shenan Stanley wrote:
> Nothing "cocky" in my answer. You asked a question so I proceded
> not only to give you the answer - but hopefully teach you how to
> obtain the answer and probably make it even more likely someone
> using google would use some of the same words and thus find the
> answer I have given you.
> Anything else you read into it - that's all you. ;-)
>
> I could have just handed you a fish - instead I taught you to fish
> and gave you a taste of the fish in question.
Also - there is a newsgroup for update issues:
microsoft.public.windowsupdate
Perhaps you and those who utilize google might benefit from this in the
future. Every bit of knowledge helps.
I didn't use any real 'keywords' or "error codes" in my examples. In fact -
several of the example searches I gave could have come from your original
posting. One key many people neglect is to put the Operating System in
their searches (Windows XP) for problems - and they could even go as far as
to put it in quotes - but many people just refer to it as "XP", which
doesn't limit their search very well. ;-)
Don't get the impression we're all like that though, we're not.
Anteaus,
Supposing you are speaking of my response that not only gave Brad exactly
what was asked for - but how I found the answer and instructional help so
that Brad (and others) might be able to find the answer in the future more
easily... Not only that - but by adding the keywords that I felt would be
most often used by those not knowing the technical terminolgy - actually
upping the chances that a non-tech would more easily find the answer they
seek.
I am unsure how my not only giving the answer but giving the methodolgy
behind finding the answer is " how-to-suck-eggs crud " - but I suppose you
could explain?
But, there is not.
Anteaus wrote:
> Brett, this guy and one or two others like him are forever posting
> this how-to-suck-eggs crud. Or, loudly berating anyone who doesn't
> conform to their personal -and faddist- notion of newsgroup
> ettiquette.
>
> Don't get the impression we're all like that though, we're not.
Shenan Stanley wrote:
> Anteaus,
>
> Supposing you are speaking of my response that not only gave Brad
> exactly what was asked for - but how I found the answer and
> instructional help so that Brad (and others) might be able to find
> the answer in the future more easily... Not only that - but by
> adding the keywords that I felt would be most often used by those
> not knowing the technical terminolgy - actually upping the chances
> that a non-tech would more easily find the answer they seek.
>
> I am unsure how my not only giving the answer but giving the
> methodolgy behind finding the answer is " how-to-suck-eggs crud " -
> but I suppose you could explain?
Anteaus wrote:
> I would if there were anything to gain from it.
>
> But, there is not.
You (nor anyone else) had nothing to gain from your interjection into the
conversation earlier - but you did so - therefore you have made your own
argument null and void.
*shrug*
Up to you.
Hit start
Choose Run
type "CMD"
at the dos screen type regsvr32 wups2.dll
that is the fix