locked
"Windows not genuine"... how do I validate? RRS feed

  • Question

  • Here is the MGADT pastage: Please advise of how I must validate this.

     

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
    Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
    Windows Product ID: 00371-OEM-8992671-00524
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {B81303CA-5F83-403C-819E-CEB6A458D434}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000000
    Build lab: 7601.win7sp1_rtm.101119-1850
    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 XP Professional with FrontPage - 100 Genuine
    Microsoft Office Outlook 2003 - 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\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-->
    File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7601.17514], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{B81303CA-5F83-403C-819E-CEB6A458D434}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-733WD</PKey><PID>00371-OEM-8992671-00524</PID><PIDType>2</PIDType><SID>S-1-5-21-2126886603-323291572-1052932243</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6400                  </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A17</Version><SMBIOSVersion major="2" minor="4"/><Date>20090917000000.000000+000</Date></BIOS><HWID>BF1A3307018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00: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="{90280409-6000-11D3-8CFE-0050048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office XP Professional with FrontPage</Name><Ver>10</Ver><Val>3FE974B4C65B448</Val><Hash>dVJl2idZ4HUtBoxIPKwAtGVpQ8E=</Hash><Pid>54185-640-8668527-17462</Pid><PidType>14</PidType></Product><Product GUID="{90E00409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Outlook 2003</Name><Ver>11</Ver><Val>6E990CE9C6B1D00</Val><Hash>0I+VrkllIuLsWA3RQj+TnJX9lNY=</Hash><Pid>73930-640-0000086-55658</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="10" Result="100"/><App Id="16" Version="10" Result="100"/><App Id="17" Version="10" Result="100"/><App Id="18" Version="10" Result="100"/><App Id="1A" Version="10" Result="100"/><App Id="1B" Version="10" Result="100"/><App Id="1A" Version="11" Result="100"/></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-700524-02-2057-7600.0000-0902011
    Installation ID: 013833988341475804133693260493813604546545445565673991
    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: 733WD
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 4
    Trusted time: 10/05/2011 18:58:48

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 5:6:2011 20:32
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: NgAAAAEAAwABAAIAAQACAAAAAgABAAEA6GFMEiHn5m7EpQbPvpoWK87sap8W7tRfgL6QBUbK

    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            DELL          M09   
      FACP            DELL          M09   
      HPET            DELL          M09   
      MCFG            DELL          M09   
      ____            DELL          M09   
      ASF!            DELL          M09   
      TCPA                   
      SSDT            PmRef        CpuPm



    Tuesday, May 10, 2011 6:04 PM

Answers

  • "headshrinker_jb" wrote in message news:9429c624-2e1d-4a61-aa47-9f9e3fc148a7...

    Here is the MGADT pastage: Please advise of how I must validate this.

     

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
    Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
    Windows Product ID: 00371-OEM-8992671-00524
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.048


    File Scan Data-->
    File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7601.17514], Hr = 0x800b0100

    Other data-->
    SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6400                  </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A17</Version><SMBIOSVersion major="2" minor="4"/><Date>20090917000000.000000+000</Date></BIOS

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Partial Product Key: 733WD
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 4
    Trusted time: 10/05/2011 18:58:48

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


    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A




    Have you updated the BIOS? For some reason, your OS is unable to properly read the BIOS to see the SLIC table that should be present.
     
    For which version and edition of Windows is the computer licensed, according to the COA sticker on the case? (or possibly inside the battery compartment)?
     
    If the sticker is for Win7 Professional, then change the Key to the one on the sticker, using the Change Product Key link on the System Properties page. Note that this may not work, as there are indications that there may be an interference in the machine from a program called RemoveWAT. If this program has been used, then you will have to undo whatever it's done before trying to change the key. If this doesn't clear the user32.dll error then you may have more problems.
     
    If the sticker is not for Win7 Pro, then you will need to use a legitimate Win 7 Pro license to make the current installation genuine
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 10, 2011 6:20 PM
    Moderator

All replies

  • "headshrinker_jb" wrote in message news:9429c624-2e1d-4a61-aa47-9f9e3fc148a7...

    Here is the MGADT pastage: Please advise of how I must validate this.

     

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
    Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
    Windows Product ID: 00371-OEM-8992671-00524
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.048


    File Scan Data-->
    File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7601.17514], Hr = 0x800b0100

    Other data-->
    SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6400                  </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A17</Version><SMBIOSVersion major="2" minor="4"/><Date>20090917000000.000000+000</Date></BIOS

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Partial Product Key: 733WD
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 4
    Trusted time: 10/05/2011 18:58:48

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


    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A




    Have you updated the BIOS? For some reason, your OS is unable to properly read the BIOS to see the SLIC table that should be present.
     
    For which version and edition of Windows is the computer licensed, according to the COA sticker on the case? (or possibly inside the battery compartment)?
     
    If the sticker is for Win7 Professional, then change the Key to the one on the sticker, using the Change Product Key link on the System Properties page. Note that this may not work, as there are indications that there may be an interference in the machine from a program called RemoveWAT. If this program has been used, then you will have to undo whatever it's done before trying to change the key. If this doesn't clear the user32.dll error then you may have more problems.
     
    If the sticker is not for Win7 Pro, then you will need to use a legitimate Win 7 Pro license to make the current installation genuine
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 10, 2011 6:20 PM
    Moderator
  • Hi,

     

    The windows version is Pro, amd I located the key on the battery.

     

    Changing the key worked. I'm unsure why it went wrong in the first place...

     

    Thanks for your help.

    Tuesday, May 10, 2011 6:53 PM
  • "headshrinker_jb" wrote in message news:50a98bf4-523e-4421-98e0-a7f0dd2d20d7...

    Hi,

     

    The windows version is Pro, amd I located the key on the battery.

     

    Changing the key worked. I'm unsure why it went wrong in the first place...

     

    Thanks for your help.


    The problem you experienced can happen for a number of reasons (and that's why MS insist on the OEM providing you with your own personal Key).
    One of the reasons is a BIOS update which doesn't include the SLIC table (for whatever reason).
    another is the action of an over-zealous anti-virus or firewall.
    and another is the action of malware.
    (that is not an exhaustive list - there are other reasons as well, such as disk failure, or registry problems)
     
    So long as the 'new' key activates and validates properly, then you should have no further problem.
     
    Please post a new MGADiag report, so that we can check that all is OK.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 10, 2011 9:59 PM
    Moderator