From: PA Bear [MS MVP] on
[To keep track of things, it helps immensely if you include all of previous
message(s) in your replies to the newsgroup. Thank you.]

Repost:

Free unlimited installation and compatibility support is available for
Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and
e-mail support is available only in the United States and Canada.

• US:
http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=11273&gprid=522131

• CA:
http://support.microsoft.com/oas/default.aspx?ln=en-ca&prid=11273&gprid=522131

• UK:
http://support.microsoft.com/oas/default.aspx?ln=en-gb&prid=11273&gprid=522131

• AU:
http://support.microsoft.com/oas/default.aspx?ln=en-au&prid=11273&gprid=522131

• Other: http://support.microsoft.com/oas/default.aspx?gprid=1173 | select
Windows XP | select Windows XP Service Pack 3
--
~PA Bear


PJK wrote:
> Thanks for the reply and the reference to the KB.
>
> Because methods 1 and 2 failed, method 3 appears to be the next approach.
> That method will require preparation to assure full recover if anything
> goes
> badly. I'll have to schedule time next week to attempt this approach
> after
> mopping up the failed attempts.
>
> Regarding the mopping up, I restored the system to the restore point taken
> prior to the Windows Update session because of this error message during
> the
> rollback of each failed SP3 installation: "Windows X Service Pack3
> installation failed, leaving Windows XP partially updated. Service Pack3
> installation did not complete".
>
> However, unlike the prior restores after the SP3 install failure, the
> latest
> restored system is incurring errors. The event log is now recording the
> following persistent errors:
>
> The Windows Media Player Network Sharing Service depends on the Universal
> Plug and Play Device Host service which has failed to start because of the
> following error: %%0
>
> The SQL Server (SQLEXPRESS) service terminated with a server-specific
> error
> 3417 (0xD59)
>
> This computer is configured as a member of workgroup, not as a member of a
> domain. The Netlogon service does not need to run in this configuration.
>
> What advice does Microsoft offer that would enable me to eliminate these
> errors and return my system to the state before the attempted SP3
> installs?
> I would prefer to attempt method 3 from the error free state I had before.

From: PJK on
Thanks again for your advice.

After getting XP back to its pre-update state, performing other clean-up,
and suspending anti-virus as well as any other programs protecting registry
keys, the SP3 update was successfully applied.

I used the on-line Windows Advantage Authetication scan to get around a
persistent problem in Windows Update with the tool update and thereby
reacquired the capacity to use Windows Update for the follow-on updates.

Initial slowness in updated System was sourced to cpu hogging and disk
fragmentation as you suggested in other posts. A few programs had to be
reinstalled for better and/or more orderly performance. A few others had to
be excepted from virus scanner and/or the OS firewall for the moment.
Windows Defender was removed. One legacy program is broke but can be fixed.
Though XP SP3 performance has improved, it is still slower in user-interface
response than XP SP2 at this writing. I'll just keep grooming the system.

Thank you again for your help.
--
Paul Keller



From: PA Bear [MS MVP] on
YW & thanks for your feedback.

Thread history:
http://groups.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/d70268ed1cb77b7e
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

PJK wrote:
> Thanks again for your advice.
>
> After getting XP back to its pre-update state, performing other clean-up,
> and suspending anti-virus as well as any other programs protecting
> registry
> keys, the SP3 update was successfully applied.
>
> I used the on-line Windows Advantage Authetication scan to get around a
> persistent problem in Windows Update with the tool update and thereby
> reacquired the capacity to use Windows Update for the follow-on updates.
>
> Initial slowness in updated System was sourced to cpu hogging and disk
> fragmentation as you suggested in other posts. A few programs had to be
> reinstalled for better and/or more orderly performance. A few others had
> to
> be excepted from virus scanner and/or the OS firewall for the moment.
> Windows Defender was removed. One legacy program is broke but can be
> fixed.
> Though XP SP3 performance has improved, it is still slower in
> user-interface
> response than XP SP2 at this writing. I'll just keep grooming the system.
>
> Thank you again for your help.