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

All replies

• 

  

  2

  Sign in to vote

  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 Frisch

  Monday, January 31, 2011 5:13 AM

  Moderator
• 

  

  0

  Sign in to vote

  "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 Windows

  http://www.microsoft.com/genuine/validate

  if 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 Sloth

  Monday, January 31, 2011 10:59 AM

  Moderator
• 

  

  1

  Sign in to vote

   

  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