locked
Windows 7 is not genuine RRS feed

  • Question

  • I have a custom built computer that is using Windows 7 OS obtained legitimately from the University of New Mexico.  I have not been able to activate Windows 7 using the activation program from the UNM KMS server.  I ran the MGA Diagnostic tool - results below.  What is the problem and what do I need to do to activate Windows 7?

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85378
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.004
    ID: {EB418F02-1A4D-42F5-92FF-1BE50AE78DE8}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Enterprise
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.110622-1506
    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)\Mozilla Firefox\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>{EB418F02-1A4D-42F5-92FF-1BE50AE78DE8}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.004</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HVTHH</PKey><PID>00392-918-5000002-85378</PID><PIDType>1</PIDType><SID>S-1-5-21-642438450-4161629714-1754634315</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7640</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.7</Version><SMBIOSVersion major="2" minor="5"/><Date>20101020000000.000000+000</Date></BIOS><HWID>0C7E3B07018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>MSI   </OEMID><OEMTableID>OEMSLIC </OEMTableID></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>311D6DEBD9D9D88</Val><Hash>rkP+FND0Isxk4+Ifj4v4d+wdDiI=</Hash><Pid>89409-708-3433555-65889</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.7601.17514

    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: ae2ee509-1b34-41c0-acb7-6d4650168915
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00392-00170-918-500000-03-1033-7600.0000-1342011
    Installation ID: 005684175743822824727030058570814033125933164944324730
    Partial Product Key: HVTHH
    License Status: Notification
    Notification Reason: 0x80070057.
    Remaining Windows rearm count: 4
    Trusted time: 9/19/2011 4:37:15 PM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 9:19:2011 16:27
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAEAAQABAAAAAgABAAEAHKJC4s6DEDNU8vyNOodW1MLqLDQKC8bhCNQC0A==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            7640MS        A7640100
      FACP            7640MS        A7640100
      SRAT            AMD           FAM_F_10
      HPET            7640MS        OEMHPET
      MCFG            7640MS        OEMMCFG
      SLIC            MSI           OEMSLIC
      OEMB            7640MS        A7640100
      SSDT            A M I         POWERNOW



    Monday, September 19, 2011 10:52 PM

Answers

  • "Willmar 1" wrote in message news:6f7152a9-2a4f-476b-9b5a-5324d965bc56...

    I have a custom built computer that is using Windows 7 OS obtained legitimately from the University of New Mexico.  I have not been able to activate Windows 7 using the activation program from the UNM KMS server.  I ran the MGA Diagnostic tool - results below.  What is the problem and what do I need to do to activate Windows 7?

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85378
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.004


    Other data-->
    SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7640</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.7</Version><SMBIOSVersion major="2" minor="5"/><Date>20101020000000.000000+000</Date></BIOS



    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Partial Product Key: HVTHH
    License Status: Notification
    Notification Reason: 0x80070057.
    Remaining Windows rearm count: 4
    Trusted time: 9/19/2011 4:37:15 PM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533


    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker



     
     
    Your Key is a KMS Client Key, which requires re-activation using the source servers at least every 6 months
    You need to contact the System Admin for assistance in entering the correct parameters for connection to the server and subsequent activation.
     
    Having said that, KMS Keys require a correct BIOS SLIC table for proper activation, in order to confirm the Upgrade status – and it may be that your problem with this is causing your current difficulties.
    It looks to me as if your computer is using a Retail motherboard  and cannot therefore have a proper BIOS SLIC table. A KMS Client cannot therefore activate, and the usual workaround for this situation is to use an MAK Key for activation. You need to consult with your institution to see whether they can provide such a Key.
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Thursday, September 22, 2011 7:30 PM
    Monday, September 19, 2011 11:21 PM
    Moderator