locked
My computer is telling me my version of Windows is not genuine. Why? RRS feed

  • Question

  • I have read some other post in terms of the steps I need to take, so here is my computer's diagnostic report.

     

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-73CQT-WMF7J-3Q6C9
    Windows Product Key Hash: KaFG+RmurcM3ZxzWyfEP9WtPUJw=
    Windows Product ID: 00359-OEM-8992687-00010
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {3BF8251C-117D-47C8-AFF9-9328CD3813BB}(1)
    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: 100 Genuine
    Microsoft Office Standard Edition 2003 - 100 Genuine
    Microsoft Office Home and Student 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_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>{3BF8251C-117D-47C8-AFF9-9328CD3813BB}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3Q6C9</PKey><PID>00359-OEM-8992687-00010</PID><PIDType>2</PIDType><SID>S-1-5-21-4219950773-3175406306-89407064</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dvx Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.07</Version><SMBIOSVersion major="2" minor="6"/><Date>20100427000000.000000+000</Date></BIOS><HWID>70B83607018400F4</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>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard Edition 2003</Name><Ver>11</Ver><Val>560074443A1ED00</Val><Hash>4BN6BGLDn+bKrRB8ZDM1Wreh7+w=</Hash><Pid>70141-640-0896032-57045</Pid><PidType>14</PidType></Product><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>A01A2A8DF170342</Val><Hash>4G3RHYTErd0ZszVpIaDSChF3ZCQ=</Hash><Pid>81602-417-8098271-68512</Pid><PidType>10</PidType></Product></Products><Applications><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/><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-800010-02-1033-7600.0000-1442010
    Installation ID: 014386215152851822231312946334184146997295056425184616
    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: 3Q6C9
    License Status: Notification
    Notification Reason: 0xC004F059.
    Remaining Windows rearm count: 1
    Trusted time: 12/31/2010 11:05:21 AM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 12:4:2010 16:12
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


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

    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            HP            1444   
      FACP            HP            1444   
      HPET            HP            1444   
      BOOT            HP            1444   
      MCFG            HP            1444   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           POWERNOW

    I am getting very frustrated with this, why does it occur?

    Friday, December 31, 2010 4:13 PM

Answers

  • Hello asanabia,

    Thank you for that info-----for best security, please edit your previous post to remove the bar code numbers.

    Here is a snippet of your mgadiag report:

    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            HP            1444   
      FACP            HP            1444   
      HPET            HP            1444   
      BOOT            HP            1444   
      MCFG            HP            1444   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           POWERNOW

    The cause of the current problem is bolded in the above snippet of the report.

    Installations of Windows done by major manufacturers such as your HP use a system called "OEM SLP" (system lock preinstallation).  Upon installation and at random periods thereafter, the Windows installed by HP looks for special data and a certificate embedded in the computer's BIOS, and when it finds that special data it verifies that it is either being installed, or verifies that it is still installed, on an HP computer.  Such verification is essential for compliance with the Software Licensing Terms.

    If, for some reason, when Windows checks for the special data and certificate, it cannot be found, then Windows assumes that it is not installed on an HP computer, and since this is a violation of the SLTs, Windows throws a fit and notifies you that it is nongenuine.

    This seems to be what has happened in your case.  The entry  " BIOS valid for OA 2.0: no, invalid SLIC table " is how we know that the data in the BIOS has become corrupted for some reason.

    There are two ways you can address this issue:

    1.  Especially if the computer is under warranty, contact HP support for your make and model, inform them of this situation (feel free to link to this posting) and request that they send you an updated BIOS that you can "flash" into the computer to possibly correct the problem.

    2.  Use Windows 7's Change Product Key function to change the installed product key from the OEM SLP product key now installed to the Product Key listed on your HP computer's CoA.  To do so, go to the Computer Properties page and look toward the bottom for the "Change Product Key" link.

    Post back to let us know how you do :-)

    Saturday, January 1, 2011 3:01 PM

All replies

  • Hello asababia,

    Please look on your HP computer for a Windows Certificate of Authenticity (CoA).  Please tell us the version and edition of Windows listed on the CoA, but don't post the product key.  Also tell us if "HP," "HPQ," "Hewlett Packard," or similar is printed on the CoA.

    Friday, December 31, 2010 8:19 PM
  • Not sure which is which but here is the order in which everything appears: Windows(R) 7 Home Prem OA HP There is a bar code here 584037-001 00196-081-161-070 Then there is another bar code. Finally there is my product key. On the other side there is another code which is X15-53758
    Friday, December 31, 2010 9:41 PM
  • Hello asanabia,

    Thank you for that info-----for best security, please edit your previous post to remove the bar code numbers.

    Here is a snippet of your mgadiag report:

    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            HP            1444   
      FACP            HP            1444   
      HPET            HP            1444   
      BOOT            HP            1444   
      MCFG            HP            1444   
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           POWERNOW

    The cause of the current problem is bolded in the above snippet of the report.

    Installations of Windows done by major manufacturers such as your HP use a system called "OEM SLP" (system lock preinstallation).  Upon installation and at random periods thereafter, the Windows installed by HP looks for special data and a certificate embedded in the computer's BIOS, and when it finds that special data it verifies that it is either being installed, or verifies that it is still installed, on an HP computer.  Such verification is essential for compliance with the Software Licensing Terms.

    If, for some reason, when Windows checks for the special data and certificate, it cannot be found, then Windows assumes that it is not installed on an HP computer, and since this is a violation of the SLTs, Windows throws a fit and notifies you that it is nongenuine.

    This seems to be what has happened in your case.  The entry  " BIOS valid for OA 2.0: no, invalid SLIC table " is how we know that the data in the BIOS has become corrupted for some reason.

    There are two ways you can address this issue:

    1.  Especially if the computer is under warranty, contact HP support for your make and model, inform them of this situation (feel free to link to this posting) and request that they send you an updated BIOS that you can "flash" into the computer to possibly correct the problem.

    2.  Use Windows 7's Change Product Key function to change the installed product key from the OEM SLP product key now installed to the Product Key listed on your HP computer's CoA.  To do so, go to the Computer Properties page and look toward the bottom for the "Change Product Key" link.

    Post back to let us know how you do :-)

    Saturday, January 1, 2011 3:01 PM