locked
Windows 7 is activated, but not genuine RRS feed

  • Question

  • HI

    I have this computer with genuine windows 7 pro product key and sticker and already activated. But it keep popping up saying windows is not genuine, I ran WGAdiag and found these, can you tell me what wrong and how to fix it. Thanks

     

     

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-T4HFB-YFPYB-YRTB6
    Windows Product Key Hash: awKFlgjjAD+Rn84YWnJ1ae/Jf8c=
    Windows Product ID: 00371-OEM-9044812-01774
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {8085A13C-4519-43BE-AF26-B6DD967170A7}(3)
    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: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: FCEE394C-429-800700c1_025D1FF3-344-800700c1_025D1FF3-229-800700c1_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\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\sppobjs.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcomapi.dll[Hr = 0x80070005]
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{8085A13C-4519-43BE-AF26-B6DD967170A7}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-YRTB6</PKey><PID>00371-OEM-9044812-01774</PID><PIDType>3</PIDType><SID>S-1-5-21-2343335980-892247823-2396810594</SID><SYSTEM/><BIOS/><HWID>BF633807018400F2</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>1</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-->
    Input Error: Can not find script file "C:\Windows\system32\slmgr.vbs".

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x000000000001EFF0
    Event Time Stamp: 6:28:2011 20:44
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppobjs.dll
    Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui
    Tampered File: %systemroot%\system32\sppwinob.dll
    Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui
    Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui
    Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui
    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui
    Tampered File: %systemroot%\system32\drivers\spsys.sys


    HWID Data-->
    HWID Hash Current: MgAAAAEAAgABAAIAAQACAAAAAQABAAEAeqi2ENowkgCedmRCrNvOcGQRYj1q486f1sc=

    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   7309MS  A7309300
      FACP   7309MS  A7309300
      SRAT   AMD     FAM_F_10
      HPET   7309MS  OEMHPET0
      MCFG   7309MS  OEMMCFG
      WDRT   7309MS  NV-WDRT
      OEMB   7309MS  A7309300
      SSDT   A M I   POWERNOW

     

     

    • Edited by Darin Smith MS Friday, July 1, 2011 6:58 PM removed duplicate Diagnostic Reports
    Friday, July 1, 2011 4:03 PM

Answers

  • HI

    I have this computer with genuine windows 7 pro product key and sticker and already activated. But it keep popping up saying windows is not genuine, I ran WGAdiag and found these, can you tell me what wrong and how to fix it. Thanks

     

     

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-T4HFB-YFPYB-YRTB6
    Windows Product Key Hash: awKFlgjjAD+Rn84YWnJ1ae/Jf8c=
    Windows Product ID: 00371-OEM-9044812-01774
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder

     

    File Scan Data-->
    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcomapi.dll[Hr = 0x80070005]
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

     

     


    Your problem is caused by the set of file mis matches above - while it's one of the more common error modes, we have as yet been unable to fix it in the forums here (but we're willing to have a go if you are! - it'll take some time though)
     

    If you're in  a hurry, your best bet is to contact WGA Support
    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4
     
    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0
     
    Please let us know if (and how)  MS manage to repair the problem without a repair install of the OS - it would be useful for future reference!
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, July 1, 2011 4:40 PM
    Moderator

All replies

  • Please delete all the multiple copies of the report.  Click Edit and cut all but the final copy. 
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Friday, July 1, 2011 4:33 PM
    Answerer
  • HI

    I have this computer with genuine windows 7 pro product key and sticker and already activated. But it keep popping up saying windows is not genuine, I ran WGAdiag and found these, can you tell me what wrong and how to fix it. Thanks

     

     

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-T4HFB-YFPYB-YRTB6
    Windows Product Key Hash: awKFlgjjAD+Rn84YWnJ1ae/Jf8c=
    Windows Product ID: 00371-OEM-9044812-01774
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder

     

    File Scan Data-->
    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcomapi.dll[Hr = 0x80070005]
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

     

     


    Your problem is caused by the set of file mis matches above - while it's one of the more common error modes, we have as yet been unable to fix it in the forums here (but we're willing to have a go if you are! - it'll take some time though)
     

    If you're in  a hurry, your best bet is to contact WGA Support
    North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4
     
    Outside North America:
    http://support.microsoft.com/contactus/?ws=support#tab0
     
    Please let us know if (and how)  MS manage to repair the problem without a repair install of the OS - it would be useful for future reference!
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, July 1, 2011 4:40 PM
    Moderator
  • HI

    Thanks for your reply

    So if the problem is the file mismatch. and If these file mismatch fixed. the geniuine problem will be fixed?

    and how do I able to fix these file mismatch anyway. Thanks

     

     

    Friday, July 1, 2011 7:14 PM
  • HI

    Thanks for your reply

    So if the problem is the file mismatch. and If these file mismatch fixed. the geniuine problem will be fixed?

    and how do I able to fix these file mismatch anyway. Thanks

     

     


    That is what we don't yet know.
    What we do know is that there is a problem which affects this set of file (and some others), and it manifests as a File Mismatch with the associated File Tampers, in the MGADiag report - all normal methods of fixing such files appear not to work, so either something is affecting the system, or there's a common failure point (possibly in either a Service or in a System Certificate.
    I can suggest a few things that might help - and might help us to isolate the problem but it'll take a while for you to work through them.....
     
    First off, let's try the 'standard' fix methods.
    1) System Restore - try restoring the system back to a date before the problem surfaced.
    Once the System Restore is complete, reboot again, and then run another MGADiag report - see if that has changed anything. If not, then go to the next one.
    2) System File Checker...
    try a System File Checker - it will attempt to replace the broken file and any others it finds.
    System File Checker - Instructions
    Click on the Start button
    type in the Search  box
    CMD.EXE
    right-click on the only file that is found
    Select Run as Administrator
     - the Elevated Command Prompt window should pop up
    At the Command prompt, type
     
    SFC   /SCANNOW
     
    and hit the Enter key
    Wait for the scan to finish - make a note of any error messages - and then reboot.
     
    run another MGADiag report, and post the results.
    If nothing appears to have changed, you may want to try the next step....
    Please open an Elevated (Administrator) Command Prompt window and use the following commands....
     
    sc qc sppsvc
    sc queryex sppsvc
    sc qprivs sppsvc
    sc qsidtype sppsvc
    sc sdshow sppsvc
     
    copy and paste the results into your response.
    This may show us what's wrong with at least one of the files.
     
    Also - please run the same commands with the Cryptographic Service -
    sc qc cryptsvc
    sc queryex cryptsvc
    sc qprivs cryptsvc
    sc qsidtype cryptsvc
    sc sdshow cryptsvc
     again, post the results.
     

     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, July 1, 2011 7:32 PM
    Moderator