WinXP SP3 MS-update web bug (KB936929)

Hi

Am I the only one coming across this bug??? it's now 6-8 weeks since SP3 was
released on MS-update web and the bug is still there....

Take a new computer, install WinXP pro with SP2 the normal way.
(fix any missing hardware drivers)

Go to MS-update on the web, attempt to run it by manually selecting stuff.

You will now be giving the oportunity to install SP3 wich sounds like a
convenient shortcut.

Select and install SP3

when it's done and the PC has rebooted return to MS-update to find some more
stuff.

The bug is that you will from now on not get anything successfully installed
rom MS-update (web)
You will get suggestions, it will be downloaded, but no matter what you do;
the result will be the same "installation was not successfull"

PS. I'm never running MS-update the automatic way, so I do not know how that
works.

I have found one work around:
DO NOT INSTALL SP3 FROM THE WEB, Download it from MS-download and install it
as an administrative file. After that its ok to run MS-update from the web
again.


Does anyone recognise this? any suggestion how to "unlock" the PC's I have
that still today cannot get anything successfully from MS-update webpage?


Regards

Kjell


Regards

Disregard the title - try method 1 if not then proceed to 2 -

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

--

TaurArian [MVP] 2005-2009 - Update Services
http://taurarian.mvps.org
======================================
How to ask a question: http://support.microsoft.com/kb/555375
Computer Maintenance: Acronis / Diskeeper / Paragon / Raxco


"Kjell" <Kjell@discussions.microsoft.com> wrote in message
news:659C5084-19B3-4E19-B65F-349122DC66BE@microsoft.com...
| Hi
|
| Am I the only one coming across this bug??? it's now 6-8 weeks since SP3 was
| released on MS-update web and the bug is still there....
|
| Take a new computer, install WinXP pro with SP2 the normal way.
| (fix any missing hardware drivers)
|
| Go to MS-update on the web, attempt to run it by manually selecting stuff.
|
| You will now be giving the oportunity to install SP3 wich sounds like a
| convenient shortcut.
|
| Select and install SP3
|
| when it's done and the PC has rebooted return to MS-update to find some more
| stuff.
|
| The bug is that you will from now on not get anything successfully installed
| rom MS-update (web)
| You will get suggestions, it will be downloaded, but no matter what you do;
| the result will be the same "installation was not successfull"
|
| PS. I'm never running MS-update the automatic way, so I do not know how that
| works.
|
| I have found one work around:
| DO NOT INSTALL SP3 FROM THE WEB, Download it from MS-download and install it
| as an administrative file. After that its ok to run MS-update from the web
| again.
|
|
| Does anyone recognise this? any suggestion how to "unlock" the PC's I have
| that still today cannot get anything successfully from MS-update webpage?
|
|
| Regards
|
| Kjell
|
|
| Regards

hahaha

this is life, I've now been looking for a solution to the bug above for
several weeks but apparantly not been looking at the right place.

The solution to the above has been discussed as a repair scenario, that's
why I did not find it earlier.


The problem is the same, the file wups2.dll is not correctly registered for
win update to proceed after SP3 has been applied over the web.

Do the registration and the problem is gone.


see this link for info on how to register wups2.dll
http://support.microsoft.com/kb/943144



thanks

Kjell

Kjell wrote:

> Am I the only one coming across this bug???

This has already been reported to Microsoft. All going well, the next version
of Windows Update (due to be released soon) will fix this.

In the meantime, you can avoid the problem by rebooting just before installing
service pack 3 (i.e., when it is offered to you the first time reboot the
machine instead) or you can fix it by reregistering wups2.dll as you've already
noted.

Harry.