none
Error message "Windows is not genuine" RRS feed

  • Question

  • I'm running Windows 7 Home Premium with Service Pack 1. After removing a virus and using Acrosis to do a system restore, I started receiving the message that Windows was not genuine.  When I check it in the System folder the MS icon is there.  I have installed updates and everything is working fine there.  How do I get rid of this message.  I did a diagnostic check  and this is the result.

    Diagnostic Report (1.5.0540.0):
    -----------------------------------------
    WGA Data-->
    Genuine Validation Status: Unsupported OS
    Windows Product Key: Failed to get Product Key.
    Windows Product Key Hash: Failed to get Product Key.
    Windows Product ID: Failed to get Product ID.
    Windows Product ID Type:
    Windows License Type:
    Windows OS version: 6.1.7601.2.00010300.1.0.000
    Download Center code: LRKXS64
    ID: {6C60E2A9-D988-435C-92AF-81A70B693C7B}
    Is Admin: No
    AutoDial: No
    Registry: 0x0
    WGA Version: Registered, 1.9.42.0
    Signature Type: Microsoft
    Validation Diagnostic:

    System Scan Data-->
    Scan: Complete
    Cryptography: Complete

    Notifications Data-->
    Cached Result: N/A
    Cache refresh Interval: N/A
    Extended notification delay(non-genuine): N/A
    Extended notification delay(un-activated): N/A
    All disabled: N/A
    Reminder reduced: N/A
    File Exists: No
    Version: N/A
    Signatue Type: N/A

    OGA Data-->
    Office Status: 111
    Office Diagnostics:

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\PROGRA~2\AOLDES~1.6\aol.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>{6C60E2A9-D988-435C-92AF-81A70B693C7B}</UGUID><Version>1.5.0540.0</Version><OS>6.1.7601.2.00010300.1.0.000</OS><PID/><SID>S-1-5-21-192566122-1382187156-2896854108</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>AW017AV-ABA e9200z</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>5.03</Version><SMBIOSVersion major="2" minor="6"/><Date>20090911000000.000000+000</Date></BIOS><HWID>13E93E07018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone></MachineData>   <Software><Office><Result>111</Result><Products/></Office></Software></GenuineResults> 

     

    Tuesday, November 1, 2011 5:49 PM

Answers

