locked
Windows 7 claims the copy is not genuine, after it was working fine for months. RRS feed

  • Question

  • One day when turning on my computer, it suddenly didn't recognize my copy of windows as genuine and, since then,  I have been unable to run windows update and update Microsoft Security Essentials.

    The Windows 7 copy has been working for me since I purchased the computer several months ago.

    Here is the diagnostic tool report.

     

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a8
    Windows Product Key: *****-*****-2QWT6-HCQXJ-9YQTR
    Windows Product Key Hash: PVjSC5x6njvqunmbCY3lOD7rYDo=
    Windows Product ID: 00359-OEM-8992687-00007
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {15447CDD-DB38-43F5-9CFE-B61B8A9C2313}(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: T:20101227051926205-
    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 (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>{15447CDD-DB38-43F5-9CFE-B61B8A9C2313}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-9YQTR</PKey><PID>00359-OEM-8992687-00007</PID><PIDType>2</PIDType><SID>S-1-5-21-398999324-3941538247-4093174684</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc.        </Manufacturer><Model>G73Jh</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>G73Jh.211</Version><SMBIOSVersion major="2" minor="6"/><Date>20100727000000.000000+000</Date></BIOS><HWID>6BB93607018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>_ASUS_</OEMID><OEMTableID>Notebook</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAABgiAAAAAAAAYWECAID6//8sDDqvyKXLAWbXGpOihAOpMHzDmWxsjuqC+ctM2NrBcE8kb8ZRZUx6GMFwefzT6DAy5+qoNNNiezOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAx4dZsxs/sxaQSZh6DCEuBHwof6p5Tmnje4Xe32j5Px9KvdjMqIdzO9hYOPMJgS8AczkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385
    Error: product key not found.

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A8
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 1:2:2011 10:14
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MAAAAAEAAQABAAEAAAACAAAAAwABAAEAln0ck0Sl+kI8izJXYj0GJXYITrtWD3ZW

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            _ASUS_        Notebook
      FACP            _ASUS_        Notebook
      DBGP            _ASUS_        Notebook
      HPET            _ASUS_        Notebook
      MCFG            _ASUS_        Notebook
      ECDT            _ASUS_        Notebook
      SLIC            _ASUS_        Notebook
      SSDT            PmRef        CpuPm
      DMAR            INTEL         CP_FIELD


     

    Sunday, January 2, 2011 6:58 PM

Answers

  • "Niaobuzz" wrote in message news:002f97d7-0ffc-4870-aaca-cba8c68a482c...

    Well now I'm really confused. I tried running slui.exe again to re-enter my product key, but it didn't let me enter it. Instead, it told me the key was invalid or something like that, and redirected me to the website to "Reslove" the problem. When I got to the website, it suddenly recognized my windows installation, and it now thinks that everything is allright. I didn't even do anything. Ran windows update, and it worked fine, although it didn't find anything new since 12/24/10. Is that correct?

     

    Here is the new diag report either way

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

    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-39R28-KDVRM-MJVYK
    Windows Product Key Hash: QrnLlLCy2wQuIb3D+oM1gEvqIGg=
    Windows Product ID: 00359-OEM-9809504-00868
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {15447CDD-DB38-43F5-9CFE-B61B8A9C2313}(3)
    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: T:20101227051926205-

     

    You have a Trusted Store Tamper present on your machine (dated 27th Dec 2010), which I didn't notice before -
    Here's what Darin has to say about these problems....
    <quote>
    This is telling me that your Windows is suffering from a Trusted Store Tamper.  (This type of issue seems to be rare in Windows 7 as I have seen this only a few times).   In Windows, there are files that have, what is known as, a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source. If a file is modified, in any way, the Digital Signature is broken.
     
    Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source (HP) a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way, it's Digital Signature is broken and becomes invalid.  So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.
     
      What I have described in the above example is basically what is happening with your Windows 7.  Some Digitally Signed file has been modified in some way (replaced, rewritten or just become corrupt) and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) and that is what has triggered the Non-Genuine messaging.
     
      Unfortunately, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.
     

      1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occur the most with Drivers.  So my first suggestion is to confirm that all your hardware drivers are up to date.
     
    Note: Figuring out if a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seek assistance or skip down to #2 or #3 below
     
      2) Restore Windows back to a past System Restore Point.
     
    1) Boot into Windows
    2) Click the ‘Start’ button
    3) In the Start Search field, type: System Restore and hit “Enter” keyboard key
    4) 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 a date Before you first noticed the issue.
    5) Click the "Next" button.
    6) Reboot
     
      3) Repair Windows using the 'sfc /scannow' command
     
    The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)
     
    1) Login to Windows
    2) Click the Start button
    3) Type: cmd.exe in the search field
    4) Right-click the cmd.exe file and select Run as Administrator
    5) In the CMD window, type: sfc /scannow
    6) Reboot and see if that resolves the issue.
     
    If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Windows.  If you do need to reinstall Windows, you will just need to run a full install of Vista, then reinstall Windows 7.
     
    </quote>

     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Wednesday, January 5, 2011 11:56 PM
    Monday, January 3, 2011 9:53 AM
    Moderator

