none
license all of a sudden not valid-after downloading updates RRS feed

  • Question

  • windows says my licence is not valid after I recently downloaded updates

    Diagnostic Report (1.7.0095.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89578-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {21A038D3-FE42-459B-9EC8-1057B19D511E}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.080425-1930
    TTS Error: M:20080823092904016-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 6.0.6002.16398

    WGA 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
    WGATray.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Home and Student 2007 - 100 Genuine
    OGA Version: Registered, 1.6.28.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.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\msvcrt.dll[7.0.6001.18000]
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6001.18023]
    File Mismatch: C:\Windows\system32\ole32.dll[6.0.6001.18000]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{21A038D3-FE42-459B-9EC8-1057B19D511E}</UGUID><Version>1.7.0095.0</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89578-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-4017482007-430093244-2307106644</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv6700 Notebook PC    </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.2C    </Version><SMBIOSVersion major="2" minor="4"/><Date>20080324000000.000000+000</Date></BIOS><HWID>28303507018400FE</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><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>1FDF6A175CEEF24</Val><Hash>b8Pp16xQeBIDD8bBVBnoRTl+0Q4=</Hash><Pid>81602-914-3578282-68992</Pid><PidType>1</PidType></Product></Products><Applications><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: U1BMRwEAAAAAAQAABAAAADIHAAAAAAAAYWECAAQweoeHSw42JAXJARsqbkNny+kXf2cj8k7x9VIAeFsM25WIcwOcw5btdUYJ3E4i///c8txUm77jMo1XOUjxkPChC8nGZ/CGnpuMJp3YQW1+6tR5tg0eEPrla9AGsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo725nC7v1JIKy7Fhxh6qIspY2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=



    Saturday, August 23, 2008 2:30 PM

Answers

  • Hello Planet,

    The core to your particular issue centers on the lines in your Diagnostic Report, that reads:

    File Scan Data-->
    File Mismatch: C:\Windows\system32\msvcrt.dll[7.0.6001.18000]
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6001.18023]
    File Mismatch: C:\Windows\system32\ole32.dll[6.0.6001.18000]

    These line means that the critical system files has either

    a)     Been tampered/modified/become corrupt to the point that its Signature Hash no longer matches the Signature Hash listed in Vista's System Catalog.

    Or

    b)    Been updated but the file's Signature Hash was not updated, in Vista's System Catalog to reflect the updated file's new Signature Hash.

     

      Vista compares a Critical System file's Signature Hash with the Signature Hash listed in its System Catalog to determine if that Critical System file has been tampered with. When this happens, depending on the file that has been tampered, Vista may show as Genuine or Non-Genuine, but either way, Vista won't Validate correctly and may also exhibit other strange behavior.

      To resolve your issue, we need to replace or repair the file so it's Signature Hash matches what is listed in Vista System Catalog. I can provide a couple of suggestions to do this:

    A)    Uninstall/Install Service Pack 1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). If possible, Uninstall SP1 and the reinstall it. Thes files may be included in the SP1 install and if so, SP1 will overwrite the bad file with a Known-Good copy.

    B)    Repair Windows using System Restore:

    1) Reboot Vista into Safe Mode

    2) Go to Control Panel

    3) On the left hand side of the Control Panel window, Click on "Classic View"

    4) Double-click "Backup and Restore Center"

    5) On the left hand side of the window, click "Repair Windows using system restore"

    6) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.

    7) Click the "Next" button.

    8) Reboot back into Normal mode

    9) Vista should no longer be in Reduced Functionality mode

       If neither of these solutions resolves your issue, the last resort, that I can provide, is to reinstall Vista. But before you do that, create a (no cost) support request at http://go.microsoft.com/fwlink/?linkid=52029 and see if they can provide any alternatives. 

    Thank you,
    Darin Smith
    WGA Forum Manager


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    Monday, August 25, 2008 8:06 PM

All replies

  • Hello Planet,

    The core to your particular issue centers on the lines in your Diagnostic Report, that reads:

    File Scan Data-->
    File Mismatch: C:\Windows\system32\msvcrt.dll[7.0.6001.18000]
    File Mismatch: C:\Windows\system32\gdi32.dll[6.0.6001.18023]
    File Mismatch: C:\Windows\system32\ole32.dll[6.0.6001.18000]

    These line means that the critical system files has either

    a)     Been tampered/modified/become corrupt to the point that its Signature Hash no longer matches the Signature Hash listed in Vista's System Catalog.

    Or

    b)    Been updated but the file's Signature Hash was not updated, in Vista's System Catalog to reflect the updated file's new Signature Hash.

     

      Vista compares a Critical System file's Signature Hash with the Signature Hash listed in its System Catalog to determine if that Critical System file has been tampered with. When this happens, depending on the file that has been tampered, Vista may show as Genuine or Non-Genuine, but either way, Vista won't Validate correctly and may also exhibit other strange behavior.

      To resolve your issue, we need to replace or repair the file so it's Signature Hash matches what is listed in Vista System Catalog. I can provide a couple of suggestions to do this:

    A)    Uninstall/Install Service Pack 1 for Vista (found at http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en). If possible, Uninstall SP1 and the reinstall it. Thes files may be included in the SP1 install and if so, SP1 will overwrite the bad file with a Known-Good copy.

    B)    Repair Windows using System Restore:

    1) Reboot Vista into Safe Mode

    2) Go to Control Panel

    3) On the left hand side of the Control Panel window, Click on "Classic View"

    4) Double-click "Backup and Restore Center"

    5) On the left hand side of the window, click "Repair Windows using system restore"

    6) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.

    7) Click the "Next" button.

    8) Reboot back into Normal mode

    9) Vista should no longer be in Reduced Functionality mode

       If neither of these solutions resolves your issue, the last resort, that I can provide, is to reinstall Vista. But before you do that, create a (no cost) support request at http://go.microsoft.com/fwlink/?linkid=52029 and see if they can provide any alternatives. 

    Thank you,
    Darin Smith
    WGA Forum Manager


    Attention Forum All Users: Please Do Not post your issue in someone else's Thread...Create your own.
    Monday, August 25, 2008 8:06 PM
  • check your product id key again , i just read another post with that same id key and i recognise it from a few years back when i got sold an illegal copy of win millenium lol. the last 15 digits you have are identical to the key i used back then .
    Monday, May 11, 2009 7:21 PM