lhearold
Thu May 08 18:46:32 PDT 2008
On May 8, 12:07=A0pm, "PA Bear [MS MVP]" <PABear...@gmail.com> wrote:
> Repost: How are you attempting to install SP3 on these machines, via Windo=
ws
> Update or using an installer you've downloaded? =A0If the latter, is the
> installer named windowsxp-kb936929-sp3-x86-debug-enu.exe?
>
> MS installation and compatibility support should be able to answer most of=
> your questions.
> --
> ~PA Bear
>
>
>
> LHearold wrote:
> > All can validate with WGA tool with no problem. Did that before I starte=
d
> > the SP3 install since it was on a checklist that I downloaded from MS
> > technet. I think the fix given in one of the links you provided may work=
.
> > Will give it a try tomorrow. I guess I'm confused about their terminolog=
y
> > though. I always thought it was Retail and OEM. So what is a "checked"
> > version? How do I know ahead of time if I have a checked version, OEM, o=
r
> > what. There isn't any literature I can find that even mentions a "checke=
d"
> > version. =A0Where and how would a "checked" version get installed on a P=
C?
> > The 3 PCs in question here had their initial install and all updates don=
e
> > by me personally as part of a maintenance agreement I have with my
> > customers. It would be nice to know ahead of time whether or not a
> > particular PC is going to give me a hassle during the update.
>
> > "PA Bear [MS MVP]" wrote:
>
> >> How are you attempting to install SP3 on this machine?
>
> >> I'd question the legitimacy of these machines myself. =A0Can all 3 mach=
ines
> >> Validate here? =3D>
> >>
http://www.microsoft.com/genuine/downloads/Validate.aspx
>
> >> That being said, see
> >>
http://www.askvg.com/windows-xp-sp3-setup-error-cannot-update-a-check...=
>
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> >> Free unlimited installation and compatibility support is available for
> >> Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat an=
d
> >> e-mail support is available only in the United States and Canada.
>
> >> =95 US:
> >>
http://support.microsoft.com/oas/default.aspx?ln=3Den-us&prid=3D11273&gp=
r...
>
> >> =95 CA:
> >>
http://support.microsoft.com/oas/default.aspx?ln=3Den-ca&prid=3D11273&gp=
r...
>
> >> =95 UK:
> >>
http://support.microsoft.com/oas/default.aspx?ln=3Den-uk&prid=3D11273&gp=
r...
>
> >> =95 AU:
> >>
http://support.microsoft.com/oas/default.aspx?ln=3Den-au&prid=3D11273&gp=
r...
>
> >> =95 Other:
http://support.microsoft.com/oas/default.aspx?gprid=3D1173|
> >> select
> >> Windows XP | select Windows XP Service Pack 3
> >> --
> >> ~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/
>
> >> LHearold wrote:
> >>> I am doing an update to SP (Pro) to SP 3 for a client. They have 7 PCs=
> >>> that
> >>> need this update. On three of the PCs I am getting the following error=
.
>
> >>> Service Pack 3 Setup cannot update a checked (debug) system with a fre=
e
> >>> (retail) version of Service Pack 3, or vice versa.
>
> >>> The COA is valid on all theree. Two are Dell and one is an OEM version=
.
> >>> I
> >>> don't quite understand the error and have had no luck in finding it
> >>> anywhere.
>
> >>> Need some help please.
>
> >>> Thanks,
>
> >>> Larry Hearold- Hide quoted text -
>
> - Show quoted text -
PA Bear,
Per our brief conversation on a different thread. The reason I have
not posted back on this one is that I haven't had time to set up my
user name again. Somehow it got lost or something since the group
didn't recognise my login. You had provided me a link on info to do a
registry change to allow the update to run. This worked but with
modification. The link gave instructions to change HKLM\SOFTWARE
\MICROSOFT\WINDOWS NT\CURRENTVERSION string value of CurrentType from
Free to Checked, or vice-versa, and reboot. If I rebooted, the same
error came up and the registry was changed back to the original value.
The only way I could get the value to remain as changed was to boot in
safe mode and make the change. This worked on the machines in this
thread, however, later on I found the same problem on another machine
at the same client and the fix DID NOT work. HOWEVER, I created a new
user, logged in under the new user account and the update worked
flawlessly. After the update was complete, I deleted the user account
I had created and everything was fine.
As a side note, about half of the machines won't install the
downloaded updates from the MS Windows Update site after the SP3
update is applied. There is a fix on the MS Knowledge-base, Article
943144, describing how to re-register the WUPS2.dll that will take
care of this problem.
So, this problem is resolved, for now. Whether or not it wil lrear its
ugly head again in a different manner I don't know. My apologies if I
have ticked you off because you are a volunteer. No offense intended
but I have more people asking me if I am paid than providing any
assistance. I'm 68 and supposed to have been retired for the past 4
years but somehow I'm in demand. Must be age and knowledge, sure as
H___ ain't beauty.
Larry Hearold