locked
Windows 7 Upgrade from XP not Validating error: 0xC004F035 RRS feed

  • Question

  • I have recently upgraded an older system from Windows XP to Windows 7.  However, it will not activate and gives an error: 0xC004F035

    I have updated other systems using the same process and was successful.  The key that is entered is for a KMS server. 

    To my uneducated eyes it looks as though the BIOS is not compatible(from the log file).  Is there any workaround?

     

    The MGADiag log follows:

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

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85689
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7600.2.00010100.0.0.004
    ID: {6BB1CF05-8C60-481B-9B99-65FFEFD14D91}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Enterprise
    Architecture: 0x00000000
    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: 100 Genuine
    Microsoft Office Enterprise 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

    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-->
    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>{6BB1CF05-8C60-481B-9B99-65FFEFD14D91}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.004</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-HVTHH</PKey><PID>00392-918-5000002-85689</PID><PIDType>1</PIDType><SID>S-1-5-21-411282545-2473339529-864648035</SID><SYSTEM><Manufacturer>LENOVO</Manufacturer><Model>892228U</Model></SYSTEM><BIOS><Manufacturer>LENOVO</Manufacturer><Version>63ET62WW</Version><SMBIOSVersion major="2" minor="4"/><Date>20070430000000.000000+000</Date></BIOS><HWID>5DBB3607018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>LENOVO</OEMID><OEMTableID>TP-63   </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>B365E959A4CA586</Val><Hash>E83FebUP27hx8YBUMGm9qHfnVRQ=</Hash><Pid>89388-707-0633252-65690</Pid><PidType>14</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.7600.16385

    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: ae2ee509-1b34-41c0-acb7-6d4650168915
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00392-00170-918-500000-03-1033-7600.0000-3612009
    Installation ID: 002072836171738514946035173030148864922964667661462752
    Partial Product Key: HVTHH
    License Status: Initial grace period
    Time remaining: 33120 minute(s) (23 day(s))
    Remaining Windows rearm count: 0
    Trusted time: 11/29/2010 10:14:49 AM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

    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-->
    HWID Hash Current: OgAAAAIABQABAAIAAAABAAAAAwABAAEAJJRw1luAvvDqTtRMUAjWGV7NFN644ZpTYMWypc4g4kf4Gg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            INTEL         TP-63  
      FACP            INTEL         TP-63  
      DBGP            LENOVO        TP-63  
      HPET            INTEL         TP-63  
      BOOT            PTLTD         TP-63  
      MCFG            INTEL         TP-63  
      TCPA            Phoeni        TP-63  
      SLIC            LENOVO        TP-63  
      APIC            INTEL         TP-63  
      SSDT            SataRe        SataPri
      SSDT            SataRe        SataPri
      SSDT            SataRe        SataPri
      SSDT            SataRe        SataPri
      SSDT            SataRe        SataPri


     

    Monday, November 29, 2010 7:41 PM

Answers

  • Actually, in this case, the BIOS is relevant.


    "The software Licensing Service reported that the computer could not be activated with a Volume license product key. Volume licensed systems require upgrading from a qualified operating system . Please contact your system administrator or use a different type of key."

    As it says, Volume Licenses (such as KMS) must be upgraded from a qualified OS.  My understanding is that that the Qualified OS referred to here is an OEM SLP activated OS.  Meaning the base OS (that the Volume License software is upgraded from) must be a self-activating, OEM SLP using OS. 

    As seen in the Diagnostic Report "BIOS valid for OA 2.0: no, invalid SLIC table" the current Bios doesn't have the SLIC Table to enable the OEM SLP  key to Self-Activate.  And since the OEM SLP key can't be used, the OS is not a "Qualified OS" for KMS software.

    Unfortunately I don't know how to resolve this issue. I support consumer level software and the information I provided regarding KMS/Volume Licensing is just what I have picked up along the way. I recommend posting in the MSDN and/or Technet forums where people, more familiar with enterprise level software, may be able to provide better assistance.

    MSDN Forums: http://social.msdn.microsoft.com/Forums/en-US/categories/ 

    Technet Forums: http://social.technet.microsoft.com/Forums/en-us/categories

     

    Sorry I couldn't be more help,


    Darin MS
    Friday, December 3, 2010 9:27 PM

