Answered by:
Windows 7 Build 7600 This copy of Windows is not genuine product key isn't working

Question
-
I bought my Laptop around a year ago at Fry's Electronics, and just today I get this message on my Desktop background saying "Windows 7 Build 7600 This copy of Windows is not genuine." Later I tried typing in my Product Key - and it didn't work
If I need to add anything else to this post, please tell me thanks.
Thanks, Kevin
I did what you told me to Noel, this is the results
Oh, and I'm using Panda Antivirus Pro 2011.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-4F8HK-M4P73-W8DQG
Windows Product Key Hash: Xs1iQgVeo0C+sObJxS7eu+FuBPQ=
Windows Product ID: 00359-OEM-8992687-00057
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7600.2.00010300.0.0.003
ID: {D0D80D23-AED2-4391-A095-EFA074C33CEB}(3)
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: 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-80070057
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Mozilla Firefox 4.0 Beta 10\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>{D0D80D23-AED2-4391-A095-EFA074C33CEB}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-W8DQG</PKey><PID>00359-OEM-8992687-00057</PID><PIDType>2</PIDType><SID>S-1-5-21-2727214545-3867784817-674875845</SID><SYSTEM><Manufacturer/></SYSTEM><BIOS><Manufacturer>INSYDE</Manufacturer><Version>1.10</Version><SMBIOSVersion major="2" minor="6"/><Date>20091126000000.000000+000</Date></BIOS><HWID>B1B83607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>US Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></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.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-800057-02-1033-7600.0000-3202009
Installation ID: 010885517642033991117725149041979336646732193691042014
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: W8DQG
License Status: Notification
Notification Reason: 0xC004F059.
Remaining Windows rearm count: 2
Trusted time: 1/31/2011 1:03:19 PM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x8004FE90
HealthStatus: 0x0000000000000000
Event Time Stamp: 1:31:2011 13:01
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: LAAAAAEAAQABAAEAAAABAAAAAgABAAEA6GE+AwLfCJ/u4QhuMqIwg85eXF0=
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC TOSINV TOSINV00
FACP TOSINV TOSINV00
HPET TOSINV TOSINV00
BOOT TOSINV TOSINV00
MCFG TOSINV TOSINV00
WDAT INTEL Calpella
ASF! TOSINV TOSINV00
SLIC TOSINV TOSINV00
SSDT INTEL SataAhci
ASPT INTEL Calpella
SSDT INTEL SataAhci
- Edited by KevinDelay Monday, January 31, 2011 9:30 PM
Monday, January 31, 2011 4:07 AM
Answers
-
1) The first error 0xC004F059 suggests that the issue is Activation related. At this point, this doesn't tell us allot.
2) My list of hrOnline error codes doesn't contain 0x8004FE90 . My Devs tell me that when that happens it means the particular error is not directly causing the Non-Genuine issue. I have my doubts about that but for now, lets assume that this error is not the cause of this issue.
3) BIOS valid for OA 2.0: no, invalid SLIC table This error message combined with error 1) above, tells us that the issue (or at least part of the issue) is that the OEM SLP key is unable to see the OEM Bios flag so is unable to self-activate.
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 OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) 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) of your computer. It is a valid product key, but should only be used in limited situations (sush 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)
Your Windows is using an OEM SLP key, but (for whatever reason) cannot see the OEM Bios Flag in the computer’s motherboard and is unable to Self-Activate.To fix the issue, you will need to change out the OEM SLP key with the COA SLP key. The normal way to do this is to click the ‘Start’ button, right-click ‘Computer’, select ‘Properties’ and then click ‘Change Product Key’ (located in the lower right-hand side of the window). Enter the COA SLP key and follow the instructions in the Change Product Key Wizard. After this use the Activate by Phone process to activate the new key.
Once you are done changing the Product Key and have activated it, the issue should be resolved. However if it isn't, run a new Diagnostic Report and post it here so we can see what has changed.
Thank you,
Darin MS- Proposed as answer by Darin Smith MS Monday, January 31, 2011 9:11 PM
- Marked as answer by Darin Smith MS Wednesday, February 2, 2011 9:45 PM
Monday, January 31, 2011 9:08 PM
All replies
-
To help us analyze and troubleshoot a non-genuine notification issue you may be experiencing, please download and run the Microsoft Genuine Advantage Diagnostics Tool.
Once you run the tool, click on the Continue button, then click on the Copy button and Paste the report into your post, along with your question.
Thank you!
Carey FrischMonday, January 31, 2011 5:13 AMModerator -
"KevinDelay" wrote in message news:09914e24-30a0-4a5e-a251-db47366bac47...
I bought my Laptop around a year ago at Fry's Electronics, and just today I get this message on my Desktop background saying "Windows 7 Build 7600 This copy of Windows is not genuine." Later I tried typing in my Product Key - and it didn't work
If I need to add anything else to this post, please tell me thanks.
Thanks, Kevin
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-4F8HK-M4P73-W8DQG
Windows Product Key Hash: Xs1iQgVeo0C+sObJxS7eu+FuBPQ=
Windows Product ID: 00359-OEM-8992687-00057
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7600.2.00010300.0.0.003
Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Partial Product Key: W8DQG
License Status: Notification
Notification Reason: 0xC004F059.
Remaining Windows rearm count: 2
Trusted time: 1/30/2011 10:55:40 PM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x8004FE90
HealthStatus: 0x0000000000000000
Event Time Stamp: 1:30:2011 22:51
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
There are two errors there - one of them I don't remember seeing before (0x8004FE90), which apparently means 'cannot find script file'What Anti-Virus are you using?Try going to the Validation site to validate Windowsif it fails, you should be offered the diagnostics(direct link - http://www.microsoft.com/geniune/diag )take that and see what it has to say - try the repair methods offered, once once you get 'all green' try to validate again. (it may well still fail because of your other error)Then post back with a new MGADiag report, and your results
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothMonday, January 31, 2011 10:59 AMModerator -
1) The first error 0xC004F059 suggests that the issue is Activation related. At this point, this doesn't tell us allot.
2) My list of hrOnline error codes doesn't contain 0x8004FE90 . My Devs tell me that when that happens it means the particular error is not directly causing the Non-Genuine issue. I have my doubts about that but for now, lets assume that this error is not the cause of this issue.
3) BIOS valid for OA 2.0: no, invalid SLIC table This error message combined with error 1) above, tells us that the issue (or at least part of the issue) is that the OEM SLP key is unable to see the OEM Bios flag so is unable to self-activate.
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 OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) 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) of your computer. It is a valid product key, but should only be used in limited situations (sush 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)
Your Windows is using an OEM SLP key, but (for whatever reason) cannot see the OEM Bios Flag in the computer’s motherboard and is unable to Self-Activate.To fix the issue, you will need to change out the OEM SLP key with the COA SLP key. The normal way to do this is to click the ‘Start’ button, right-click ‘Computer’, select ‘Properties’ and then click ‘Change Product Key’ (located in the lower right-hand side of the window). Enter the COA SLP key and follow the instructions in the Change Product Key Wizard. After this use the Activate by Phone process to activate the new key.
Once you are done changing the Product Key and have activated it, the issue should be resolved. However if it isn't, run a new Diagnostic Report and post it here so we can see what has changed.
Thank you,
Darin MS- Proposed as answer by Darin Smith MS Monday, January 31, 2011 9:11 PM
- Marked as answer by Darin Smith MS Wednesday, February 2, 2011 9:45 PM
Monday, January 31, 2011 9:08 PM