Windows 7 Pro x64 Not Genuine Pop-ups

Page 1 of 2 12 LastLast

  1. Posts : 512
    Windows 7 Professional x64 SP1
       #1

    Windows 7 Pro x64 Not Genuine Pop-ups


    Hi,

    I'm getting indications that my Windows 7 Pro x64 software is not genuine. I've contacted Microsoft four times and they have confirmed the license and reactivated my already activated system.

    I believe their reactivation efforts caused a corrupted slui.exe file, that was resolved in the below thread.

    https://www.sevenforums.com/performan...can-t-fix.html

    The corrupted slui.exe issue is resolved, but I still get the indications that my Windows is not Genuine.

    The Microsoft Genuine Advantage Diagnostic Tool information follows:

    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-9CBQQ-CBRDX-4VBW4
    Windows Product Key Hash: 4o79yMzf+5/lHKmwIiotxng2nPc=
    Windows Product ID: 00371-OEM-9045181-41077
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {88569B0E-21CB-4760-A2CC-9595DA52037D}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows 7 Professional
    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: 100 Genuine
    Microsoft Office Professional 2007 - 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_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.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>{88569B0E-21CB-4760-A2CC-9595DA52037D}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-4VBW4</PKey><PID>00371-OEM-9045181-41077</PID><PIDType>3</PIDType><SID>S-1-5-21-764048772-141219837-185285450</SID><SYSTEM><Manufacturer>INTEL_</Manufacturer><Model>DX58SO__</Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>SOX5810J.86A.5600.2013.0729.2250</Version><SMBIOSVersion major="2" minor="5"/><Date>20130729000000.000000+000</Date></BIOS><HWID>92393407018400FE</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/><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>1B16FCA35E8C714</Val><Hash>Ox0izo7MjcnLKUdV4ul5G/4OhBY=</Hash><Pid>81605-906-5273533-65430</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-->
    Software licensing service version: 6.1.7601.17514
    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activation ID: e120e868-3df2-464a-95a0-b52fa5ada4bf
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00180-451-841077-02-1033-7601.0000-2132014
    Installation ID: 021892549173720063162803583281194772514004932426885526
    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: 4VBW4
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 02-Aug-14 20:29:17
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
     
    HWID Data-->
    HWID Hash Current: MgAAAAMAAAABAAEAAQACAAAAAgABAAEACrYw0kNG2mNsQ7K6xFcOLJyfvSCl9qae6oI=
    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   INTEL   DX58SO  
      FACP   INTEL   DX58SO  
      HPET   INTEL   DX58SO  
      MCFG   INTEL   DX58SO  
      WDDT   INTEL   DX58SO  
      ASF!   INTEL   DX58SO  
      SSDT   INTEL   SSDT  PM
      DMAR   INTEL   DX58SO  
      WDTT   INTEL   DX58SO  
      ASPT   INTEL   PerfTune
    I'm seeking assistance to resolve this non-genuine Windows issue.

    Thank you for your assistance.

    Regards
      My Computer


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


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

    There's nothing wrong with the report - you shouldn't be seeing any non-genuine notifications?
    Is it just the black background?
      My Computer


  4. Posts : 512
    Windows 7 Professional x64 SP1
    Thread Starter
       #4

    NoelDP said:
    There's nothing wrong with the report - you shouldn't be seeing any non-genuine notifications?
    Is it just the black background?
    After I followed your Windows Repair instructions (properly) described in the referenced thread above for the corrupted slui.exe file and confirmed the fix with SFC, I did a complete disk clean-up and rebooted multiple times. On the first or second reboot, I saw the non-genuine indication in white text on the lower right corner of black screen just after the black Starting Windows screen. I've probably rebooted in excess of ten times and I only saw that text one time. After multiple reboots with no additional non-genuine indications I thought it was just a momentary blip that won't appear again unless I have another major issue or change some hardware. I've seen that text before after changing hardware.

    Then, after about two hours after the fix, the following pop-up appeared again.

    Attachment 327950

    I just cancelled the pop-up and it hasn't reappeared yet, but that is the pattern. It will pop-up, I'll clear or cancel the pop-up and it will reappear in the next 24 to 48 hours.

    I'll report the next time it pops-up by posting here.

    Should I run the MGA diagnostic utility during the next non-genuine pop-up incident?

    Regards
      My Computer


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

    Sounds like a race condition to me - check what's running in the background.
    What AV are you using?
      My Computer


  6. Posts : 512
    Windows 7 Professional x64 SP1
    Thread Starter
       #6

    NoelDP said:
    Sounds like a race condition to me - check what's running in the background.
    What AV are you using?
    I'm running ESET Smart Security 7 and I have Windows Defender set to scan daily. I also have SuperAntiSpywarePro loaded, but it's not set to do any scanning. I've been running these AV programs for the past several years without any conflict issues.

    As for what's running in the background, I've taken the following screen shot of the Task Manager Processes tab.

    Attachment 327952
    Last edited by tjg79; 07 Aug 2014 at 00:17.
      My Computer


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

    I'd have thought that ESET would switch Defender off? It may be a conflict there, as they could be fighting over the same file for checking at boot, and blocking the activation tests.
      My Computer


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

    I would highly suggest turning Windows Defender off.

    I'm surprised that Eset didn't turn it off.
      My Computer


  9. Posts : 512
    Windows 7 Professional x64 SP1
    Thread Starter
       #9

    About two weeks ago, I got a blue screen on shutdown. The instructions on the blue screen indicated that if this was the first time (it was) then just to restart Windows. I did and didn't see any issues.

    I've checked with ESET on their forum and they indicated that ESET SS and Windows Defender are compatible. They work in conjunction together. I've been running ESET and Defender for the past five years (On Win XP before I upgraded to Win 7) and I haven't had any conflicts that I can recall.

    I've also been running Intel RAID for the past five years without any issues that weren't a result of hdd hardware/firmware failures.
      My Computer


  10. Posts : 512
    Windows 7 Professional x64 SP1
    Thread Starter
       #10

    Layback Bear said:
    I attribute that issue to Microsoft reactivating my "fake" Windows 7. Microsoft Support insisted I pay for paid support to fix the SFC issue that was a result of their reactivation actions.
      My Computer


 
Page 1 of 2 12 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 18:09.
Find Us