TRockford wrote:
> As far as having problems installing updates after installing
> SP3...you need to install Windows Installer 3.0 BEFORE installing
> SP3 by clicking on "other updates". Seems to be a problem for
> people who are doing a fresh install of Windows XP SP2. I see so
> many weird solutions for this that are completely unnecessary. I
> haven't seen where this answer was given so I thought I'd try to
> help
>
> I don't know why it happens or if Microtards ever fixed
> it(doubtful) or not but this solved the problem for me when I
> reinstalled XP SP2
Shenan Stanley wrote:
> Truthfully - if you reboot right before installing SP2 and/or SP3 -
> you should not see the issue that is the subject of this posting.
TRockford wrote:
> That's nonsense. I install XP with SP2(inbox) on a regular basis,
> although it has been a few weeks since the last time. I reboot
> trust me. Unless they have fixed it quite recently, you WILL need
> to install Windows Installer 3.0 prior to installing SP3 or else
> you'll not be able to install any more updates after SP3. Like I
> said, it seems to be a problem with people doing a new full install
> of Windows XP, I dont know about upgrades
Nonsense? Doubtful.
My experience is different than yours? Quite probable.
I have installed SP3 on hundreds, possibly thousands of machines by now -
some with SP1a fresh install, some with SP2 fresh install, some with SP2 and
all the patches and years of mess on it, a few with SP1a and years of mess
on it and I have only had the problem with the updates not installing on a
select few - and none of those did I reboot right before I installed (on
those I did reboot prior to installing SP3 - I have had no issues.)
The fixes I have used on systems I personally instigated the issue upon and
those I had nothing to do with other than trying to help the person in
question are as follows:
First thing to try:
As many will tell you - ignore the title and symptoms listed in the article
referred to. Do method 1 and 2 and see if it fixes your issue whether or
not you repaired anything.
http://support.microsoft.com/kb/943144
Try method 1 and try to update*.
If fails - try method 2 and try to update*.
*try to update:
- Visit
http://windowsupdate.microsoft.com/
- If it asks you to install anything before you see a selection of "Custom"
or "Express" - do so.
- Once you see the "Custom" or "Express" selection, choose "Custom".
- Scan for updates.
- When it lists what it finds - install the critical ones.
- You are generally safe doing the Optional Software Updates. I suggest
avoiding the Optional Hardware Updates completely.
Second thing to try:
http://www.codeplex.com/aureset
Third thing to try:
Get Dial-a-Fix:
http://wiki.djlizard.net/Dial-a-fix
Use its options to fix:
- Windows Installer
- Windows Update
- All the Registration Center options.
Turn off the "Empty System32\Catroot 2"
Do NOT do "Flush SoftwareDistribution".
Then click "GO" and wait until it is done... Reboot will be needed.
- Download/Install Windows Update v3.
http://go.microsoft.com/fwlink/?LinkID=91237
(You *may* need to install it using the command line switch "/wuforce"
right after the reboot - immediately after logging in.)
- Reboot.
- Visit
http://windowsupdate.microsoft.com/ and scan for/install updates.
Usually - method one from the first suggestion fixes the issue.
Sometimes they have to proceed to method two from the first suggestion.
Less seldom - but it does happen - only the tool from the second suggestion
will work - although the first suggestion is contained within the second in
many ways (as well as some of the third.)
And the third suggestion is there because before there was a suggestion (1)
and a suggestion (2) - the third was the best bet and worked in most cases.
Enjoy!
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
Linear Mode
