locked
Frequent "Windows 7 build 7601 This copy of Windows is not genuine" notifications RRS feed

  • Question

  • This issue just keeps reoccurring. I am a software tester, and have several virtual machines running versions of Windows for  various test scenarios. I am using the keys assigned to me. Frequently, out of the blue, when I start up a VM, I get the "Windows 7 build 7601 This copy of Windows is not genuine" notification. Sometimes restarting the VM fixes the problem, other times it 'sticks'. I seem to recall this happening with other versions of Windows, too. This is a huge waste of time. How can I make sure my genuine windows installations remain genuine?

    (I understand the following is required on all posts to this forum. So ... )=====

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

    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-WVG2K-CVBYR-KY48X
    Windows Product Key Hash: GLs+dTwKm7kFEZRx5gPK6qBu6ms=
    Windows Product ID: 00426-383-1108083-06384
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {39C5A454-8163-46FB-B618-29ED8CD87C67}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000000
    Build lab: 7601.win7sp1_gdr.130828-1532
    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 Ultimate 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_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>{39C5A454-8163-46FB-B618-29ED8CD87C67}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-KY48X</PKey><PID>00426-383-1108083-06384</PID><PIDType>5</PIDType><SID>S-1-5-21-224419172-3425685319-1612329413</SID><SYSTEM><Manufacturer>innotek GmbH</Manufacturer><Model>VirtualBox</Model></SYSTEM><BIOS><Manufacturer>innotek GmbH</Manufacturer><Version>VirtualBox</Version><SMBIOSVersion major="2" minor="5"/><Date>20061201000000.000000+000</Date></BIOS><HWID>99E53A07018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central America 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-002E-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Ultimate 2007</Name><Ver>12</Ver><Val>14E8615322D7EC4</Val><Hash>Q1LOeARBMB+zMR9nesAgate+zhM=</Hash><Pid>81608-866-8102944-65155</Pid><PidType>8</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"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" 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, 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-110808-00-1033-7601.0000-2672013
    Installation ID: 016873535312918705442215862920556675249651054941464572
    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: KY48X
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 3/13/2014 10:14:44 AM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 2:19:2014 07:53
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MAAAAAEABAABAAEAAAABAAAAAQABAAEAJJRQ9bytBgzmt/7bJGaoW3bodvkcMdpH

    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
      FACP            VBOX          VBOXFACP
      SSDT            VBOX          VBOXCPUT


    Thursday, March 13, 2014 4:18 PM

Answers

  • There's no obvious problem evident in your report.

    Please run the tool again when you next see the notification (it may even fix it!), and post the resulting report.

    This sort of behaviour can happen in a VM where the machine is built up over a number of snapshots - and may be caused by the changes that the VM goes through at boot.

    I've found that creating a new snapshot after a couple of reboots, to bed the activation in properly, will often eliminate the problem.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Thursday, March 13, 2014 4:29 PM
    Moderator

All replies

  • There's no obvious problem evident in your report.

    Please run the tool again when you next see the notification (it may even fix it!), and post the resulting report.

    This sort of behaviour can happen in a VM where the machine is built up over a number of snapshots - and may be caused by the changes that the VM goes through at boot.

    I've found that creating a new snapshot after a couple of reboots, to bed the activation in properly, will often eliminate the problem.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Thursday, March 13, 2014 4:29 PM
    Moderator
  • Thank you for replying.

    What triggers Windows checking for 'genuine-ness', and what would make it think it was not genuine?

    Friday, March 14, 2014 8:10 PM
  • the WAT update 'phones home' about every 90 days to check the state of the current system, according to very tight and specific parameters.

    If it finds errors, it will flag the system as not genuine.

    ALSO on every boot, the system does a quick check to ensure that certain files are in the correct version, with the correct content - and will flag if this is not correct. It will also flag a problem if the system prevents proper evaluation within an acceptable time limit.

    This means that there are a number of conditions which will trigger a non-genuine status, while there is in fact nothing amiss.

    The most common of these is an over-zealous Anti-Virus - or other security software.

    next comes malware which may be emulating parts of Windows.

    after that, there are sundry file or registry errors which could cause the problem.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Saturday, March 15, 2014 5:07 PM
    Moderator