All replies

  • Monday, November 29, 2010 7:56 PM
    Moderator
  • Thank you, I have reviewed.  The KMS server seems to be operating fine and we have plenty of licenses available.  Additionally, I just did a fresh install on the same make/model and it activated fine, even with an older BIOS.  I tried rolling the problem systems BIOS back to the same version, but I'm still getting an error.

     

    Monday, November 29, 2010 9:33 PM
  • "Igofast" wrote in message news:581c9f87-7066-4526-a962-12251e103d8a...

    Thank you, I have reviewed.  The KMS server seems to be operating fine and we have plenty of licenses available.  Additionally, I just did a fresh install on the same make/model and it activated fine, even with an older BIOS.  I tried rolling the problem systems BIOS back to the same version, but I'm still getting an error.

     


    The BIOS is irrelevant in terms of external activation - it only matters for OEM_SLP keys, which self-activate.
     

    Error code 0xC004F035

    <SCRIPT type=text/javascript> loadTOCNode(2, 'moreinformation'); </SCRIPT>

    Symptom

    <SCRIPT type=text/javascript> loadTOCNode(3, 'moreinformation'); </SCRIPT> When you try to use a KMS client or a KMS host to activate one or more computers, you may receive the following error message:
    0xC004F035
    The software Licensing Service reported that the computer could not be activated with a Volume license product key. Volume licensed systems require upgrading from a qualified operating system. Please contact your system administrator or use a different type of key.

    Cause

    <SCRIPT type=text/javascript> loadTOCNode(3, 'moreinformation'); </SCRIPT> This issue may occur because volume editions are licensed for upgrade only. Installation of a volume operating system on a computer that does not have a qualifying operating system installed is not supported.

    Workaround

    <SCRIPT type=text/javascript> loadTOCNode(3, 'moreinformation'); </SCRIPT> To work around this issue, install a qualifying version of a Microsoft operating system, and then reinstall the volume operating system.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, November 30, 2010 6:03 AM
    Moderator
  • Actually, in this case, the BIOS is relevant.


    "The software Licensing Service reported that the computer could not be activated with a Volume license product key. Volume licensed systems require upgrading from a qualified operating system . Please contact your system administrator or use a different type of key."

    As it says, Volume Licenses (such as KMS) must be upgraded from a qualified OS.  My understanding is that that the Qualified OS referred to here is an OEM SLP activated OS.  Meaning the base OS (that the Volume License software is upgraded from) must be a self-activating, OEM SLP using OS. 

    As seen in the Diagnostic Report "BIOS valid for OA 2.0: no, invalid SLIC table" the current Bios doesn't have the SLIC Table to enable the OEM SLP  key to Self-Activate.  And since the OEM SLP key can't be used, the OS is not a "Qualified OS" for KMS software.

    Unfortunately I don't know how to resolve this issue. I support consumer level software and the information I provided regarding KMS/Volume Licensing is just what I have picked up along the way. I recommend posting in the MSDN and/or Technet forums where people, more familiar with enterprise level software, may be able to provide better assistance.

    MSDN Forums: http://social.msdn.microsoft.com/Forums/en-US/categories/ 

    Technet Forums: http://social.technet.microsoft.com/Forums/en-us/categories

     

    Sorry I couldn't be more help,


    Darin MS
    Friday, December 3, 2010 9:27 PM
  • (benefit of 20/20 hindsight, and a lot more knowledge)

    Just in case anyone trips across this thread, here's the cause and resolution...

    1) Cause: A KMS activation of Windows 7 looks for a SLIC table to confirm eligibility - if it finds one, it must be valid. The SLIC table here is not valid, and so KMS activation fails.

    2) Resolution

    Either

    a) change the Volume License Key to a MAK type and activate against the Microsoft servers

    or

    b) resolve the error in the SLIC table - this may mean reflashing the BIOS, contacting the manufacturer for assistance, or simply reinstalling the OS.

    Hope that helps someone!


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

    Saturday, December 28, 2013 11:23 AM
    Moderator