Answered by:
My Windows 7 is not genuine???

Question
-
I got my daughter an eee pc from Asus and all was fine till I sent the computer away because it would not charge. Then a few months later the screen went black and stated my windows is not genuine. So contacted Asus who told me to factory reset it and it should be fine, so I did and it worked, then a few months later....guess what the same thing!!! Called Asus and they told me to reset it again..... told them no because it wont resolve the problem as this is what I did last time...asked them to come take it again and fix it and he told me if they took it, that is all they would do....cheeky or what. Anyway found this forum and was told to do some system check and copy and post my findings....
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->Validation Code: 50
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-KG794-FJYHG-YCJVG
Windows Product Key Hash: 4clElKz4x2Yzq4iiborX50Uv898=
Windows Product ID: 00342-OEM-8992752-30005
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7600.2.00010300.0.0.011
ID: {3D033E58-4079-47D2-8335-70A7D78F587F}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Starter
Architecture: 0x00000000
Build lab: 7600.win7_gdr.110408-1633
TTS Error:
Validation Diagnostic:
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002Windows 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: 102
Microsoft Office Home and Student 2007 - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_B4D0AA8B-920-80070057Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.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-->
File Mismatch: C:\windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
File Mismatch: C:\windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
File Mismatch: C:\windows\system32\wat\watux.exe[Hr = 0x80070003]
File Mismatch: C:\windows\system32\wat\watweb.dll[Hr = 0x80070003]Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{3D033E58-4079-47D2-8335-70A7D78F587F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.011</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-YCJVG</PKey><PID>00342-OEM-8992752-30005</PID><PIDType>2</PIDType><SID>S-1-5-21-3033720901-2872045933-1170363893</SID><SYSTEM><Manufacturer>ASUSTeK Computer INC.</Manufacturer><Model>1005HAG</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0301 </Version><SMBIOSVersion major="2" minor="5"/><Date>20091231000000.000000+000</Date></BIOS><HWID>E4B90600018400E4</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>102</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><PidType>19</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7600.16385Name: Windows(R) 7, Starter edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: 8be4a481-9b5c-4588-a5ec-5dad4b1f15da
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00342-00178-927-530005-02-1033-7600.0000-2792009
Installation ID: 020165083250184963232142045936829161644500295934097234
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: YCJVG
License Status: Notification
Notification Reason: 0xC004F057.
Remaining Windows rearm count: 2
Trusted time: 12/07/2011 11:52:42Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0xC004C533
HealthStatus: 0x0000000000000000
Event Time Stamp: 6:10:2011 21:20
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: LgAAAAAAAQABAAIAAAABAAAAAwABAAEAnJ82Rhh+BvWeb7xyRpBoz878FBByGQ==OEM Activation 1.0 Data-->
N/AOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC A_M_I_ OEMAPIC
FACP A_M_I_ OEMFACP
HPET A_M_I_ OEMHPET
MCFG A_M_I_ OEMMCFG
OEMB A_M_I_ AMI_OEM
SSDT PmRef CpuPm
Help anyone????Tuesday, July 12, 2011 11:03 AM
Answers
-
BIOS valid for OA 2.0: yes, but no SLIC table
You will have to change your product key to the one on your COA
click start
right click computer
select properties
scroll to the bottom of the page and select change product key
You will then have to activate by phone:
How to activate Windows 7 manually (activate by phone)
1) Click Start, and in the Search box type: slui.exe 4
2) Next press the 'ENTER' key
3) Select your 'Country' from the list.
4) Choose the 'Phone Activation' option.
5) Stay on the phone (do not select/press any options) and wait for a person to help you with activation.
6) Explain your problem clearly to the support person.
Additional information:
Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:
A) OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows 7 looks at the motherboard and sees the special instructions and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)
B) COA SLP: This is the Product key that you see on the sticker on the side (or bottom,[ or inside the battery compartment]) of your computer. It is a valid product key, but should only be used in limited situations (such as if the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone. (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer)
- Marked as answer by Darin Smith MS Tuesday, July 12, 2011 8:39 PM
Tuesday, July 12, 2011 12:42 PMAnswerer
All replies
-
BIOS valid for OA 2.0: yes, but no SLIC table
You will have to change your product key to the one on your COA
click start
right click computer
select properties
scroll to the bottom of the page and select change product key
You will then have to activate by phone:
How to activate Windows 7 manually (activate by phone)
1) Click Start, and in the Search box type: slui.exe 4
2) Next press the 'ENTER' key
3) Select your 'Country' from the list.
4) Choose the 'Phone Activation' option.
5) Stay on the phone (do not select/press any options) and wait for a person to help you with activation.
6) Explain your problem clearly to the support person.
Additional information:
Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:
A) OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows 7 looks at the motherboard and sees the special instructions and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)
B) COA SLP: This is the Product key that you see on the sticker on the side (or bottom,[ or inside the battery compartment]) of your computer. It is a valid product key, but should only be used in limited situations (such as if the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone. (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer)
- Marked as answer by Darin Smith MS Tuesday, July 12, 2011 8:39 PM
Tuesday, July 12, 2011 12:42 PMAnswerer -
Nice job! Very clean layout, informative and easy to understand. (Although you may want to explain what a CoA is and were to find it)
While it's basically the same information as I usually post for this type of issue, I may use this instead. It just seems to look and flow better then what I normally use.
Thanks george1009
Darin MSTuesday, July 12, 2011 8:44 PM -
Thanks Darin. I appreciate that. Still learning. I think I can identify almost all issues, however still struggling with proper solutions for many, especially software licensing service and software protection platform issues. I will get there but will take time. Thanks again,
George
Tuesday, July 12, 2011 8:54 PMAnswerer