Windows 7 Pro "Build 7601 this copy of windows is not genuine"

All replies

• 

  

  0

  Sign in to vote

   You need to change the Product Key to the one on the COA sticker on the machine's case (or inside the battery compartment),  using the Change Product Key link at the bottom of the System properties page.

   

  You may need to activate by phone.   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  Wednesday, May 1, 2013 7:27 PM

  Moderator
• 

  

  0

  Sign in to vote

  for whatever reason there is no product id on the case even under the battery - it seems typical with Win8 machines we sell from Lenovo but my assumption was this was microsoft not Lenovo making it be this way?

  Wednesday, May 1, 2013 7:38 PM
• 

  

  0

  Sign in to vote

  Windows 8 OEM Pre-installs don't need a product Key or COA sticker - the Key is built into the BIOS at manufacture.

  Even if they did have a Win8 sticker, it would not be valid for Windows 7 installs.

  If there's no CAO sticker, it would require a valid v2.1 SLIC table to be able to activate a Win7 OEM_SLP Key - which this machine doesn't have. (BIOS valid for OA 2.0: no, invalid SLIC table)

  If it shipped with Windows 8, there's a Windows 8 label on it - is it for Windows 8, or Windows 8 Pro? If it's not Pro, then it's not eligible for the downgrade anyhow.

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  Wednesday, May 1, 2013 7:45 PM

  Moderator
• 

  

  0

  Sign in to vote

  As my first line says (no offense meant) "It came with Win8 recovery media but Win7 was pre-installed"

  Many new Lenovo's show windows 8 pro but ship with Windows 7 pro (Thankfully)  It is perfectly legit as it came from Lenovo
  

  I'm hoping we can get this resolved and have no further issues like this- if many of these that shipped with 8 and have 7 pre-installed do this we will have a real mess

  What can I do?

  Wednesday, May 1, 2013 7:54 PM
• 

  

  0

  Sign in to vote

  I never said it wasn't genuine :)

  Is the sticker for Win 8 or Win 8 Pro?

  There are really only two options

  1) attempt a reinstall using Lenovo Windows 7 recovery media

  2) contact Lenovo for assistance - it's their BIOS which has broken down if #1 fails.

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  Wednesday, May 1, 2013 8:00 PM

  Moderator
• 

  

  0

  Sign in to vote

  It's their BIOS but the Lenovo tech I spoke with first thing this morning said it was a M$ issue as it is happening with Dell, HP, and others as well.  If I do a reinstall with recovery media why would it be any different than it is now when it came with Windows 7 and was fine til recently? It was stated on multiple websites that M$ Windows update KB971033 causes this error but uninstalling it made no difference
  

  If M$ got paid to allow Windows be sold on this Lenovo unit (and we know they did) and we have no way to see/find the key that was purchased to license Windows to this machine then clearly this whole licensing concept is very flawed.  I am not at all enthusiastic about the possibility of having to deal with this on a regular basis and the end users and the service providers like us are the ones who will pay the price.  As prevalent as this issue is already it seems there needs to be some real thought given to get this process working correctly.  My client has hours in getting all his applications setup and we have hours in trying to get a M$ product to quit interfering with the operation of the system when the software is totally legitimate.
  

  Wednesday, May 1, 2013 8:15 PM
• 

  

  0

  Sign in to vote

  The basic problem is that the system is unable to properly read the SLIC table.

  This means one of two things.

  Either the SLIC table itself is damaged - in which case it's a hardware/firmware issue and not software, and therefore it's Lenovo's problem no matter what they like to say - or it's because of system corruption, in which case a reinstall from proper recovery media will fix it.

  Experience from these forums over the past three years is that the error you have is caused by the BIOS SLIC table rather than software.

  I know for a fact that Lenovo went through a patch where they shipped machines without the proper Win8 BIOS tables and Key - and had to recall them all as a result, since the Product Key is embedded at manufacture and can't be added later

  It's possible that for Windows 7 they have released a BIOS patch that would work - it's unlikely to be posted on their site, but it's always worth a try.

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  • Proposed as answer by Noel D PatonModerator Saturday, May 4, 2013 10:10 AM
  • Marked as answer by Noel D PatonModerator Saturday, May 11, 2013 4:04 PM

  Wednesday, May 1, 2013 8:50 PM

  Moderator
