locked
Windows 7 Build 7601 Not Genuine? RRS feed

  • Question

  • I ran the WGADiag tool and it just spat out errors.

    I received my key from MSDN Academic Alliance, as part of my College studies. I know the key works, but Windows is having problems during startup with windows validation. It takes an hour or so before I get the bottom-right text saying windows is not genuine. All I do is view the System area, and it instantly validates. I run the validation tools, and it still says its all validated.

    It's annoying, and I want it to go away.

     

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

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-*****-*****-4732W
    Windows Product Key Hash: ymirf+lzb5Pw48L8DarIz/KByo0=
    Windows Product ID: 55041-090-7415864-86637
    Windows Product ID Type: 6
    Windows License Type: Volume MAK
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {21B3617A-C8B6-4C17-A9F3-2E6B7B368AEE}(3)
    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_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: 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: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Users\Brian\AppData\Local\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-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{21B3617A-C8B6-4C17-A9F3-2E6B7B368AEE}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-090-7415864-86637</PID><PIDType>6</PIDType><SID>S-1-5-21-129502303-3463593409-2197745360</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7612</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.1</Version><SMBIOSVersion major="2" minor="6"/><Date>20090928000000.000000+000</Date></BIOS><HWID>A83E3307018400FA</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/><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, VOLUME_MAK channel
    Activation ID: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 55041-00172-090-741586-03-1033-7601.0000-0802011
    Installation ID: 004646157555162311056505805273180900047446682725104294
    Partial Product Key: 4732W
    License Status: Licensed

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Not Registered - 0x80070005
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: NgAAAAIABAABAAEAAAADAAAAAQABAAEAonaA6kT8WmLUFJaSPgooQl6XeFJiPYIyeKIQqY4u

    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   7612MS  A7612200
      FACP   7612MS  A7612200
      MCFG   7612MS  OEMMCFG
      OEMB   7612MS  A7612200
      INFO   7612MS  AMDINFO
      NVHD   7612MS  NVHDCP
      SSDT   A M I   POWERNOW 

    Monday, March 21, 2011 10:55 PM

Answers

  • I see no issue with the Diagnostic Report currently showing in the Original Post. I have also checked the key and it is Valid and Genuine.

     

    I recommend running a new report while the Non-genuine issue is occurring. Once you have the new Diagnostic Report post it in a NEW post (Do Not replace it in the Original Post).

     

    Thank you,

     


    Darin MS
    Tuesday, March 29, 2011 9:19 PM

All replies

  • I just changed the report. The key that was supposedly in use was wrong, I changed it to the correct key and reran the diagnostic tool.
    Monday, March 21, 2011 11:09 PM
  • Where is the report?
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Monday, March 21, 2011 11:57 PM
    Answerer
  • I just changed the report. The key that was supposedly in use was wrong, I changed it to the correct key and reran the diagnostic tool.


    Since you did not post the new Diagnostic Report (the one where the correct key is being used) can we assume the issue is resolved?

     

    Thank you,


    Darin MS
    • Proposed as answer by Darin Smith MS Wednesday, March 23, 2011 10:21 PM
    • Marked as answer by Darin Smith MS Thursday, March 24, 2011 8:56 PM
    • Unmarked as answer by BrianGraham91 Friday, March 25, 2011 2:52 PM
    Wednesday, March 23, 2011 10:21 PM
  • I just changed the report. The key that was supposedly in use was wrong, I changed it to the correct key and reran the diagnostic tool.


    Since you did not post the new Diagnostic Report (the one where the correct key is being used) can we assume the issue is resolved?

     

    Thank you,


    Darin MS
    The updated main post has the correct key being used, and the issue is not resolved.
    Friday, March 25, 2011 2:53 PM
  • If you are saying that you edited the first report rather than make a new reply for the second report, please don't do that.  For one thing no one should have to read a prior reply for changes to it.  For another it makes impossible to compare changes that may occur throughout the report. 
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Friday, March 25, 2011 3:05 PM
    Answerer
  • I pasted the new report in place of the original report, on the original post. This means that the report you see above is the report of my CURRENT problem.

    Saturday, March 26, 2011 8:50 PM
  • I see no issue with the Diagnostic Report currently showing in the Original Post. I have also checked the key and it is Valid and Genuine.

     

    I recommend running a new report while the Non-genuine issue is occurring. Once you have the new Diagnostic Report post it in a NEW post (Do Not replace it in the Original Post).

     

    Thank you,

     


    Darin MS
    Tuesday, March 29, 2011 9:19 PM
  • No further reply from the Original Poster.

    Issue is assumed to be resolved.


    Darin MS
    Tuesday, April 5, 2011 8:52 PM