locked
Window 7 fails Genuine Validation after installing IE9 RC RRS feed

  • Question

  • I just installed IE9 RC and started receiving validation warnings from Microsofts Genuine Check. It is obvious that IE9 changed several files in the process. Some people suggest running the genuine check pages in IE compatibility mode but that does not seem to work. Actually I am not sure if it is possible to run microsoft in compatibility mode although I have tried. The compatibility mode icon dissappears when I visit any microsoft.com page.

    Thank you for your recommendations.

    Monday, February 14, 2011 3:36 PM

Answers

  • Seems that I found the issue.I actually used an older recommendation of yours on another post.
    I used SFC and that seems to have fixed the issue. Further the application that caused the change in files stopped working, so now I know which one it is. Apparently there is  a Gateway Voice Command Application that I activated recently just to play with. ON the same day I installed IE9 for testing and thought that this was potentially the source of the error. Apparently it was not because IE is running. The Voice App is complaining at startup so I know it is missing the file that was changed.

    Thank you for the assistance but through your previous post  ;-)

    • Marked as answer by Darin Smith MS Friday, February 18, 2011 11:08 PM
    Thursday, February 17, 2011 6:01 PM

All replies

  • I just installed IE9 RC and started receiving validation warnings from Microsofts Genuine Check. It is obvious that IE9 changed several files in the process. Some people suggest running the genuine check pages in IE compatibility mode but that does not seem to work. Actually I am not sure if it is possible to run microsoft in compatibility mode although I have tried. The compatibility mode icon dissappears when I visit any microsoft.com page.

    Thank you for your recommendations.


    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, February 14, 2011 3:58 PM
    Moderator
  • I run the MGADiag and of course shows that my Windows 7 Ultimate is Genuine. Results below:

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-P9YHX-V9BHG-RDTWB
    Windows Product Key Hash: D3jE/cfbKx7QuPEGOj8s/Dh3jow=
    Windows Product ID: 00426-068-0942607-86346
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {4C61704A-4E14-4313-A2EF-01848B86377F}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.101026-1503
    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: B4D0AA8B-604-645_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\en-US\sppcext.dll.mui[Hr = 0x80004005]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{4C61704A-4E14-4313-A2EF-01848B86377F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-RDTWB</PKey><PID>00426-068-0942607-86346</PID><PIDType>5</PIDType><SID>S-1-5-21-810944243-3456619164-3329540265</SID><SYSTEM><Manufacturer>Gateway</Manufacturer><Model>LX6810-01</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>R01-A1C0</Version><SMBIOSVersion major="2" minor="5"/><Date>20090717000000.000000+000</Date></BIOS><HWID>71BA3607018400F8</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>ACRSYS</OEMID><OEMTableID>ACRPRDCT</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.7600.16385

    Name: Windows(R) 7, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: a0cde89c-3304-4157-b61c-c8ad785d1fad
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00172-068-094260-00-1033-7600.0000-2322010
    Installation ID: 022203617290674350291011408432088040383643848175690014
    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: RDTWB
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 2/16/2011 7:14:05 AM

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x0000000000000040
    Event Time Stamp: 2:16:2011 07:11
    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: MAAAAAEAAAABAAEAAgACAAAAAgABAAEAln0ARBRpkulkW5K8RgugF6l5Mfa+LkxY

    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   ACRSYS  APIC1138
      FACP   ACRSYS  FACP1138
      HPET   ACRSYS  OEMHPET0
      MCFG   ACRSYS  OEMMCFG
      WDRT   ACRSYS  NV-WDRT
      SLIC   ACRSYS  ACRPRDCT
      OEMB   ACRSYS  OEMB1138
      NVHD   ACRSYS  NVHDCP
      AWMI   ACRSYS  OEMB1138
      SSDT   DpgPmm  CpuPm

     

    Wednesday, February 16, 2011 3:20 PM
  • I run the MGADiag and of course shows that my Windows 7 Ultimate is Genuine. Results below:

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-P9YHX-V9BHG-RDTWB
    Windows Product Key Hash: D3jE/cfbKx7QuPEGOj8s/Dh3jow=
    Windows Product ID: 00426-068-0942607-86346
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001

    File Scan Data-->
    File Mismatch: C:\Windows\system32\en-US\sppcext.dll.mui[Hr = 0x80004005]

    Other data-->
    ><SYSTEM><Manufacturer>Gateway</Manufacturer><Model>LX6810-01</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>R01-A1C0</Version><SMBIOSVersion major="2" minor="5"/><Date>20090717000000.000000+000</Date></BIOS>

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Partial Product Key: RDTWB
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 2/16/2011 7:14:05 AM

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x0000000000000040
    Event Time Stamp: 2:16:2011 07:11
    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
    Windows marker version: 0x0


    It's not showing your installation as genuine at all!
    What it is showing, is that you have a corrupted file (sppcext.dll.mui) - with possibly a problematic registry reference to it.
     
     
    Having said that, you are using a Windows Key that is from an MSDN account - if you are not a member of MSDN, then the installation is totally non-genuine, and you need to claim a refund from your vendor.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Proposed as answer by Darin Smith MS Thursday, February 17, 2011 12:36 AM
    • Marked as answer by Darin Smith MS Thursday, February 17, 2011 12:36 AM
    • Unmarked as answer by AEK21 Thursday, February 17, 2011 3:53 PM
    Wednesday, February 16, 2011 10:54 PM
    Moderator
  • Yes I am a member of MSDN and therefore the "Genuine Key" (under a different work related email)

    So to follow up, what is the proposed action for the corrupted file (sppcext.dll.mui)? Should I extract from the CD and replace? Is it completely coincidental that the issue appeared as soon as I installed IE9 RC ?

    Thank you for looking inot this

    GS

    Thursday, February 17, 2011 3:58 PM
  • Why not uninstall IE9 and see where you are.  I think it is confusing the issues.  It is prerelease and you can reinstall at will.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Thursday, February 17, 2011 4:17 PM
    Answerer
  • Seems that I found the issue.I actually used an older recommendation of yours on another post.
    I used SFC and that seems to have fixed the issue. Further the application that caused the change in files stopped working, so now I know which one it is. Apparently there is  a Gateway Voice Command Application that I activated recently just to play with. ON the same day I installed IE9 for testing and thought that this was potentially the source of the error. Apparently it was not because IE is running. The Voice App is complaining at startup so I know it is missing the file that was changed.

    Thank you for the assistance but through your previous post  ;-)

    • Marked as answer by Darin Smith MS Friday, February 18, 2011 11:08 PM
    Thursday, February 17, 2011 6:01 PM
  • "Cbarnhorst" wrote in message news:bb99f1b3-e6aa-4bac-a202-037a9dbf377c...
    Why not uninstall IE9 and see where you are.  I think it is confusing the issues.  It is prerelease and you can reinstall at will.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    That certainly makes sense to me :)
    If that doesn't fix the issue, then  use SFC  /SCANNOW from an elevated Command Prompt, and see if that does the trick (or at least fixes the corrupted file issue).

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, February 17, 2011 8:52 PM
    Moderator