• 

  

  0

  Sign in to vote

  I have been on the phone with Lenovo for 30 minutes and they claim if I do a new install of Win7 it will be ok.  The MGAdiag reports the SLIC which is in the BIOS as the culprit so again even if i run thru this will it fail immediately or will it go for a period of time before it is an issue again?  I will attempt a re-image on a clean hard drive so as not to jeopardize the clients documents, pictures and general setup as he runs various programs on the network at his office.  THanks for your assistance- I will report back
  

  Wednesday, May 1, 2013 9:32 PM
• 

  

  0

  Sign in to vote

  If you do the reinstall, using Lenovo Recovery media for Windows 7, it will show as genuine for a period - if you then run MGADiag again, and check the SLIC table in that, it will tell you whether the table is OK or not (I'm prepared to lay odds on it still being bad).

  If you want a second opinion, feel free to post the report.

  If the SLIC is OK, then hopefully it will stay that way.

  If the SLIC still shows as Invalid, then the problem is firmware - and Lenovo's responsibility.

  If you use other media for the install, it will still show as genuine for a period, but will be un-activatable without entering a COA or Retail Key - it should still be sufficient to check the SLIC table.

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  Wednesday, May 1, 2013 9:46 PM

  Moderator
• 

  

  0

  Sign in to vote

  Ran clean install from Lenovo Recovery Media for another Lenovo notebook- the drivers are not in place yet as they are downloading SLOW but I ran the MGAdiag and got this.  Maybe it must go online? Still says invalid SLIC table
  

  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  
  Validation Code: 0
  Cached Online Validation Code: N/A, hr = 0xc004f012
  Windows Product Key: *****-*****-MV8MH-98QJM-24367
  Windows Product Key Hash: wgci5Gdejx4esg7++zTOe3LWF+4=
  Windows Product ID: 55041-OEM-8992671-00437
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  Windows OS version: 6.1.7601.2.00010100.1.0.048
  ID: {FB6B2A7B-1779-4716-86A7-A4AEE81B3355}(1)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows 7 Professional
  Architecture: 0x00000009
  Build lab: 7601.win7sp1_gdr.110407-1603
  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:
  User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
  Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.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-->
  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>{FB6B2A7B-1779-4716-86A7-A4AEE81B3355}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-24367</PKey><PID>55041-OEM-8992671-00437</PID><PIDType>2</PIDType><SID>S-1-5-21-4168714422-799752586-4193365905</SID><SYSTEM><Manufacturer>LENOVO</Manufacturer><Model>62724GU</Model></SYSTEM><BIOS><Manufacturer>LENOVO</Manufacturer><Version>H0ET91WW (2.51 )</Version><SMBIOSVersion major="2" minor="7"/><Date>20130227000000.000000+000</Date></BIOS><HWID>64183207018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>LENOVO</OEMID><OEMTableID>TP-H0   </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.7601.17514
  
  Name: Windows(R) 7, Professional edition
  Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
  Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 00371-00178-926-700437-02-1033-7601.0000-0462011
  Installation ID: 007066631342184204217854503435023263242432164372491713
  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: 24367
  License Status: Initial grace period
  Time remaining: 43200 minute(s) (30 day(s))
  Remaining Windows rearm count: 2
  Trusted time: 5/2/2013 10:05:34 AM
  
  Windows Activation Technologies-->
  HrOffline: 0x00000000
  HrOnline: N/A
  HealthStatus: 0x0000000000000000
  Event Time Stamp: N/A
  ActiveX: Not Registered - 0x80040154
  Admin Service: Not Registered - 0x80040154
  HealthStatus Bitmask Output:
  
  
  HWID Data-->
  HWID Hash Current: LAAAAAEAAgABAAEAAAACAAAAAAABAAEA6GHS+WCpMCAcL1DkKOo+/fxFlmM=
  
  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            LENOVO        TP-H0   
    FACP            LENOVO        TP-H0   
    HPET            LENOVO        TP-H0   
    MCFG            LENOVO        TP-H0   
    SLIC            LENOVO        TP-H0   
    SSDT            LENOVO        SataAhci
    SSDT            LENOVO        SataAhci
    ASF!            LENOVO        TP-H0   
    FPDT            LENOVO        TP-H0   
    SSDT            LENOVO        SataAhci
    SSDT            LENOVO        SataAhci
    UEFI            LENOVO        TP-H0   
    UEFI            LENOVO        TP-H0   
    POAT            LENOVO        TP-H0   
    UEFI            LENOVO        TP-H0   
    DBG2            LENOVO        TP-H0   
  
  

  Thursday, May 2, 2013 2:54 PM
• 

  

  0

  Sign in to vote

  Installed drivers to go online and have Windows Updates installing- I want to test to see if it will be ok now or if it will go back to "not genuine" and the invalid SLIC table in the MGAdiag seems to see it will be NOT GENUINE again?
  

  Thursday, May 2, 2013 3:49 PM
• 

  

  0

  Sign in to vote

  The indications are that it still has a bad SLIC table -

  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: no, invalid SLIC table

  It's a firmware problem, which only Lenovo can resolve.

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  • Marked as answer by ItsMeAgain66 Monday, May 13, 2013 8:42 PM

  Thursday, May 2, 2013 9:33 PM

  Moderator
• 

  

  0

  Sign in to vote

  To force the issue I went to "Activate Windows Now" and as you expected it came back with "The Windows 7 Professional Product Key that you typed is invalid for activation"  I'll be calling Lenovo again this morning.  Thanks Noel.  This concept seems like one of the many brilliant ideas that are poorly executed.  Having the code in the BIOS is OK as long as it works.
  

  Friday, May 3, 2013 11:21 AM
• 

  

  0

  Sign in to vote

  sorry for the delay- was out for a while.  Lenovo has been a pain on this one and we returned the machine a week ago after doing a clean install here to no avail.  They insist that if they re-image the notebook it will be fine.  We are to get the unit back in our hands on Wednesday of this week so we will run the mgadiag.exe immediately and see what it says.  I figure that Windows is M$ and if the M$ tool says "invalid SLIC table" we are in for more grief.  We will see soon.

  Monday, May 13, 2013 8:45 PM
• 

  

  0

  Sign in to vote

  I'll agree with your analysis there :)
  

  I'll await the results with bated (but not held) breath!

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  Tuesday, May 14, 2013 8:45 PM

  Moderator
• 

  

  0

  Sign in to vote

  Ok Lenovo did better than they promised (on the delivery date) and FedEx brought the notebook back today.  Ran MGAdiag right off the bat and got the following:

  (actually I scaled it back and this is the part we got in trouble with before)

  BIOS valid for OA 2.0: yes

  In place of a simple YES was the NO, Invalid SLIC Table prior to the service
  

  The client has M$ Office and multiple other applications setup as it was also configured to access resources on our client's network.  The machine was in fact re-imaged and we attempted to boot the unit on the copy of the drive as it was prior to going in for repair service.  The unit failed to boot and gave a "signature error".  We did a repair of the boot sector and got into Windows but were unsuccessful at changing the Windows Key in the original install to match what we pulled from the BIOS with a key viewer so the additional configuration needed to use the notebook will have to be redone.As dangerous as ASSuME is shall it suffice to say that when MGAdiag reports BIOS valid for OA 2.0: yes we are not likely to experience issues with Windows being tagged as NOT GENUINE?

  Tuesday, May 14, 2013 9:02 PM
• 

  

  0

  Sign in to vote

  There's actually a second and third line there which need checking (but doesn't usually cause too many problems if the first is right)...

  BIOS valid for OA 2.0: yes
  Windows marker version: 0x20001
  OEMID and OEMTableID Consistent: yes

  The second indicates that the SLIC table is for Windows7

  The third that the SLIC table is for the same manufacturer as the installed OS was built by/for.

  Assuming that all three show as above then hopefully, there should be no further problems.

  Did Lenovo eventually agree that they had to reflash the BIOS (or change the BIOS chip)?

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  No - I do not work for Microsoft, or any of its contractors.

  Wednesday, May 15, 2013 7:39 AM

  Moderator