Cannot activate Windows XP
-
Monday, 23 April, 2012 10:41 PM
Microsoft Support confirm my product key (on COA sticker attached to PC) is genuine. I am using an XP OEM CD.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Not Activated
Validation Code: 1
Cached Validation Code: N/A
Windows Product Key: *****-*****-XD49X-28Y9R-HB2GT
Windows Product Key Hash: Y4w6nslkak7wEiGSx9Hq5V4u3oQ=
Windows Product ID: 51882-OEM-2266525-54742
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 5.1.2600.2.00010100.3.0.pro
ID: {8C0C1BCA-A28F-4996-B861-8D73249CF9D7}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: N/A
Architecture: N/A
Build lab: N/A
TTS Error: N/A
Validation Diagnostic: 025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A
Version: N/AWindows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-543-80070002_025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)
Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: AllowedFile Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{8C0C1BCA-A28F-4996-B861-8D73249CF9D7}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-HB2GT</PKey><PID>51882-OEM-2266525-54742</PID><PIDType>3</PIDType><SID>S-1-5-21-507921405-484763869-1801674531</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq dc7600 Small Form Factor</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>786D1 v01.61</Version><SMBIOSVersion major="2" minor="4"/><Date>20090701000000.000000+000</Date></BIOS><HWID>8F623F070184E066</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Licensing Data-->
N/AWindows Activation Technologies-->
N/AHWID Data-->
N/AOEM Activation 1.0 Data-->
BIOS string matches: yes
Marker string from BIOS: 8619:Compaq Computer Corporation|116FC:Compaq Computer Corporation|1FFEA:Compaq Computer Corporation|E618:Compaq Computer Corporation|11723:Compaq Computer Corporation|11723:Compaq Computer Corporation|1FFEA:Hewlett-Packard Company|E618:Hewlett-Packard Company
Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005OEM Activation 2.0 Data-->
N/A
All Replies
-
Tuesday, 24 April, 2012 12:22 AMOwner
Have you tried the Activate by Phone process?
Thank you,
Darin MS
- Proposed As Answer by hassan issaBanned Tuesday, 24 April, 2012 3:56 PM
- Unproposed As Answer by Noel D PatonMicrosoft Community Contributor, Editor Tuesday, 24 April, 2012 9:34 PM
-
Tuesday, 24 April, 2012 12:37 AMYes. My current theory is that the XP key stuck to the machine isn't recognised by Microsoft because they expect this machine to be installed using the OEM's special install CD which looks for the preactivated BIOS. I heard somewhere that Microsoft decided not to accept product keys from OEM stickers on these machines as you should never need to enter them. Unless, like me, you no longer have the manufacturer's CD, only a generic XP OEM CD.
-
Tuesday, 24 April, 2012 3:27 PMAnswererTry using the Windows XP Product Key Update Tool. You may still have to "activate by phone".
Carey Frisch
-
Tuesday, 24 April, 2012 6:56 PMModerator"tjfs" wrote in message news:1aa73a74-6ea3-403f-be9e-58c66656657d...
Microsoft Support confirm my product key (on COA sticker attached to PC) is genuine. I am using an XP OEM CD.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Not Activated
Validation Code: 1
Cached Validation Code: N/A
Windows Product Key: *****-*****-XD49X-28Y9R-HB2GT
Windows Product Key Hash: Y4w6nslkak7wEiGSx9Hq5V4u3oQ=
Windows Product ID: 51882-OEM-2266525-54742
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 5.1.2600.2.00010100.3.0.pro
Other data-->
SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq dc7600 Small Form Factor</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>786D1 v01.61</Version><SMBIOSVersion major="2" minor="4"/><Date>20090701000000.000000+000</Date></BIOSOEM Activation 1.0 Data-->
BIOS string matches: yes
Marker string from BIOS: 8619:Compaq Computer Corporation|116FC:Compaq Computer Corporation|1FFEA:Compaq Computer Corporation|E618:Compaq Computer Corporation|11723:Compaq Computer Corporation|11723:Compaq Computer Corporation|1FFEA:Hewlett-Packard Company|E618:Hewlett-Packard Company
Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005For what version and edition of Windows is your PC licensed, according to the COA sticker on the case??The machine appears to be a Compaq - which would have normally come (given the date of the BIOS) with Vista installed.You say that MS confirmed that your Key is valid - but for which version of Windows?Does the Key you have entered agree with the Key in the report?
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Proposed As Answer by hassan issaBanned Wednesday, 25 April, 2012 9:20 PM
- Unproposed As Answer by Carey FrischMVP, Editor Thursday, 26 April, 2012 5:19 PM
-
Wednesday, 25 April, 2012 10:19 PMI think I've sorted this out now. The PC is an HP model which has a specific XP restore CD. It looks as if the generic XP OEM CD I used doesn't work with the key on the sticker. If you use the specific restore CD then it never asks for a key as it relies on a string in the BIOS instead.
-
Wednesday, 25 April, 2012 10:35 PMModeratorPlease post a new MGADiag report so that we can check the system is properly activated
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
-
Wednesday, 25 April, 2012 10:41 PMDiagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Genuine
Validation Code: 0
Cached Validation Code: N/A
Windows Product Key: *****-*****-2MDY9-F6J9M-K42BQ
Windows Product Key Hash: jY+nlE0RT38EEXpeUqSdQPABSQc=
Windows Product ID: 76487-OEM-2211906-00101
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 5.1.2600.2.00010100.3.0.pro
ID: {EF12281E-133F-4454-891F-F885E7427151}(3)
Is Admin: No
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.40.0
Signed By: Microsoft
Product Name: N/A
Architecture: N/A
Build lab: N/A
TTS Error: N/A
Validation Diagnostic: 025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A
Version: N/A
Windows XP Notifications Data-->
Cached Result: 0
File Exists: Yes
Version: 1.9.40.0
WgaTray.exe Signed By: Microsoft
WgaLogon.dll Signed By: Microsoft
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-543-80070002_025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{EF12281E-133F-4454-891F-F885E7427151}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-K42BQ</PKey><PID>76487-OEM-2211906-00101</PID><PIDType>2</PIDType><SID>S-1-5-21-1614895754-484763869-1801674531</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq dc7600 Small Form Factor</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>786D1 v01.61</Version><SMBIOSVersion major="2" minor="4"/><Date>20090701000000.000000+000</Date><SLPBIOS>Compaq,Hewlett,Hewlett,Compaq</SLPBIOS></BIOS><HWID>1F603F7F0184E066</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.9.40.0"/><File Name="WgaLogon.dll" Version="1.9.40.0"/></GANotification></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>
Licensing Data-->
N/A
Windows Activation Technologies-->
N/A
HWID Data-->
N/A
OEM Activation 1.0 Data-->
BIOS string matches: N/A
Marker string from BIOS: N/A, hr = 0x80004005
Marker string from OEMBIOS.DAT: Compaq,Hewlett,Hewlett,Compaq
OEM Activation 2.0 Data-->
N/A -
Wednesday, 25 April, 2012 11:06 PMModerator"tjfs" wrote in message news:b213b9e6-923d-4171-8936-17bd8f3dd7d3...Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Genuine
Validation Code: 0
Cached Validation Code: N/A
Windows Product Key: *****-*****-2MDY9-F6J9M-K42BQ
Windows Product Key Hash: jY+nlE0RT38EEXpeUqSdQPABSQc=
Windows Product ID: 76487-OEM-2211906-00101
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 5.1.2600.2.00010100.3.0.pro
Other data-->
SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq dc7600 Small Form Factor</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>786D1 v01.61</Version><SMBIOSVersion major="2" minor="4"/><Date>20090701000000.000000+000</Date><SLPBIOS>Compaq,Hewlett,Hewlett,Compaq</SLPBIOS></BIOS
OEM Activation 1.0 Data-->
BIOS string matches: N/A
Marker string from BIOS: N/A, hr = 0x80004005
Marker string from OEMBIOS.DAT: Compaq,Hewlett,Hewlett,Compaq
Compare the OEM Activation with your original one....OEM Activation 1.0 Data-->
BIOS string matches: yes
Marker string from BIOS: 8619:Compaq Computer Corporation|116FC:Compaq Computer Corporation|1FFEA:Compaq Computer Corporation|E618:Compaq Computer Corporation|11723:Compaq Computer Corporation|11723:Compaq Computer Corporation|1FFEA:Hewlett-Packard Company|E618:Hewlett-Packard Company
Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005ONE of them is very definitely non-genuine.
The original install at least admitted to not having an OEMBIOS.DAT file (an OEM System Builder shouldn't have one)- which probably means that it was genuine.
An OEM_SLP Key should only activate when the BIOS string and OEMBIOS.DAT data match. This one has somehow 'lost' the BIOS ID, but has still self-activated.
This would imply that an activation exploit has been installed to circumvent activation and validation requirements.
This installation would therefore be non-genuine.
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth -
Wednesday, 25 April, 2012 11:08 PM
I assure you I have used no hacks at all. I hoped that I could activate a standard XP OEM install with the key stuck to the unit, which I'm sure is genuine, but it seems that doesn't work despite Microsoft Support confirming with me that it's a genuine OEM key. Using the HP XP OEM CD does the job.
Thank you for your help.
-
Wednesday, 25 April, 2012 11:22 PMModerator
I've asked someone with more in-depth experience of XP WGA problem than me to have a look at the thread, and offer an opinion - hopefully he'll be able to see something (or maybe Darin, the forum owner, will be able to).
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
-
Wednesday, 25 April, 2012 11:31 PM
From the Wiki article at http://en.wikipedia.org/wiki/System_Locked_Pre-installation
"The product key printed on the Certificate of Authenticity affixed to an OEM assembled is sometimes said to suffice, but this is not necessarily the case. On February 28, 2005, Microsoft attempted to reduce software piracy by invalidating those keys for normal activation"
See also http://betanews.com/2005/02/24/microsoft-closes-activation-loophole/
-
Wednesday, 25 April, 2012 11:42 PMModerator
That's not the whole story, though.
Those Keys are still valid - but the first time they are used, they require Telephone activation. After that, internet activation suffices.
If they were already activated at that date, internet activation would still work.
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
-
Thursday, 26 April, 2012 3:19 PM
I agree with Noel that there is something unusual going on.
The first installation was a systembuilder/OEM product key for XP Pro used with a systembuilder/OEM installation disc, which yielded a standard systembuilder/OEM installaton which should have activated just fine using automatic activation or as Darin suggested, Telephonic activation. The OP never offered specifics about what happened when s/he tried to activate.
The second installation was a Compaq SLP Product key for XP Pro used with a Compaq recovery disc for XP Pro which yielded a typical Comapq SLP installation with the expected PID as well. But, since there appears to be no detection of the Compaq BIOS string and/or certificate, this installation should not self-activate. It should activate with the use of the Product Key on the CoA using the PK updater, but then the status of the license type should have changed to reflect CoA.
Given the available details, I would tend to go with Noel's opinion that an exploit of some type may have been used. OTOH, it appears that the final result is a Compaq XP Pro license activated on a Compaq computer, so while the journey to such might have been open to debate vis-a-vis whether legitimate means were used, the end result seems to be "kosher" :-)
- Edited by Dan at IT Associates Thursday, 26 April, 2012 3:20 PM
-
Thursday, 26 April, 2012 3:31 PM
I assure you that no exploit of any kind has been used, and the hard disk has been wiped in between installations. The first install didn't activate, and when I telephoned the representative told me that it was a valid key but he couldn't advise me why it wouldn't activate. The second install was done using a HP/Compaq OEM XP install disk and proceeded without asking for a product key. msoobe /a says Windows is activated. I have also sent you the output from MGAdiag which also says it's Genuine. It also passes the online genuine check and downloads MSE without difficulty.
As far as I can see I've followed all the rules and I now have a genuine installation. I am not sure why Microsoft make the process so difficult, or why they could not activate the key attached to the CPU, but I'm glad that I have a working PC now.
Tim