locked
Windows 7 version no longer genuine RRS feed

  • Question

  • I have been running Windows 7 (purchased from NewEgg) for about 15 months and now get the message saying my version is no longer genuine.  In preparation for the withdrawal Windows Live Sync I attempted to install Windows Live Mesh, and things have gone downhill since then.  The Live Mesh would not install completely, and I used the program remove tool to uninstall it.  Several other applications damaged by the Live Mesh, and among them were the MS Office products which had to be all reinstalled.  (Some functions still do not work right).  How do I repair the damage done by Windows Live?? 

    My diagnostic report follows: 

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

     

    Validation Code: 0x8004FE22

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-M3FHD-VC9D3-DDWJX

    Windows Product Key Hash: tHvIAJ29P98/t8ZMVlCdgSpnUXg=

    Windows Product ID: 00371-OEM-9043982-86551

    Windows Product ID Type: 3

    Windows License Type: OEM System Builder

    Windows OS version: 6.1.7600.2.00010100.0.0.048

    ID: {E8E86E78-2D5A-4868-A51F-505C480DA0B0}(3)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Professional

    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: 100 Genuine

    Microsoft Office Professional 2007 - 100 Genuine

    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:\Users\DaleH\AppData\Local\Google\Chrome\Application\chrome.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>{E8E86E78-2D5A-4868-A51F-505C480DA0B0}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-DDWJX</PKey><PID>00371-OEM-9043982-86551</PID><PIDType>3</PIDType><SID>S-1-5-21-644407321-4166437340-1983415</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1807   </Version><SMBIOSVersion major="2" minor="6"/><Date>20100723000000.000000+000</Date></BIOS><HWID>CDB93607018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0014-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional 2007</Name><Ver>12</Ver><Val>9B66B6A210A4F14</Val><Hash>0nqs+iZdmiBVW7xHC07GfZshpSU=</Hash><Pid>81605-906-4494716-65070</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    C:\Windows\system32\slmgr.vbs(22, 1) (null): Library not registered. 

     

    Windows Activation Technologies-->

    HrOffline: 0x8004FE22

    HrOnline: N/A

    HealthStatus: 0x0000000000000800

    Event Time Stamp: 4:13:2011 09:58

    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

     

     

    HWID Data-->

    HWID Hash Current: OAAAAAEABgABAAEAAAADAAAAAQABAAEAln2AOJJqgJYKgAiFkC+mdkLG5sIKNT5vidgB8lp3dlY=

     

    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 072310 APIC1636

      FACP 072310 FACP1636

      HPET 072310 OEMHPET 

      MCFG 072310 OEMMCFG 

      OEMB 072310 OEMB1636

      ASPT 072310 PerfTune

      OSFR 072310 OEMOSFR 

      SSDT DpgPmm CpuPm

     

     

    Wednesday, April 13, 2011 4:08 PM

Answers

  • I looked at the System Restore and found that there were no restore points. :-( 
    The System Protection configuration has been changed so that the maximum space allocated was 0.  I increased the amount significantly, but then when I tried to create a new restore point it failed with the following message: 
    The restore point could not be created for the following reason:
    An error was detected in the Volume SHadow Copy Service (VSS).  The problem occurred while trying to contact VSS writers. Verify --
    The log shows the following message:
    Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  The Registry Writer failed to respond to a query from VSS. Check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.
    Now what are my options?  And how long will it be before "Windows Interruption" occurs and my system ceases to operate?   

    dh2al
    This sounds like the effect of a malware infection.
    'Windows Interruption', as you call it, is very limited in Win7 - so you have time to sort the problem out :)
     
    Please check that the VSS Service is properly installed and running...
    Click on Start
    in the Search box, type
    SERVICES.MSC
    and hit the Enter key.
    accept the UAC prompt if offered.
    the Services control panel will come up
    look there for the Volume Shadow Copy service - right-click on it, and select Properties.
    Check that the 'path to executable' is C:\Windows\system32\vssvc.exe  and that the service is set to 'Manual' start. - it will probably be be in the Stopped state, so attempt to Start it. If it fails to start, make a note of the EXACT error message.
     
    close the Services Control panel, and reboot Windows
    post back with your results.
     
    Then download and install Malwarebytes Anti-Malware from www.malwarebytes.org . Update it, then reboot to Safe Mode and run a Full System Scan from there.
    See what it reports.
    Post back with a results summary.
     
     

     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, April 14, 2011 7:40 PM
    Moderator

