Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows 7 validation issue RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I had windows 7 installed and validated on my home computer for approx two years before i began getting a message at each start up telling me to activate my copy of windows. Every time i try to re-activate it using the product key, it gives an error. Ive been dealing with this issue for about a year, but with no permanent success.  Here is my MGADiag report:

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

    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    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: {54973D54-2C5D-4C79-9A4D-BB72BBA22D92}(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_gdr.130828-1532
    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:\Program Files\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-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{54973D54-2C5D-4C79-9A4D-BB72BBA22D92}</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-594964920-1048372748-3233468046</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv9500 Notebook PC    </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.34    </Version><SMBIOSVersion major="2" minor="4"/><Date>20110322000000.000000+000</Date></BIOS><HWID>32A73407018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06: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>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, OEM_SLP channel
    Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00178-926-700524-02-1033-7601.0000-0772014
    Installation ID: 019581130241889133330393559372820523230723650553887842
    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: 0xC004F07C.
    Remaining Windows rearm count: 2
    Trusted time: 1/22/2015 3:01:44 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 4:18:2014 10:42
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:


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

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x0
    OEMID and OEMTableID Consistent: yes
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC PTLTD APIC  
      FACP NVIDIA MCP67-M 
      SRAT AMD   HAMMER  
      HPET PTLTD HPETTBL 
      BOOT PTLTD $SBFTBL$
      MCFG PTLTD  MCFG  
      TCPA Phoeni x      
      SSDT PTLTD POWERNOW
      SLIC HPQOEM SLIC-MPC

    Thursday, January 22, 2015 9:08 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    The activation/validation is failing because the Key in use is for a DELL computer - and yours is a Hewlett Packard, which appears to have only a Vista SLIC table despite having a BIOS date well within Windows 7 territory.

    Foe what version and edition of Windows is the machine licensed, according to the COA sticker on the case?

    Where did you  purchase the Upgrade from??

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, January 23, 2015 7:09 AM
    Moderator

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    The activation/validation is failing because the Key in use is for a DELL computer - and yours is a Hewlett Packard, which appears to have only a Vista SLIC table despite having a BIOS date well within Windows 7 territory.

    Foe what version and edition of Windows is the machine licensed, according to the COA sticker on the case?

    Where did you  purchase the Upgrade from??

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, January 23, 2015 7:09 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you so much for the reply. I got the laptop from my father-in-law who works on computers. Im not sure what edition it is licensed to, as I no longer have the box. Im also unsure where the upgrade was purchased from, but i do know that according to my father-in-law everything was done legitimately and should be in working order. I had no problems for the first year or two after i got the computer. Is there a was to fix this problem or is this a compatibility issue that cannot be fixed?
    Friday, January 23, 2015 4:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It's not a compatibility issue, but a licensing issue - without a legitimate Product Key, there is no way to make the system genuine.

    You need to check for such a Key with your father.

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Sunday, January 25, 2015 8:08 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    From what you're sayng It sounds to me like the legitimacy of the product key is not an issue, but that the version of windows is simply not compatible with the type of computer that it is being used on. Is this incorrect? If this is the case, would installing this windows onto a dell computer solve the problem? I do have a dell laptop that i stopped using because the OS was outdated. Also, if the issue has to do with validation, why didnt I have this problem since I got the computer? It doesnt make sense to me that it would work just fine for two years and then suddenly have this issue?
    Sunday, January 25, 2015 4:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The Key is legitimate ONLY where

    1) the machine originally shipped with the relevant OS version and edition installed

    and

    2) The manufacturer's Recovery media are used.

    all other installs are non-valid/counterfeit.

    Assuming this Key has been in use throughout, then the probable explanation is that it was enabled by a hacker's Activation Exploit, which was recently broken/removed by an update such as Service Pack 1.

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Monday, January 26, 2015 7:04 AM
    Moderator