Answered by:
Windows 7 Failed Validation

Question
-
The validation message began showing up this morning. The laptop I am using was upgraded to Windows 7 almost a year ago, though a month ago I reinstalled Windows after a system failure.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-BJD6C-K3YVH-DVQJG
Windows Product Key Hash: WFqPPaNJ0hrc3E/8MgITJa2Xf0M=
Windows Product ID: 00359-OEM-8992687-00118
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7600.2.00010300.0.0.003
ID: {23843DC1-1E31-4723-B4AA-98CBF4A6A215}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7600.win7_gdr.100618-1621
TTS Error:
Validation Diagnostic:
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
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: 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 (x86)\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>{23843DC1-1E31-4723-B4AA-98CBF4A6A215}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-DVQJG</PKey><PID>00359-OEM-8992687-00118</PID><PIDType>2</PIDType><SID>S-1-5-21-1725323601-3603795056-2548805827</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc. </Manufacturer><Model>K50IJ </Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>207 </Version><SMBIOSVersion major="2" minor="5"/><Date>20090508000000.000000+000</Date></BIOS><HWID>7CBB3607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>_ASUS_</OEMID><OEMTableID>Notebook</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7600.16385
Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800118-02-1033-7600.0000-2172009
Installation ID: 017440093584312686743613816130937676843374523213337575
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: DVQJG
License Status: Notification
Notification Reason: 0xC004F07C.
Remaining Windows rearm count: 2
Trusted time: 11/29/2010 8:59:59 AM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0xC004C533
HealthStatus: 0x0000000000000000
Event Time Stamp: 11:29:2010 08:54
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: MgAAAAEAAgABAAIAAAABAAAAAwABAAEAeqguUkZi0jN6fwKmhomUCZ6DCDAGO+qWRso=
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x0
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC 050809 APIC1447
FACP 050809 FACP1447
DBGP 050809 DBGP1447
HPET 050809 OEMHPET
BOOT 050809 BOOT1447
MCFG 050809 OEMMCFG
SLIC _ASUS_ Notebook
ECDT 050809 OEMECDT
OEMB 050809 OEMB1447
GSCI 050809 GMCHSCI
SSDT PmRef CpuPm
Monday, November 29, 2010 3:10 PM
Answers
-
"ColdWaterHeater" wrote in message news:f98a8071-7fb7-4b54-8847-69213aad0f4e...Alright, after going through the steps involving slui.exe in the other posts again(forgot to mention that, sorry), and reentering my product key, and encountering a few invalid messages, it finally agreed that the product key the manufacturer gave me was valid.
Why would a valid product key be considered invalid 4 different times when attempting to validate it(and yes, it was typed in correctly), then suddenly go through?
It can happen for a number of reasons - from your initial report, it looks as if you were having problems with the Licensing Store, which re-entering the product key would reset.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by Darin Smith MS Friday, December 3, 2010 12:36 AM
Tuesday, November 30, 2010 5:57 AMModerator
All replies
-
Alright, after going through the steps involving slui.exe in the other posts again(forgot to mention that, sorry), and reentering my product key, and encountering a few invalid messages, it finally agreed that the product key the manufacturer gave me was valid.
Why would a valid product key be considered invalid 4 different times when attempting to validate it(and yes, it was typed in correctly), then suddenly go through?Monday, November 29, 2010 4:23 PM -
"ColdWaterHeater" wrote in message news:f98a8071-7fb7-4b54-8847-69213aad0f4e...Alright, after going through the steps involving slui.exe in the other posts again(forgot to mention that, sorry), and reentering my product key, and encountering a few invalid messages, it finally agreed that the product key the manufacturer gave me was valid.
Why would a valid product key be considered invalid 4 different times when attempting to validate it(and yes, it was typed in correctly), then suddenly go through?
It can happen for a number of reasons - from your initial report, it looks as if you were having problems with the Licensing Store, which re-entering the product key would reset.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by Darin Smith MS Friday, December 3, 2010 12:36 AM
Tuesday, November 30, 2010 5:57 AMModerator