All replies

  • You are using an old version of the tool.  It is not compatible with Windows 7.  You need to use the latest version.

    http://go.microsoft.com/fwlink/?linkid=52012


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, November 1, 2011 6:04 PM
    Answerer
  • Sorry about that.  Here it is again:

     

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

    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0x80070003
    Windows Product Key: *****-*****-73CQT-WMF7J-3Q6C9
    Windows Product Key Hash: KaFG+RmurcM3ZxzWyfEP9WtPUJw=
    Windows Product ID: 00359-OEM-8992687-00010
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {AF38C35E-CF39-4888-9E26-96A0ECDC6649}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.110622-1506
    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
    2007 Microsoft Office system - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_70AFE6BE-656-80070057_E2AD56EA-815-80070057

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\PROGRA~2\AOLDES~1.6\aol.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>{AF38C35E-CF39-4888-9E26-96A0ECDC6649}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3Q6C9</PKey><PID>00359-OEM-8992687-00010</PID><PIDType>2</PIDType><SID>S-1-5-21-192566122-1382187156-2896854108</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>AW017AV-ABA e9200z</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>5.03</Version><SMBIOSVersion major="2" minor="6"/><Date>20090911000000.000000+000</Date></BIOS><HWID>13E93E07018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-CPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0031-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>2007 Microsoft Office system</Name><Ver>12</Ver><Val>8E24F7C38C1C168</Val><Hash>/ov8Wgn6HV29d2327DYFxvIGRgw=</Hash><Pid>89451-OEM-6618086-20193</Pid><PidType>4</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-->
    On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x80070003' to display the error text.
    Error: 0x80070003

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 10:27:2011 13:47
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Not Registered - 0x80070003
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: LgAAAAIAAAABAAEAAQABAAAAAgABAAEAln10PPIvLGbuM5BTmAgG/nCBTAGOLg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   HPQOEM  SLIC-CPC
      FACP   HPQOEM  SLIC-CPC
      HPET   HPQOEM  SLIC-CPC
      MCFG   HPQOEM  SLIC-CPC
      SLIC   HPQOEM  SLIC-CPC
      OEMB   HPQOEM  SLIC-CPC
      SSDT   HPQOEM  SLIC-CPC

     

    Tuesday, November 1, 2011 6:32 PM
  • "Lee813" wrote in message news:6e004d62-ba84-427c-afa5-74d8cce101bb...

    Sorry about that.  Here it is again:

     

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

    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0x80070003
    Windows Product Key: *****-*****-73CQT-WMF7J-3Q6C9
    Windows Product Key Hash: KaFG+RmurcM3ZxzWyfEP9WtPUJw=
    Windows Product ID: 00359-OEM-8992687-00010
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010300.1.0.003

     

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\PROGRA~2\AOLDES~1.6\aol.exe

    Other data—>
    SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>AW017AV-ABA e9200z</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>5.03</Version><SMBIOSVersion major="2" minor="6"/><Date>20090911000000.000000+000</Date></BIOS

     

    Licensing Data-->
    On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x80070003' to display the error text.
    Error: 0x80070003

     

     

    I am not an expert in AOL – but the version of their browser that appears to be in use here seems to be extremely old, and I can’t help wondering if it’s even compliant with any recent internet standard, let alone Windows 7. Perhaps they’ve changed their numbering system, but I can’t think that they are that stupid (Oh – hang on, this *is* AOL we’re talking about!).......
     
     
    Your problem is the error message highlighted above, which translates as ‘The system cannot find the path specified’ – which is not terribly useful
     
    This could well be the result of malware or disk problems.
    let’s start with checking the disk.
    I would suggest running CHKDSK and SFC (assuming that you’ve already tried a System Restore?)
    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
    CHKDSK C: /R
    and hit the Enter key
    You will be told that the drive is locked, and the CHKDSK will run at he 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 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.
     
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, November 1, 2011 8:39 PM
    Moderator
  • Noel, I am interested in how you figured out the AOL browser version.  All I can see from the report is the path to AOL.exe given in DOS (8 character) names.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, November 1, 2011 8:57 PM
    Answerer
  • "Cbarnhorst" wrote in message news:773cd7d1-1fa3-441f-a5bc-80a270a28e79...
    Noel, I am interested in how you figured out the AOL browser version.  All I can see from the report is the path to AOL.exe given in DOS (8 character) names.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
     
    AOLDES~1.6
     
    The 8.3 filename is actually a folder name – with a .6 extension, contrary to the normal rules.
    No-one in their right minds does that nowadays (and OK, AOL is not known for sense<g>) so it must be an old installation, or one that has been frequently updated (assuming they use the extension to differentiate between builds – nothing would surprise me about AOL!)
    Either way, it looks very odd to me (I used to be a rare AOL supporter back-in-the-day of dialup on toll-free numbers). AOL were never good at versioning, and the browser was always a skin on IE – I always logged on using AOL, then minimised it and used IE for real browsing.
     
    This is actually the first MGADiag report I recall seeing that references the AOL browser – so I could well be far off the mark (again<g>)
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, November 1, 2011 9:48 PM
    Moderator
  • AOL probably hangs on to old ways for compatibility purposes.  I had to use the 8.3 folder names to install Creative Studio 3 on Vista x64 back in 2007 so AOL is not alone.  CS Setup was not parsing the parentheses in the long forum, Program (x86), so I had to use the 8.3 form, Progra~2.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, November 1, 2011 10:06 PM
    Answerer
  • The AOL that I have is the latest version and just installed on a clean install.  I had problems with AOL after I cleaned up the virus and did the system restore with Acronis, so I uninstalled and started over.  I have run AVG and also Malwarebytes and the system appears to be clean at this time.  Since I did the restore is when this problem on not having a genuine copy of Windows started.  It had always been fine before that. 

    I'll try running the ChkDsk and see what happens.  Everytime I run Runeup Utilities, it finds errors in the registry and when I click the "fix-it" and it supposedly fixes those errors, then it is fine for a few hours but the error message eventually returns.

     

     

    Tuesday, November 1, 2011 10:53 PM
  • "Lee813" wrote in message news:d2f6abf0-ecc8-4573-b39c-f5f0cba543b6...

     

    Everytime I run Runeup Utilities, it finds errors in the registry and when I click the "fix-it" and it supposedly fixes those errors, then it is fine for a few hours but the error message eventually returns.

     

     

    There’s the cause of your problems!
    DO NOT, EVER, run Registry ‘Cleaners’ – they’re like bleach that destroys cotton fabric!
    UNDO any changes that this rubbish has made to your system (if you can) either by using whatever undo function comes with it, or by using System Restore.
    Then UNINSTALL it.
     
    Then post back with a new MGADiag report.
     
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, November 1, 2011 11:06 PM
    Moderator
  • Please review: Cleaning a Compromised System
    Carey Frisch
    Tuesday, November 1, 2011 11:08 PM
    Moderator
  •  

    I'll try running the ChkDsk and see what happens.  Everytime I run Runeup Utilities, it finds errors in the registry and when I click the "fix-it" and it supposedly fixes those errors, then it is fine for a few hours but the error message eventually returns.

     

     

    Those "error" messages are simply Windows writing temp registry entries for all kinds of housekeeping.  Once the task is done the registry entries are "orphaned" and clever registry cleaner devs make sure that all these registry paths that no longer lead to anything show up in a report to you as "errors".  That is how the commercial registry cleaners sell themselves online.  They offer a diagnosis that is always going to result in a report that lists "errors".  Such reports are designed to create a bit of anxiety about the health of your computer so that you will buy the product.  Obsolete registry entries are not errors and removing them or not does not affect Windows performance because the entry is never consulted again. 

    On the other hand, registry cleaners do make mistakes and sometimes bad ones.

    If you think you have an error in your registry that is affecting Windows or a program then you should track down the problematic entry and fix it.  Never "fix" the registry as a whole.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, November 1, 2011 11:09 PM
    Answerer
  • No further reply from the Original Poster.

    Issue is assumed to be resolved.


    Darin MS
    • Marked as answer by Darin Smith MS Tuesday, November 8, 2011 12:16 AM
    Tuesday, November 8, 2011 12:15 AM