windows 2008 R2 Virtual says me NOT GENUINE RRS feed

  • Question

  • Hallo everyone,

    In a virtual environment, i have a phisical host running Windows 2008 R2 Enterprise Ed. and a virtual Windows 2008 R2 Enterprise.

    OS is a oem version by fujitsu and i have 2 activation keys, one for phisical and one for virtual.

    After few days from installation of virtual os, at logon wga says me that the version is not genuine, what can i do?


    This is result of MGADT:




    Diagnostic Report (1.9.0027.0):


    Windows Validation Data-->


    Validation Code: 50

    Cached Online Validation Code: N/A, hr = 0xc004f012

    Windows Product Key: *****-*****-JTHXK-FMFQ4-2DQDR

    Windows Product Key Hash: LEzM6mdmVylFoZityJCnV3Orh/o=

    Windows Product ID: 00486-OEM-8400691-20133

    Windows Product ID Type: 2

    Windows License Type: OEM SLP

    Windows OS version: 6.1.7600.2.00030112.0.0.010

    ID: {3FDA1D48-1C4B-41DF-A852-62D421F586F8}(1)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows Server 2008 R2 Enterprise

    Architecture: 0x00000009

    Build lab: 7600.win7_gdr.100618-1621

    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)\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-->

    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]

    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]

    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]

    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]


    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{3FDA1D48-1C4B-41DF-A852-62D421F586F8}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00030112.0.0.010</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-2DQDR</PKey><PID>00486-OEM-8400691-20133</PID><PIDType>2</PIDType><SID>S-1-5-21-3325572-1836309459-3970571272</SID><SYSTEM><Manufacturer>Microsoft Corporation</Manufacturer><Model>Virtual Machine</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>090004 </Version><SMBIOSVersion major="2" minor="3"/><Date>20090319000000.000000+000</Date></BIOS><HWID>3EBA3607018400F4</HWID><UserLCID>0410</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>VRTUAL</OEMID><OEMTableID>MICROSFT</OEMTableID></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.7600.16385


    Name: Windows Server(R), ServerEnterprise edition

    Description: Windows Operating System - Windows Server(R), OEM_SLP channel

    Activation ID: ea36520d-fbfe-4042-acd8-fe926781b615

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 00486-00168-006-920133-02-1040-7600.0000-2602010

    Installation ID: 014466383114216040695734606662175171672125078563916762

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344

    Partial Product Key: 2DQDR

    License Status: Notification

    Notification Reason: 0xC004F07C.

    Remaining Windows rearm count: 2

    Trusted time: 21/10/2010 10:15:19


    Windows Activation Technologies-->

    HrOffline: 0x00000000

    HrOnline: N/A

    HealthStatus: 0x0000000000000000

    Event Time Stamp: N/A

    ActiveX: Not Registered - 0x80040154

    Admin Service: Not Registered - 0x80040154

    HealthStatus Bitmask Output:



    HWID Data-->



    OEM Activation 1.0 Data-->



    OEM Activation 2.0 Data-->

    BIOS valid for OA 2.0: yes

    Windows marker version: 0x0

    OEMID and OEMTableID Consistent: yes

    BIOS Information: 

      ACPI Table Name OEMID Value OEMTableID Value









    Thanks in advance

    Andrea Canzian



    Andrea Canzian MCP
    Thursday, October 21, 2010 8:41 AM


  • Hi, I do not know how the license for the virtual install is supposed to work, but the key in the report is an OEM SLP key and there is no marker in the virtualized bios, could you have gotten the keys mixed up?

    Anyway, if you continue to have problems then double check your keys, the one ending in JTHXK-FMFQ4-2DQDR is an SLP key, try changing keys to the other after verifying what I have just said.

    The key on the report is the SLP key, it should be the key that was used in the OEM install, the key on the sticker located on the case is the COA key which is used for backup activation if SLP activation fails. I have no knowledge of any other key given for virtual installations of the software and I would not suggest using the COA key, that would invalidate it for future use, do not use the key from the sticker on the computer for the virtualized install

    • Marked as answer by Andrea Canzian Thursday, October 21, 2010 1:58 PM
    Thursday, October 21, 2010 1:02 PM