Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows 7- Build 7600 - This copy of windows is not genuine RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have read many of the questions similar to this, but most I saw turned out to be situations like, "I bought this pc used from xxx". 

    I work in the IT deparment of a private career college.  We buy our machines direct from DakTech. Sporadically, a machine will come up with this error.  To date I have been successful fixing them using the "net stop spssvc ... rename tokens.bat ... net start spssvc ... slui.exe 3"

    So far no machine has had this issue a second time.  All so have been on one particular architecture (an Intel DG41RQ system board).  Machines were purchased since 6/2010.

    This -seems- to be happening with increasing frequency.

    I have opened a help ticket with DakTech, and they have not heard of this issue from other users, at least yet.

    Is there anything I can do to stop this from happening?  It makes our school look bad when students see messages implying that we are using counterfeit copies of Windows...

    Thanks!

    Joel.

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-FTKYK-QBVD7-9DXH8
    Windows Product Key Hash: cXz+3RtDw80mocW4G4KBEKFrO8Q=
    Windows Product ID: 00371-OEM-8992671-00288
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {03876FF6-69DB-4540-A04B-BB960AE86B3E}(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: 7600.win7_gdr.101026-1503
    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: 100 Genuine
    Microsoft Office Professional Plus 2007 - 100 Genuine
    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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\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: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{03876FF6-69DB-4540-A04B-BB960AE86B3E}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-9DXH8</PKey><PID>00371-OEM-8992671-00288</PID><PIDType>2</PIDType><SID>S-1-5-21-505850852-2834682140-1434730464</SID><SYSTEM><Manufacturer>DakTech</Manufacturer><Model>DG41RQ</Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>RQG4110H.86A.0013.2009.1223.1136</Version><SMBIOSVersion major="2" minor="4"/><Date>20091223000000.000000+000</Date></BIOS><HWID>DEB93607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Plus 2007</Name><Ver>12</Ver><Val>4AABF62A9AED86</Val><Hash>i0O8wtXTI/gLm33cno6TWgOr9RI=</Hash><Pid>89409-707-6100905-65565</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" 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, 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-700288-02-1033-7600.0000-3652007
    Installation ID: 005064631710445313713410032621345345459276380053702830
    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: 9DXH8
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 3
    Trusted time: 4/14/2011 12:03:48 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 4:3:2011 18:23
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MgAAAAEABAABAAIAAAABAAAAAQABAAEA6GFEMagYmLtI5Kp2brIEX7AvznBsTxSoRso=

    OEM Activation 1.0 Data-->
    N/A

    OEM 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            INTEL         DG41RQ  
      FACP            INTEL        DG41RQ
      HPET            INTEL         DG41RQ  
      MCFG            INTEL         DG41RQ  


     

    Thursday, April 14, 2011 8:38 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Did changing the Product Key to the CoA key resolve the issue?
    Darin MS
    Friday, April 15, 2011 10:42 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    "Joel Alpers" wrote in message news:a40d6b81-f619-418f-9e8c-972362a0a4b5...

    I have read many of the questions similar to this, but most I saw turned out to be situations like, "I bought this pc used from xxx". 

    I work in the IT deparment of a private career college.  We buy our machines direct from DakTech. Sporadically, a machine will come up with this error.  To date I have been successful fixing them using the "net stop spssvc ... rename tokens.bat ... net start spssvc ... slui.exe 3"

    So far no machine has had this issue a second time.  All so have been on one particular architecture (an Intel DG41RQ system board).  Machines were purchased since 6/2010.

    This -seems- to be happening with increasing frequency.

    I have opened a help ticket with DakTech, and they have not heard of this issue from other users, at least yet.

    Is there anything I can do to stop this from happening?  It makes our school look bad when students see messages implying that we are using counterfeit copies of Windows...

    Thanks!

    Joel.

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-FTKYK-QBVD7-9DXH8
    Windows Product Key Hash: cXz+3RtDw80mocW4G4KBEKFrO8Q=
    Windows Product ID: 00371-OEM-8992671-00288
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048


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


     


    Your problem here is because the OS cannot read the SLIC table that should be present in the BIOS - either because the BIOS has been updated with a non-compliant one, or because of a problem with the OS. The OEM_SLP Key relies on the presence of this table to be able to self-activate.
     
    Your fix is a bit of a sledgehammer/nut response. Simply changing the Key to the one on the COA sticker and activating the machine should do the trick.
     
    Interestingly, the OEM_SLP Key above is one of the few not Google-able. This may simply mean that it's from a relatively small OEM, or that the Key is not actually a real one (although I would have expected a different error message in that case).
     

    --

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, April 14, 2011 9:21 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Noel:


    Thank you for that information - we have not done any BIOS updates since purchasing these machines, though the mfgr (DakTech) as offered to send me an updated version to try if they have a new one since the machines were made.

    But it puzzles me how sporadic, apparently randomly this is showing up. Related to windows updates?  Phase of the moon???

    Here is a snippet of the MGADiag output for the machine right next to the one that had the error message --- same model, same date code, it just hasn't (yet) displayed the "non genuine" message:

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            INTEL         DG41RQ  
      FACP            INTEL        DG41RQ
      HPET            INTEL         DG41RQ  
      MCFG            INTEL         DG41RQ  
      SLIC            daktec        Vista

    It DOES NOT complain about "no SLIC table"...

     

    Both the machine generating the error message and the one which has not have the exact same INTEL BIOS version:  RQG4110H.86A.0013.2009.1223.1136

    So it does not appear to be the BIOS itself that is causing the issue.


    I've run MGADiag on several machines that have not had this error message, and saved the results.  If one of them develops the message, we will have a "before and after" report, which may help.

     

    Re: the non-googleable OEM_SLP:   DakTech may be relatively small, but they are a first-rate supplier - I couldn't be more pleased with their warranty and customer service!

    They are based in Fargo, North Dakota.  You can visit their web site at http://DakTech.com if you are interested!

    Joel.

    Thursday, April 14, 2011 10:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    "Joel Alpers" wrote in message news:5af5b42d-c249-4e2d-ba9b-de83ff6de724...

    Noel:


    Thank you for that information - we have not done any BIOS updates since purchasing these machines, though the mfgr (DakTech) as offered to send me an updated version to try if they have a new one since the machines were made.

    But it puzzles me how sporadic, apparently randomly this is showing up. Related to windows updates?  Phase of the moon???

    Here is a snippet of the MGADiag output for the machine right next to the one that had the error message --- same model, same date code, it just hasn't (yet) displayed the "non genuine" message:

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            INTEL         DG41RQ  
      FACP            INTEL        DG41RQ
      HPET            INTEL         DG41RQ  
      MCFG            INTEL         DG41RQ  
      SLIC            daktec        Vista

    It DOES NOT complain about "no SLIC table"...

     

    Both the machine generating the error message and the one which has not have the exact same INTEL BIOS version:  RQG4110H.86A.0013.2009.1223.1136

    So it does not appear to be the BIOS itself that is causing the issue.


    I've run MGADiag on several machines that have not had this error message, and saved the results.  If one of them develops the message, we will have a "before and after" report, which may help.

     

    Re: the non-googleable OEM_SLP:   DakTech may be relatively small, but they are a first-rate supplier - I couldn't be more pleased with their warranty and customer service!

    They are based in Fargo, North Dakota.  You can visit their web site at http://DakTech.com if you are interested!

    Joel.


    Interesting site - thanks for the link.
    I agree that the probability is that something has 'slipped' in the OS - unfortunately it's not an easy thing to troubleshoot (as you've no doubt already discovered) especially in a forum context. There are so many
    variables that may apply that unless one has complete system backups before and after for comparison, it's unlikely that the issue can be isolated, and the easiest solution is simply to apply the COA Key.
    MGADiag is good - but it's not the complete diagnostic tool that is needed in such situations (unless the log files it creates are more complete than I believe they are - I haven't attempted to delve into them yet).
     
     

    --

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, April 15, 2011 6:37 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did changing the Product Key to the CoA key resolve the issue?
    Darin MS
    Friday, April 15, 2011 10:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No reply from the Original Poster.

    Issue is assumed to be resolved.

    Darin MS
    Tuesday, April 19, 2011 10:03 PM