0x8004FE22 (Win 7 activated, but still getting "non-genuine" popup)

Page 1 of 3 123 LastLast

  1. Posts : 11
    Windows 7 Ultimate x64
       #1

    0x8004FE22 (Win 7 activated, but still getting "non-genuine" popup)


    Hi,

    Windows 7 Ultimate x64. It has been installed for a while, but I just recently (re)activated with a genuine key. I managed to make the "non-genuine" message (bottom right corner) go away, but still getting the "This computer is not running genuine Windows" popup dialog.

    The output of MGADiag is below. Could you please help?


    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 0x8004FE22
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-CF66B-YBBPF-8HGJ8
    Windows Product Key Hash: 8b3KXN3WYp8U8TBOYhESMKSoL7Y=
    Windows Product ID: 00426-383-2990305-06527
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {C448DCA9-78F4-4E41-9C52-EBC1B33F0943}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.140303-2144
    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\systemcpl.dll[6.1.7600.16384], Hr = 0x800b0100
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{C448DCA9-78F4-4E41-9C52-EBC1B33F0943}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-8HGJ8</PKey><PID>00426-383-2990305-06527</PID><PIDType>5</PIDType><SID>S-1-5-21-2639045236-29053441-75679838</SID><SYSTEM><Manufacturer>FUJITSU</Manufacturer><Model>LIFEBOOK A531</Model></SYSTEM><BIOS><Manufacturer>FUJITSU // Phoenix Technologies Ltd.</Manufacturer><Version>1.24</Version><SMBIOSVersion major="2" minor="6"/><Date>20110927000000.000000+000</Date></BIOS><HWID>B1083307018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00: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, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: c619d61c-c2f2-40c3-ab3f-c5924314b0f3
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00212-383-299030-00-1033-7601.0000-2772014
    Installation ID: 014721111234195036068823229023783983005272048681734361
    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: 8HGJ8
    License Status: Initial grace period
    Time remaining: 42180 minute(s) (29 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 10/9/2014 10:21:11 AM
    
    Windows Activation Technologies-->
    HrOffline: 0x8004FE22
    HrOnline: N/A
    HealthStatus: 0x0000000000002800
    Event Time Stamp: 10:9:2014 09:29
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    
    
    HWID Data-->
    HWID Hash Current: MAAAAAEAAQABAAEAAAABAAAABAABAAEA6GGk/wSxUpyEEoiW1N4ypkaAKGtszy5z
    
    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            FUJ           PC      
      FACP            FUJ           PC      
      HPET            FUJ           PC      
      MCFG            FUJ           PC      
      SSDT            FUJ           PtidDevc
      ASF!            FUJ           PC      
      SSDT            FUJ           PtidDevc
      SSDT            FUJ           PtidDevc
      UEFI            FUJ           PC      
      UEFI            FUJ           PC      
      UEFI            FUJ           PC
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    File Scan Data-->
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16384], Hr = 0x800b0100
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui

    Please follow the Windows Update Posting Instructions and post the requested data
    If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)
      My Computer


  3. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Hi,

    Thank you; I attached the CBS folder zipped.
    I ran the "sfc /scannow" twice with the following result...

    Code:
    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
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #4


    That file does at least contain the failure log for the latest attempt to install SP1 - but no SFC data.
    Please post he current CBS.log

    Sorry - wrong thread!
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #5

    Sorry about that!
    Your CheckSUR log is clear - but SFC shows the following problems.
    Code:
     Line 17395: 2014-10-11 17:05:29, Info                  CSI    000006b6 [SR] Repairing 8 components
     Line 17396: 2014-10-11 17:05:29, Info                  CSI    000006b7 [SR] Beginning Verify and Repair transaction
     Line 17397: 2014-10-11 17:05:29, Info                  CSI    000006b8 [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
     Line 17398: 2014-10-11 17:05:29, Info                  CSI    000006b9 [SR] Cannot repair member file [l:20{10}]"winver.exe" of Microsoft-Windows-winver, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
     Line 17399: 2014-10-11 17:05:29, Info                  CSI    000006ba [SR] Cannot repair member file [l:14{7}]"sfc.exe" of Microsoft-Windows-WRP-Integrity-Client, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
     Line 17400: 2014-10-11 17:05:29, Info                  CSI    000006bb [SR] Cannot repair member file [l:26{13}]"sppcomapi.dll" of Microsoft-Windows-Security-SPP-UX, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
     Line 17401: 2014-10-11 17:05:29, Info                  CSI    000006bc [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
     Line 17402: 2014-10-11 17:05:29, Info                  CSI    000006bd [SR] Cannot repair member file [l:26{13}]"systemcpl.dll" of Microsoft-Windows-systemcpl, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
     Line 17403: 2014-10-11 17:05:29, Info                  CSI    000006be [SR] Cannot repair member file [l:20{10}]"winver.exe" of Microsoft-Windows-winver, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
     Line 17404: 2014-10-11 17:05:29, Info                  CSI    000006bf [SR] Cannot repair member file [l:14{7}]"sfc.exe" of Microsoft-Windows-WRP-Integrity-Client, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

    I'll post a fix protocol later.
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    I've uploaded a file - jtsaa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    Close all windows (it would be a good idea to print these instructions!)

    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.

    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\jtsaa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\jtsaa
    or
    DIR E:\jtsaa



    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



    XCOPY <drive>:\jtsaa <drive>:\windows\winsxs /y /i /s /v /h



    (e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



    run the command (it should take almost no time) and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your reply
      My Computer


  7. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Hi,

    I get an "Access denied" when trying to copy on the very first file in the package... I tried to take ownership of everything (including the winsxs folder), but nothing seems to help...
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #8

    That actually gives us some important information (I think).
    I'll have to ponder on it, and come back to you tomorrow (too much EtOH under the belt at present )
    Shout if you don't hear from me in 48 hours.
      My Computer


  9. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Hi Noel,

    I'm wondering if you had a chance to deal with this yet? Thanks a lot!
    Cheers,

    Joe
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #10

    Two possible causes - disk corruption, and Registry corruption.

    Please run a full CHKDSK and SFC scan....
    Click on Start > All Programs > Accessories
    Right-click on the Command Prompt entry
    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
    At the Command prompt, type
    CHKDSK C: /R
    and hit the Enter key.
    You will be told that the drive is locked, and the CHKDSK will run at the next boot - hit the Y key, and then reboot.
    The CHKDSK will take a few hours depending on the size of the drive, so be patient!
    After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) - then run the SFC.

    SFC -System File Checker - Instructions
    Click on Start > All Programs > Accessories
    Right-click on the Command Prompt entry
    Select Run as Administrator and accept the UAC prompt - 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.

    Upload the CBS.log file (compressed, please!) to your reply
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:38.
Find Us