Windows 7: "Windows is not genuine" error, ran most tests still errors


  1. Posts : 4
    windows 7 home premium 64bit
       #1

    Windows 7: "Windows is not genuine" error, ran most tests still errors


    My computer crashed and wouldn't boot back up. I ran some scans and got it to boot, however it tells me that my Windows is not Genuine I ran chkdsk C: /r in an elevated prompt then ran sfc/scannow in an elevated prompt as well. Then I used the checksur tool from Microsoft. The diagnostic file is from after I ran all of these scans. There are no updates to install so no errors that I can post.


    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Code:
    Windows Validation Data-->
    
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-BWX2H-6JFK2-QQVCT
    Windows Product Key Hash: Kh/qFa9XWKuiYBeWJM1y3aS7bAk=
    Windows Product ID: 00359-OEM-8703046-32264
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {7C01003D-F4CD-4E0E-BBC8-E1437FE7BEF4}(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.141211-1742
    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-->
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{7C01003D-F4CD-4E0E-BBC8-E1437FE7BEF4}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-QQVCT</PKey><PID>00359-OEM-8703046-32264</PID><PIDType>3</PIDType><SID>S-1-5-21-4083210228-1935258850-3389655937</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1402</Version><SMBIOSVersion major="2" minor="7"/><Date>20140321000000.000000+000</Date></BIOS><HWID>5C0A3707018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07: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-432264-02-1033-7600.0000-0622014
    Installation ID: 006236125383283391231826988556316362496391267605290721
    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: QQVCT
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 1/23/2015 2:36:11 PM
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 12:4:2014 00:25
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: MAAAAAEAAQABAAEAAAAEAAAAAQABAAEAHKLU9kqKClP6KRbLips+k5iQF/Ok1C5z
    
    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			ALASKA		A M I
      FACP			ALASKA		A M I
      HPET			ALASKA		A M I
      MCFG			ALASKA		A M I
      FPDT			ALASKA		A M I
      SSDT			SataRe		SataTabl
      BGRT			ALASKA		A M I
      SSDT			SataRe		SataTabl
      SSDT			SataRe		SataTabl
    Last edited by benchwarrior; 23 Jan 2015 at 22:02.
      My Computer


  2. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #2

    Please complete this tutorial by Brink and post it here.
    Our experts will need to take a look at it.

    Windows Genuine and Activation Issue Posting Instructions
      My Computer


  3. Posts : 4
    windows 7 home premium 64bit
    Thread Starter
       #3

    Thanks for the links. I edited the post should be up to par now.
      My Computer


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

    Hmm...
    CheckSUR shows these problems.
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_39eb8a414c1c62e1498a17a84a023a82_31bf3856ad364e35_6.1.7601.18640_none_732593940dec34d5.manifest
     winsxs\manifests\amd64_0e18f0866438a6e4b74b845fa4568470_31bf3856ad364e35_6.1.7601.22846_none_4db9ef9da6021a1e.manifest
     winsxs\manifests\amd64_be7aa94dc5c7cd8401392d086fcb81f4_31bf3856ad364e35_6.1.7601.18656_none_cca83b1c9cac3c4b.manifest
     winsxs\manifests\amd64_b4edc3d043314a56fdbafad6e06df14d_31bf3856ad364e35_6.1.7601.18648_none_c6e127073ecb1339.manifest
     winsxs\manifests\amd64_55a0b079bf7a9988040264e300798201_31bf3856ad364e35_6.1.7601.18656_none_c886afb80d251ff0.manifest
     winsxs\manifests\amd64_de48c12b1ee28246c1c4f57a19d6ea36_31bf3856ad364e35_6.1.7601.22856_none_ae7480221f5ce5d2.manifest
     winsxs\manifests\amd64_709e16f27ba69b57c1b7e4dab62483e7_31bf3856ad364e35_6.1.7601.18619_none_476c7b2ba8e8aa9e.manifest
     winsxs\manifests\amd64_64f1268ac63816d334b6731f6821a6f2_31bf3856ad364e35_6.1.7601.22865_none_2c837590554c9b45.manifest
     winsxs\manifests\amd64_caa61a52c414e34a6485d91cca61418d_31bf3856ad364e35_11.2.9600.17509_none_e464296f0266b091.manifest
     winsxs\manifests\amd64_cb34934faac5fa95f7a92be2a00d7e55_31bf3856ad364e35_6.1.7601.18656_none_817084b328aaf6de.manifest
     winsxs\manifests\amd64_009d2bc9d8033c3a3fea3971da0fdbdb_31bf3856ad364e35_6.1.7601.22863_none_2b351d4f0800e26f.manifest
     winsxs\manifests\amd64_852256bfd66578cd41a92df1aed2eab0_31bf3856ad364e35_6.1.7601.18656_none_31b971a5e887145f.manifest
     winsxs\manifests\amd64_c7757e020f7a4ba8b4143f345cee80c8_31bf3856ad364e35_6.1.7601.22863_none_e86ce5290f7d358c.manifest
     winsxs\manifests\amd64_be46c260ed3feac15d24bdf9f2212505_31bf3856ad364e35_6.1.7601.18658_none_2c7f837bc2410781.manifest
     winsxs\manifests\amd64_822517633880ba72795f54c3e9517b85_31bf3856ad364e35_6.1.7601.22863_none_3e64f309ec751fea.manifest
     winsxs\manifests\amd64_aa60a096aaf186b831bc26bed846bb83_31bf3856ad364e35_6.1.7601.22863_none_b72a9aca2ebd5a13.manifest
     winsxs\manifests\amd64_70ba546a6eb85b9e456de7405e1fd152_31bf3856ad364e35_6.1.7601.22826_none_838fe82904e84f2e.manifest
     winsxs\manifests\amd64_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7601.22865_none_48b848380bfa8bbd.manifest
     winsxs\manifests\wow64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.18640_none_04b5592f57ddfbfe.manifest
     winsxs\manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_f4c171fd1bd9961e.manifest
     winsxs\manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_f444a3cc02b20fea.manifest
     winsxs\manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_50e00d80d4370754.manifest
     winsxs\manifests\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.22826_none_3360df98112c1ae9.manifest
     winsxs\manifests\wow64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.22846_none_0544f99c70f630f9.manifest
     winsxs\manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.18656_none_7d98b23954b11659.manifest
     winsxs\manifests\amd64_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7601.18658_none_483c7a50f2d21ee0.manifest
     winsxs\manifests\amd64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.18640_none_fa60aedd237d3a03.manifest
     winsxs\manifests\wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.22863_none_7e1480206dd98336.manifest
     winsxs\manifests\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.18619_none_32e511b0f803ae0c.manifest
     winsxs\manifests\amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.22863_none_73bfd5ce3978c13b.manifest
     winsxs\manifests\amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.18619_none_2890675ec3a2ec11.manifest
     winsxs\manifests\amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.22826_none_290c3545dccb58ee.manifest
     winsxs\manifests\wow64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.17509_none_1c00d80763777475.manifest
     winsxs\manifests\amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.18656_none_734407e72050545e.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.17509_none_11ac2db52f16b27a.manifest
     winsxs\manifests\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.22863_en-us_e1edd162b1ad35f8.manifest
     winsxs\manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_50633f4fbb0f8120.manifest
     winsxs\manifests\amd64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.22846_none_faf04f4a3c956efe.manifest
     winsxs\manifests\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18656_en-us_855367f7e02757e5.manifest
     winsxs\manifests\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18656_en-us_e172037b9884c91b.manifest
     servicing\packages\Package_109_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_110_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_113_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_114_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB3006625~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB3025390~31bf3856ad364e35~amd64~~11.2.1.0.mum
     servicing\packages\Package_2_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_39_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_74_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3006625_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3006625~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3009736_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3013410_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
     servicing\packages\Package_for_KB3014406_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3025390_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
     servicing\packages\Package_for_KB3025390~31bf3856ad364e35~amd64~~11.2.1.0.mum
    SFC shows nothing apart from similar errors
    I'll post a fix protocol later.
      My Computer


  5. Posts : 4
    windows 7 home premium 64bit
    Thread Starter
       #5

    whoops forgot about this. let me tell you what has happened since i posted this. I used another computer and grabbed the manual updates for vipre anti-virus. Ran a full scan with it and it started to quarantine a trojan called js.kryptik.atb. The kryptik virus' are known for being a nasty rootkit. And none of my anti-virus can uninstall it. I'm probably going to end up doing a clean install of windows unless you guys have someone who can help me get rid of it manually.
      My Computer


  6. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #6

    In my opinion once you have a rootkit a Clean Install should be done. You also must be careful after you do the install not to move saved things back into the computer. They can also be infected. Unless you know the exact date of the infection I also wouldn't use any backups. They also may be infected.

    I have not heard a lot of good things about Viper anti virus.
      My Computer


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

    Vipre used to be highly respected - it came from the same stable as a VERY good firewall (kerio?).
    I've not heard much about it in the past few years.
      My Computer


  8. Posts : 4
    windows 7 home premium 64bit
    Thread Starter
       #8

    they're still pretty good. SAS, malwarebytes, avast and hitmanpro didn't even find traces of this sucker. i repeated all steps with them as well and no luck. I'd be willing to run some tests with different antivirus' before i clean install if you guys want to find the best one to find rootkit trojans. XD
    Last edited by benchwarrior; 24 Jan 2015 at 14:09.
      My Computer


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

    I'm with the Bear on this - a clean install is your optimal way forward.
      My Computer


  10. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #10

    NoelDP said:
    I'm with the Bear on this - a clean install is your optimal way forward.
    ...not forgetting to do a DISKPART CLEAN ALL prior to formatting and installing.

    Disk - Clean and Clean All with Diskpart Command

    You access DISKPART from the installation DVD by pressing SHIFT+F10 at the languages screen during installtion
      My Computer


 

  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 15:39.
Find Us