Answered by:
Vista reactivation issue
Question
-
0. Laptop crashed - restart said Windows had changed
1. Product key re-entered from sticker
2. Followed on line activation but will not re-activate - inuse message
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Invalid License
Validation Code: 50
Cached Online Validation Code: 0xc004c4a8
Windows Product Key: *****-*****-R8X7W-K3JK9-TG2P9
Windows Product Key Hash: kKDtC3z3qS/7g/mCW+Wp/SGC/1k=
Windows Product ID: 89576-OEM-7202665-27661
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.0.6002.2.00010100.2.0.006
ID: {F3FF37C3-7843-4BCB-AB65-2EC0ABF05084}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: Windows Vista (TM) Business
Architecture: 0x00000000
Build lab: 6002.vistasp2_gdr.100608-0458
TTS Error: T:20101204095943592-
Validation Diagnostic:
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: 6.0.6002.16398
Windows 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 = 0x80070002
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-604-645_B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Mozilla Firefox\firefox.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>{F3FF37C3-7843-4BCB-AB65-2EC0ABF05084}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010100.2.0.006</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-TG2P9</PKey><PID>89576-OEM-7202665-27661</PID><PIDType>8</PIDType><SID>S-1-5-21-1720490537-2585126208-3180209284</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq 6720s</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>68MDU Ver. F.09</Version><SMBIOSVersion major="2" minor="4"/><Date>20080110000000.000000+000</Date></BIOS><HWID>58323507018400FA</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><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>
Spsys.log Content: U1BMRwEAAAAAAQAABAAAAIUHAAAAAAAAYWECAOSfhqs0UFv2mZPLASPvOhE4aiPWkIrToHXwxdonqXjfBAKlale8ulLyUcxy5vvejoxi1bdOjW8Pfd/MZjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw2LChCixnhclyLKxemNGWeKAXTXyXos2HZ7TJbPe3ZHXmb9XQt68JDS42no7EJYLczkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM
Licensing Data-->
Software licensing service version: 6.0.6002.18005
Name: Windows(TM) Vista, Business edition
Description: Windows Operating System - Vista, OEM_COA_SLP channel
Activation ID: f758e09b-7c7c-492c-b78c-aba5bd4e3f5b
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 89576-00144-026-627661-02-2057-6002.0000-3382010
Installation ID: 021833750346297903180153691420138814005396428826234625
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
Partial Product Key: TG2P9
License Status: Unlicensed
Windows Activation Technologies-->
N/A
HWID Data-->
HWID Hash Current: OAAAAAEAAwABAAIAAgABAAAAAwABAAEAJJRcuhTBvg1wokaDxKySveSRje/y9Lww9FO8qaxWKoU=
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20000
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC HP 30D8
FACP HP 30D8
HPET HP 30D8
MCFG HP 30D8
SLIC HPQOEM SLIC-MPC
TCPA HP 30D8
SSDT HP HPQSAT
SSDT HP HPQSAT
SSDT HP HPQSAT
SSDT HP HPQSAT
SSDT HP HPQSAT
Saturday, December 4, 2010 12:09 PM
Answers
-
"JohnBognor" wrote in message news:22d4f13b-04c7-45a9-b36f-f6012d5a8f59...
0. Laptop crashed - restart said Windows had changed
1. Product key re-entered from sticker
2. Followed on line activation but will not re-activate - inuse message
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Invalid License
Validation Code: 50
Cached Online Validation Code: 0xc004c4a8
Windows Product Key: *****-*****-R8X7W-K3JK9-TG2P9
Windows Product Key Hash: kKDtC3z3qS/7g/mCW+Wp/SGC/1k=
Windows Product ID: 89576-OEM-7202665-27661
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.0.6002.2.00010100.2.0.006
ID: {F3FF37C3-7843-4BCB-AB65-2EC0ABF05084}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: Windows Vista (TM) Business
Architecture: 0x00000000
Build lab: 6002.vistasp2_gdr.100608-0458
TTS Error: T:20101204095943592-
Validation Diagnostic:
Resolution Status: N/A
You havea problem which needs to be fixed before you will be able to activate - a Trusted Store Tamper (which is probably what caused the problem in the first place).to quote Darin.....
<quote>
You have a T-type Tamper present on your machine, which is preventing proper self-activation.
Your Diagnostic Report is telling me that your Windows is suffering from a Trusted Store Tamper. In Windows, there are files that have, what is known as, a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source. If a file is modified, in any way, the Digital Signature is broken.
Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source (HP) a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way, it's Digital Signature is broken and becomes invalid. So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.
What I have described in the above example is basically what is happening with your Windows. Some Digitally Signed file has been modified in some way and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) which invalidates the Certificate in the Trusted Store and that is what has triggered the Non-Genuine messaging.
Unfortunately, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.
1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occur the most with Drivers. So my first suggestion is to confirm that all your hardware drivers are up to date. Note: Figuring out id a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seek assistance or skip down to #2 or #3 below
2) Restore Windows back to a past System Restore Point.
1) Boot into Windows
2) Click the Start button
3) In the Start Search field, type: System Restore and hit the Enter key
4) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to a date Before you first noticed the issue (8th October, I suspect).
5) Click the "Next" button.
6) Reboot
3) Repair Windows using the 'sfc /scannow' command
The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)
1) Login to Windows
2) Click the Start button
3) Type: cmd.exe in the search field
4) Right-click the cmd.exe file and select Run as Administrator
5) In the CMD window, type: sfc /scannow
6) Reboot and see if that resolves the issue.
If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Windows.
</quote>
In your case, once the T-type tamper is fixed, you will have to activate Windows by phone
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by Darin Smith MS Tuesday, December 7, 2010 12:12 AM
Saturday, December 4, 2010 1:34 PMModerator
