locked
Windows 7 - This computer is not running genuine Windows RRS feed

  • Question

  • For the last week or so, the following message appears when I log in to Windows on my PC.

    "This computer is not running genuine Windows
    To use windows without interruption, ..."

    Clicking "Resolve online now" takes me to a page where I can buy a Windows license.
    https://www.microsoft.com/genuine/validate/ValidationResult.aspx?displaylang=en&PageName=validate

    Since I have a genuine copy of Windows, purchased from a reputable online store along with DVD, Product key etc.,  which has been installed on my PC for over a year without any problems, I am not going to buy another license.


    Looking on the MS support pages, I found this article:
    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/windows-is-showing-as-not-genuine/cbd43297-0e4d-458c-8487-9168c4cd668d

    Following the three steps shown there:

    1. "To verify Date and Time are correct:..."
    Date and time is verified to be correct.


    2. "Retype the Product Key:..." I get the following error message:

    C:\Windows\system32\sppcext.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support


    3. "Reactivate by Phone:...". I type "SLUI 4.exe" in the seach field, press enter and get the same error as in step 2 above.


    Searching the forums, I found some instructions on how to use the System File Checker - for example:
    the last post here https://social.microsoft.com/Forums/en/genuinewindows7/thread/5125891f-768b-4bc8-a922-487179495ade

    or the post from Friday, July 23, 2010 6:33 AM here
    https://social.microsoft.com/Forums/en/genuinewindows7/thread/33c3001c-513c-43fb-924b-99348085e0c0

    I followed those instructions, ran sfc /scannow from cmd.exe which completed with the following message:

    <START MESSAGE>
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

    The system file repair changes will take effect after the next reboot.
    <END MESSAGE>

    I rebooted the computer and, as instructed in the posts linked above, visited www.microsoft.com/genuine/validate which, as did the "Resolve online now" link, took me to a page to purchase Windows.

    Finally, I tried following the instructions in the first reply here:
    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/sluiexe-bad-image/8df84c62-44a5-4638-8e0e-69073ce084ea

    After following Steps 1-8 and typing slui.exe (step 9), the same error dialog apprared as above: "C:\Windows\system32\sppcext.dll is either not designed to run on Windows or..."

    Then, preparing to post here, I ran MGADiag.exe. After it completed, pressing 'Copy' resulted in the error dialog "Failed to create output files, hr=0x80070002. Please contact support."

    I went back to the above 9-steps and changed the name of the tokens file (Step 6) back to "tokens.dat". Then MGADiag.exe gave me something I could copy - results are below.

    What do I do now? Do I need to re-install Windows or is there a way to repair the damaged sppcext.dll?



    MGADiag results:
    ----------------

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-MR876-KP79Q-J7C2R
    Windows Product Key Hash: zQ0huzLYzfyD9/Z1H4SxJfyWzQE=
    Windows Product ID: 00359-OEM-8703012-52776
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {AA3386CB-E721-4CFD-8393-A94F9500E274}(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: 7601.win7sp1_gdr.120305-1505
    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 (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-->
    File Mismatch: C:\Windows\system32\sppcext.dll[Hr = 0x800b0100]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{AA3386CB-E721-4CFD-8393-A94F9500E274}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-J7C2R</PKey><PID>00359-OEM-8703012-52776</PID><PIDType>3</PIDType><SID>S-1-5-21-958966916-1164187426-3781525466</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7636</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.3</Version><SMBIOSVersion major="2" minor="6"/><Date>20091221000000.000000+000</Date></BIOS><HWID>E0C53D07018400FC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01: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, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activation ID: 586bc076-c93d-429a-afe5-a69fbc644e88
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00174-030-152776-02-2057-7600.0000-1692010
    Installation ID: 007846704442028720413115940190794060742565787265920101
    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: J7C2R
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 02/05/2012 20:56:19

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x0000000000000040
    Event Time Stamp: 5:1:2012 21:25
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui


    HWID Data-->
    HWID Hash Current: OAAAAAEABAABAAIAAQACAAAAAgABAAEA6GFU5mz34l8snwZP5nZk/ZgnHHHeiGI9wHwq/cbrXF0=

    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            7636MS        A7636100
      FACP            7636MS        A7636100
      HPET            7636MS        OEMHPET
      MCFG            7636MS        OEMMCFG
      OEMB            7636MS        A7636100
      DMAR            AMI        OEMDMAR
      SSDT            DpgPmm        CpuPm

    Wednesday, May 2, 2012 7:08 PM

Answers

All replies

  • Use System Restore to recover to a date before you first saw the error.

    Note:  The message about the MGADiag tool not creating an output file is normal.  You don't need one anyway since the report is copied to your clipboard.  The message has nothing to do with your issue, which is a tampered file.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.


    Wednesday, May 2, 2012 7:36 PM
    Answerer
  • C:\Windows\system32\sppcext.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support

    Windows Resource Protection found corrupt files but was unable to fix some of them.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log


    MGADiag results:
    ----------------

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-MR876-KP79Q-J7C2R
    Windows Product Key Hash: zQ0huzLYzfyD9/Z1H4SxJfyWzQE=
    Windows Product ID: 00359-OEM-8703012-52776
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010300.1.0.003


    File Scan Data-->
    File Mismatch: C:\Windows\system32\sppcext.dll[Hr = 0x800b0100]

    Other data-->
    SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7636</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.3</Version><SMBIOSVersion major="2" minor="6"/><Date>20091221000000.000000+000</Date></BIOS


    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Partial Product Key: J7C2R
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 02/05/2012 20:56:19

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x0000000000000040
    Event Time Stamp: 5:1:2012 21:25
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui


    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table


    s

    The problem, as you discovered is with the file mismatch/tamper in sppcext.dll
     
    You say that SFC ran, but failed to fix all errors, and demanded a reboot - the demand for a reboot is unusual. It can sometimes mean that it was unable to properly complete the scan, so have you run it again since?
    Please do so, and then copy the CBS.log file to your desktop, then upload it to your public SkyDrive (or other fileshare site) and post a link in your response.
     
    Please also run the following commands from an Elevated Command Prompt -
     
    DIR C:\Windows\sppcext.* /S
    ICACLS C:\Windows\sppcext.* /T
     
    post the results, so we can perhaps see exactly what the problem is.
     
    Here are some instructions to make life easier
    :)
    1) To open an Elevated Command Prompt Window
    (the CP window), click on Start, All Programs, Accessories – then right-click on
    Command Prompt, and select Run as Administrator. Accept the UAC
    prompt.
    2) To run the commands easier, highlight the
    block of commands, and right-click on the highlight – select Copy. In the CP
    Windows, click on the black/white icon at top left – select Paste. The commands
    will run but may not complete the last command, so hit the Enter Key
    once.
    3) To copy the results... click on the
    Black/White icon in the top left, and select Edit... 'Select All', and hit the
    Enter key - then use Ctrl+V or r-click+Paste to paste it into your
    response.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, May 2, 2012 7:44 PM
    Moderator
  • "Cbarnhorst" wrote in message news:3758f3f8-731c-4dc2-a832-1693db2293f3...

    Use System Restore to recover to a date before you first saw the error.

    Note:  The message about the MGADiag tool not creating an output file is normal.  You don't need one anyway since the report is copied to your clipboard.  The message has nothing to do with your issue, which is a tampered file.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

     

    I'd be wary of a System Restore - the SFC result would tend to indicate severe problems which may be reinstated unless the restore point is far enough back, and risk of other problems increases with the time factor.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, May 2, 2012 7:47 PM
    Moderator
  • Thanks for your response. As suggested, I've not (yet) done a system restore.

    The CBS.log file after running sfc /scannow again is here:
    https://skydrive.live.com/redir.aspx?cid=da8ba10df0f75a4d&resid=DA8BA10DF0F75A4D!133&parid=DA8BA10DF0F75A4D!132&authkey=!AN1BvCjYrHTLxtE

    The results of running the two commands you mentioned are here (you can also see the output of sfc /scannow):

    <CMD.EXE OUTPUT>

    C:\Windows\system32>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of th
    em.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    C:\Windows\system32>DIR C:\Windows\sppcext.* /S
     Volume in drive C has no label.
     Volume Serial Number is 4AB8-9B69

     Directory of C:\Windows\System32

    14/07/2009  03:41         1,203,712 sppcext.dll
                   1 File(s)      1,203,712 bytes

     Directory of C:\Windows\System32\en-US

    14/07/2009  04:30            17,408 sppcext.dll.mui
                   1 File(s)         17,408 bytes

     Directory of C:\Windows\SysWOW64

    14/07/2009  03:16         1,111,552 sppcext.dll
                   1 File(s)      1,111,552 bytes

     Directory of C:\Windows\SysWOW64\en-US

    14/07/2009  04:04            17,408 sppcext.dll.mui
                   1 File(s)         17,408 bytes

     Directory of C:\Windows\winsxs\amd64_microsoft-windows-s..clientext.resources_3
    1bf3856ad364e35_6.1.7600.16385_en-us_c2382769078e1059

    14/07/2009  04:30            17,408 sppcext.dll.mui
                   1 File(s)         17,408 bytes

     Directory of C:\Windows\winsxs\amd64_microsoft-windows-security-spp-clientext_3
    1bf3856ad364e35_6.1.7600.16385_none_28bbe77bcacffbe4

    14/07/2009  03:41         1,203,712 sppcext.dll
                   1 File(s)      1,203,712 bytes

     Directory of C:\Windows\winsxs\x86_microsoft-windows-s..clientext.resources_31b
    f3856ad364e35_6.1.7600.16385_en-us_66198be54f309f23

    14/07/2009  04:04            17,408 sppcext.dll.mui
                   1 File(s)         17,408 bytes

     Directory of C:\Windows\winsxs\x86_microsoft-windows-security-spp-clientext_31b
    f3856ad364e35_6.1.7600.16385_none_cc9d4bf812728aae

    14/07/2009  03:16         1,111,552 sppcext.dll
                   1 File(s)      1,111,552 bytes

         Total Files Listed:
                   8 File(s)      4,700,160 bytes
                   0 Dir(s)  536,771,297,280 bytes free

    C:\Windows\system32>ICACLS C:\Windows\sppcext.* /T
    C:\Windows\System32\sppcext.dll NT SERVICE\TrustedInstaller:(F)
                                    BUILTIN\Administrators:(RX)
                                    NT AUTHORITY\SYSTEM:(RX)
                                    BUILTIN\Users:(RX)

    C:\Windows\System32\en-US\sppcext.dll.mui NT SERVICE\TrustedInstaller:(F)
                                              BUILTIN\Administrators:(RX)
                                              NT AUTHORITY\SYSTEM:(RX)
                                              BUILTIN\Users:(RX)

    C:\Windows\System32\LogFiles\WMI\RtBackup\sppcext.*: Access is denied.
    Successfully processed 2 files; Failed processing 1 files

    <END CMD.EXE OUTPUT>

    Hoping that sheds some light on the problem.

    Best Regards and thanks in advance.

    Thursday, May 3, 2012 7:52 PM
  • I've just noticed this additional answer.

    Please see my reply to your above response.

    Thanks!

    Thursday, May 3, 2012 7:53 PM
  • You have a huge number of errors in the CBS.log - the only solution I can see is to reinstall.

    A Repair install may be sufficient - please see the tutorial here...

    http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

    I would suggest backing up your data to external storage first.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    • Marked as answer by dgndg Thursday, May 3, 2012 8:59 PM
    Thursday, May 3, 2012 8:12 PM
    Moderator
  • Oh, that doesn't sound good. Luckily, I do make regular backups.

    Thanks for your help.

    Thursday, May 3, 2012 8:59 PM
  • A repair install whould, in theory at least, retain your data.

    If you mean that you have system backups, then you  should check the SFC after the restore.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Thursday, May 3, 2012 9:34 PM
    Moderator
  • I mean backups of my files - I will do a fresh install of Windows.

    I had hoped that Windows 7 was an improvement over the old 're-install every year or two to keep the system usable' approach of former versions. Of well, seems not. Outside got a re-spray, but it's the same old sh*t under the bonnet.

    :-(

    Sunday, May 6, 2012 7:59 AM
  • I've never had to reinstall  Windows for any  such reason - and one of the machines I'm currently using was last reinstalled in 2006, after a hard drive went AWOL.

    A little preventinve maintenance every now and then reaps a reward.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Sunday, May 6, 2012 10:37 AM
    Moderator
  • I agree with Noel.  I have several installations of Windows 7 and I have never had to do a reinstall on any of them.  In that respect Windows 7 has been far more stable and reliable for me than any previous Windows.

    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    Sunday, May 6, 2012 2:23 PM
    Answerer