All replies

  • "Niaobuzz" wrote in message news:65ad25a4-34bc-4141-8f98-30adb96c85c9...

    One day when turning on my computer, it suddenly didn't recognize my copy of windows as genuine and, since then,  I have been unable to run windows update and update Microsoft Security Essentials.

    The Windows 7 copy has been working for me since I purchased the computer several months ago.

    Here is the diagnostic tool report.

     

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

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a8
    Windows Product Key: *****-*****-2QWT6-HCQXJ-9YQTR
    Windows Product Key Hash: PVjSC5x6njvqunmbCY3lOD7rYDo=
    Windows Product ID: 00359-OEM-8992687-00007
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385
    Error: product key not found.

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

    This type of error is likely to be caused by over-zealous security settings or software (or malware).
    What Security software are you using?
     
     
    I would try rebuilding the Licensing Store first, -
     
    Recreate the Licensing Store
    1) Click Start button.
    2) Type: CMD.exe into the 'Search programs and files' field
    3) Right-Click on CMD.exe and select Run as Administrator
    4) Type: net stop sppsvc   (It may ask you if you are sure, select yes)
    Note: the Software Protection service may not be running, this is ok.
    5) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
    6) Type: rename tokens.dat tokens.bar
    7) Type: cd %windir%\system32
    8) Type: net start sppsvc
    9) Type: slui.exe
    10) After a couple of seconds Windows Activation dialog will appear. You may be asked to re-activate and/or re-enter your product key or Activation may occur automatically.
     
    Run MGADiag again, and post the report
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Sunday, January 2, 2011 7:33 PM
    Moderator
  • The process stopped with the following error after I entered my product key at step 10 of your instructions.

     

    The following failure occurred while trying to use the product key:

    Code:
        0xC004F050

    Description:
        The Software Licensing Service reported that the product key is invalid.

     

    I was using Microsoft Security Essentials, but as that stopped updating and other things started acting up after the validation problems occurred, I am also running Panda Cloud Antivirus

     

    Thank you

    Sunday, January 2, 2011 7:51 PM
  • "Niaobuzz" wrote in message news:721a99c5-fcb3-495a-b9c3-e79058e69fc8...

    The process stopped with the following error after I entered my product key at step 10 of your instructions.

     

    The following failure occurred while trying to use the product key:

    Code:
        0xC004F050

    Description:
        The Software Licensing Service reported that the product key is invalid.

     

    I was using Microsoft Security Essentials, but as that stopped updating and other things started acting up after the validation problems occurred, I am also running Panda Cloud Antivirus

     

    Thank you


    Are you sure that you are entering the right key? - some characters are easily confused (Been There - Done That!) unless you are very careful - using a magnifier and a good light is almost an essential!!)
    Some people have reported problems using AVG this past few days - I would recommend uninstalling it completely, and using the AVG removal too as well, to get rid of the left-overs.....  http://www.avg.com/us-en/download-tools
    Once you've done that, try  using MGADiag again, and post the report.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Sunday, January 2, 2011 8:10 PM
    Moderator
  • Well now I'm really confused. I tried running slui.exe again to re-enter my product key, but it didn't let me enter it. Instead, it told me the key was invalid or something like that, and redirected me to the website to "Reslove" the problem. When I got to the website, it suddenly recognized my windows installation, and it now thinks that everything is allright. I didn't even do anything. Ran windows update, and it worked fine, although it didn't find anything new since 12/24/10. Is that correct?

     

    Here is the new diag report either way

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

    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-39R28-KDVRM-MJVYK
    Windows Product Key Hash: QrnLlLCy2wQuIb3D+oM1gEvqIGg=
    Windows Product ID: 00359-OEM-9809504-00868
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {15447CDD-DB38-43F5-9CFE-B61B8A9C2313}(3)
    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: T:20101227051926205-
    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 (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>{15447CDD-DB38-43F5-9CFE-B61B8A9C2313}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MJVYK</PKey><PID>00359-OEM-9809504-00868</PID><PIDType>8</PIDType><SID>S-1-5-21-398999324-3941538247-4093174684</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc.        </Manufacturer><Model>G73Jh</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>G73Jh.211</Version><SMBIOSVersion major="2" minor="6"/><Date>20100727000000.000000+000</Date></BIOS><HWID>6BB93607018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>_ASUS_</OEMID><OEMTableID>Notebook</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAACAAAABgiAAAAAAAAYWECAID6//8sDDqvyKXLAWbXGpOihAOpMHzDmWxsjuqC+ctM2NrBcE8kb8ZRZUx6GMFwefzT6DAy5+qoNNNiezOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAx4dZsxs/sxaQSZh6DCEuBHwof6p5Tmnje4Xe32j5Px9KvdjMqIdzO9hYOPMJgS8AczkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
    Activation ID: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00196-095-000868-02-1033-7600.0000-0022011
    Installation ID: 098961105386899605286933878206924591873880329702697313
    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: MJVYK
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 1/2/2011 12:19:28 PM

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


    HWID Data-->
    HWID Hash Current: MAAAAAEAAQABAAEAAAACAAAAAwABAAEAln0ck0Sl+kI8izJXYj0GJXYITrtWD3ZW

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            _ASUS_        Notebook
      FACP            _ASUS_        Notebook
      DBGP            _ASUS_        Notebook
      HPET            _ASUS_        Notebook
      MCFG            _ASUS_        Notebook
      ECDT            _ASUS_        Notebook
      SLIC            _ASUS_        Notebook
      SSDT            PmRef        CpuPm
      DMAR            INTEL         CP_FIELD


    Sunday, January 2, 2011 8:29 PM
  • "Niaobuzz" wrote in message news:002f97d7-0ffc-4870-aaca-cba8c68a482c...

    Well now I'm really confused. I tried running slui.exe again to re-enter my product key, but it didn't let me enter it. Instead, it told me the key was invalid or something like that, and redirected me to the website to "Reslove" the problem. When I got to the website, it suddenly recognized my windows installation, and it now thinks that everything is allright. I didn't even do anything. Ran windows update, and it worked fine, although it didn't find anything new since 12/24/10. Is that correct?

     

    Here is the new diag report either way

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

    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-39R28-KDVRM-MJVYK
    Windows Product Key Hash: QrnLlLCy2wQuIb3D+oM1gEvqIGg=
    Windows Product ID: 00359-OEM-9809504-00868
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {15447CDD-DB38-43F5-9CFE-B61B8A9C2313}(3)
    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: T:20101227051926205-

     

    You have a Trusted Store Tamper present on your machine (dated 27th Dec 2010), which I didn't notice before -
    Here's what Darin has to say about these problems....
    <quote>
    This is telling me that your Windows is suffering from a Trusted Store Tamper.  (This type of issue seems to be rare in Windows 7 as I have seen this only a few times).   In Windows, there are files that have, what is known as, a Digital Signature. A Digital Signature is an industry standard that ensures that a file is, in fact, from the specified source. If a file is modified, in any way, the Digital Signature is broken.
     
    Example: lets say you get a Printer Driver that is Digitally Signed from HP. Since the Digital Signature was created by a Trusted Source (HP) a Certificate is created within Window's Trusted Store. The Digital Signature is dependent on the file's Hash (think fingerprint) so if the file is changed in any way, it's Digital Signature is broken and becomes invalid.  So lets say that the HP Driver got modified by some sort of Malware. The File's Hash would no longer match the hash listed in the Digitally Signature (or the Signature may not even be readable at that point). The Digital Signature become invalid because windows now don't know what has been done to that file, so the file can no longer be trusted. This in turn invalidates the corresponding Certificate within the Trusted Store.
     
      What I have described in the above example is basically what is happening with your Windows 7.  Some Digitally Signed file has been modified in some way (replaced, rewritten or just become corrupt) and the Certificate within Windows's Trusted Store has become invalid (i.e. no longer trusted) and that is what has triggered the Non-Genuine messaging.
     
      Unfortunately, none of my tools are able to pinpoint which file/signature/certificate is causing the problem. However there are a few thing you can try that may correct the issue.
     

      1) First off not all Digitally Signed files are Drivers, but from experience we have found that this issue seems to occur the most with Drivers.  So my first suggestion is to confirm that all your hardware drivers are up to date.
     
    Note: Figuring out if a Driver is up to date and/or replacing a driver with a more current one can sometimes take semi-advanced computer knowledge and me explaining the process is outside the scope of this forum. If you do not know how to work with Drivers seek assistance or skip down to #2 or #3 below
     
      2) Restore Windows back to a past System Restore Point.
     
    1) Boot into Windows
    2) Click the ‘Start’ button
    3) In the Start Search field, type: System Restore and hit “Enter” keyboard key
    4) 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 a date Before you first noticed the issue.
    5) Click the "Next" button.
    6) Reboot
     
      3) Repair Windows using the 'sfc /scannow' command
     
    The Scan Now will look for any bad Windows files and attempt to repair them, if possible (it isn't always able to)
     
    1) Login to Windows
    2) Click the Start button
    3) Type: cmd.exe in the search field
    4) Right-click the cmd.exe file and select Run as Administrator
    5) In the CMD window, type: sfc /scannow
    6) Reboot and see if that resolves the issue.
     
    If none of my suggestions resolves the issue, then the only other thing I can suggest is to either create a (no cost) support request at http://support.microsoft.com/gp/contactwga or reinstall Windows.  If you do need to reinstall Windows, you will just need to run a full install of Vista, then reinstall Windows 7.
     
    </quote>

     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Wednesday, January 5, 2011 11:56 PM
    Monday, January 3, 2011 9:53 AM
    Moderator