All replies

  • I have been running Windows 7 (purchased from NewEgg) for about 15 months and now get the message saying my version is no longer genuine.  In preparation for the withdrawal Windows Live Sync I attempted to install Windows Live Mesh, and things have gone downhill since then.  The Live Mesh would not install completely, and I used the program remove tool to uninstall it.  Several other applications damaged by the Live Mesh, and among them were the MS Office products which had to be all reinstalled.  (Some functions still do not work right).  How do I repair the damage done by Windows Live?? 

    My diagnostic report follows: 

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

     

    Validation Code: 0x8004FE22

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-M3FHD-VC9D3-DDWJX

    Windows Product Key Hash: tHvIAJ29P98/t8ZMVlCdgSpnUXg=

    Windows Product ID: 00371-OEM-9043982-86551

    Windows Product ID Type: 3

    Windows License Type: OEM System Builder

    Windows OS version: 6.1.7600.2.00010100.0.0.048

     

    Licensing Data-->

    C:\Windows\system32\slmgr.vbs(22, 1) (null): Library not registered. 

     

    Windows Activation Technologies-->

    HrOffline: 0x8004FE22

    HrOnline: N/A

    HealthStatus: 0x0000000000000800

    Event Time Stamp: 4:13:2011 09:58

    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


    Your report indicates that the WGA system attempted to repair the problem it found, and failed.
    There are two problems evident in your report
    1) 'Library not registered'
    2) a Tampered File - SLUI.EXE (or perhaps SLUI.EXE.MUI- although that's unlikely)
     
    It's possible that the second error is causing the first, because of the way the system works.
    Your first action should be to attempt a System Restore to a time when the system worked properly - or preferably about 3 days before the error appeared.
     
    Try that, and then run the MGADiag report again, and post back with your results.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Proposed as answer by Darin Smith MS Wednesday, April 13, 2011 11:55 PM
    Wednesday, April 13, 2011 6:50 PM
    Moderator
  • I looked at the System Restore and found that there were no restore points. :-( 
    The System Protection configuration has been changed so that the maximum space allocated was 0.  I increased the amount significantly, but then when I tried to create a new restore point it failed with the following message: 
    The restore point could not be created for the following reason:
    An error was detected in the Volume SHadow Copy Service (VSS).  The problem occurred while trying to contact VSS writers. Verify --
    The log shows the following message:
    Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  The Registry Writer failed to respond to a query from VSS. Check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.
    Now what are my options?  And how long will it be before "Windows Interruption" occurs and my system ceases to operate?   

    dh2al
    Thursday, April 14, 2011 2:50 PM
  • I looked at the System Restore and found that there were no restore points. :-( 
    The System Protection configuration has been changed so that the maximum space allocated was 0.  I increased the amount significantly, but then when I tried to create a new restore point it failed with the following message: 
    The restore point could not be created for the following reason:
    An error was detected in the Volume SHadow Copy Service (VSS).  The problem occurred while trying to contact VSS writers. Verify --
    The log shows the following message:
    Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  The Registry Writer failed to respond to a query from VSS. Check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.
    Now what are my options?  And how long will it be before "Windows Interruption" occurs and my system ceases to operate?   

    dh2al
    This sounds like the effect of a malware infection.
    'Windows Interruption', as you call it, is very limited in Win7 - so you have time to sort the problem out :)
     
    Please check that the VSS Service is properly installed and running...
    Click on Start
    in the Search box, type
    SERVICES.MSC
    and hit the Enter key.
    accept the UAC prompt if offered.
    the Services control panel will come up
    look there for the Volume Shadow Copy service - right-click on it, and select Properties.
    Check that the 'path to executable' is C:\Windows\system32\vssvc.exe  and that the service is set to 'Manual' start. - it will probably be be in the Stopped state, so attempt to Start it. If it fails to start, make a note of the EXACT error message.
     
    close the Services Control panel, and reboot Windows
    post back with your results.
     
    Then download and install Malwarebytes Anti-Malware from www.malwarebytes.org . Update it, then reboot to Safe Mode and run a Full System Scan from there.
    See what it reports.
    Post back with a results summary.
     
     

     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, April 14, 2011 7:40 PM
    Moderator
  • I see that there was a PUP.adware flagged by the malware tool, but not sure what impact that might have had.  I got a larger hard file and am in the process of rebuilding Windows 7 from the ground up.  

    I don't have all the apps installed yet, but there were several that seem to run OK now that were hit after I tried (unsuccessfully) to install Windows Live Mesh as a replacement for the now defunct Windows Sync.   I think I will forge ahead and continue building on the new disk.  I can salvage my data from the old disk.   It will take some time and effort, but probably less than it would take to put Humpty-Dumpty together again (cleaning up Windows 7 after failed Mesh install).     


    dh2al
    Wednesday, April 20, 2011 10:46 PM