locked
Invalid BIOS for Vista Enterprise activation? RRS feed

  • Question

  • Hello there,

    I'm having problems with Vista Enterprise Edition activation.
    I've installed Vista (clean install) on a system purchased with an OEM XP Pro preinstalled. I've used a MAK key from an Open License SA contract. This caused no problems during installation and I even thought Vista was correctly activated during install but some time ago it reported problems activating Windows. The error I get is the following:

    Error Code: 0xC004F059

    Description: The Software Licensing Service reported that a license in the computer BIOS is invalid.

    Solutions include getting a new motherboard from the vendor (you're kidding, right?) or using a MAK key. Well... I am using a MAK key!?! Since I can now only enter RFM, I'm not sure how to run the diagnostic tool (read about it a bit late, sorry)

    I've got three more machines waiting to be upgraded to Vista with the same MAK (machines are from the same vendor, with the same XP Pro OEM licenses currently installed) but I can't risk locking them all out, and would not want to go through installing Vista just to have to reinstall XP since it's not working...

    Anyone an idea on how to proceed on this?

    Thank you in advance,

    Ben

    Thursday, January 4, 2007 11:11 AM

Answers

  • Please enter the MAK key again. Click on the change product key button and paste in the same key which you used to install Vista. This time it should activate on the first attempt.

    Maybe worth trying this and seeing if it works for you!

    Thursday, January 4, 2007 4:15 PM
    Moderator
  • Unfortunately, because this is a validation issues forum we don't have this much information on activation.  Could I ask you to contact Product Support Services ?  Thank you!
    Thursday, March 22, 2007 11:31 PM

All replies

  • Please enter the MAK key again. Click on the change product key button and paste in the same key which you used to install Vista. This time it should activate on the first attempt.

    Maybe worth trying this and seeing if it works for you!

    Thursday, January 4, 2007 4:15 PM
    Moderator
  • Helo Voluntary Contributor,

    Thank you very much, this indeed resolved the problem! Didn't Windows use the product key I entered the first time for some reason? It is the only key I have, so I'm pretty sure I entered it exactly the same the first time...

    Thanks again!

    Ben

    Friday, January 5, 2007 7:07 AM
  • Hello,

    I have the same error message when I try to activate Vista Business/Enterprise via KMS after upgrading the BIOS of

    3 ASUS P5B-VM mainboards to the latest version (0613). MAK activation works fine, but we want to use KMS activation on our campus.

    I thing there is a problem with the SLIC-informations.


    --------[ ACPI ]--------------------------------------------------------------------------------------------------------


      [ SLIC: Software Licensing Description Table ]

        ACPI Tabellen Eigenschaften:
          ACPI Signatur                                     SLIC
          Tabellenbezeichnung                               Software Licensing Description Table
          Speicheraddresse                                  3E790440h
          Tabellenlänge                                     374 Bytes
          OEM ID                                            MSTEST
          OEM Table ID                                      TESTONLY
          Creator ID                                        MSFT


    ------------------------------------------------------------------------------------------------------------------------

    A BIOS downgrade is not supported

    ------------------------------------------------------------------------------------------------------------------------

    Here is the report AFTER using MAK activation:

    Diagnostic Report (1.7.0012.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Detailed Status: 0x1
    Windows Product Key: *****-*****-BBBBB-BBBBB-BBBBB
    Windows Product Key Hash: 7n86V3QGhtY7XyNXmsOyS2HO8Yo=
    Windows Product ID: 55041-038-7044497-71315
    Windows Product ID Type: 6
    Windows License Type: Volume MAK
    Windows OS version: 6.0.6000.2.00010100.0.0.006
    ID: 11a65f5d-4551-4f97-b270-860a2cdd6e2d
    Is Admin: No
    AutoDial:
    Registry: 0x0
    WGA Version: Registered, 1.5.723.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Business
    Architecture: 0x00000000
    Build lab: 6000.vista_rtm.061101-2205
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    Notifications Data-->
    Cached Result: N/A
    File Exists: No
    Version: N/A
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    OGA Version: Registered, 1.6.21.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-138-80041013_025D1FF3-324-80040154_025D1FF3-269-80040154_025D1FF3-273-80070002

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.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>11a65f5d-4551-4f97-b270-860a2cdd6e2d</UGUID><Version>1.7.0012.0</Version><OS>6.0.6000.2.00010100.0.0.006</OS><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-038-7044497-71315</PID><PIDType>6</PIDType><SID>S-1-5-21-299502267-1645522239-1801674531</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0613   </Version><SMBIOSVersion major="2" minor="4"/><Date>20070118000000.000000+000</Date></BIOS><HWID>CC533807018400EA</HWID><UserLCID>0407</UserLCID><SystemLCID>0407</SystemLCID><TimeZone>Mitteleuropäische Zeit(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>MSTEST</OEMID><OEMTableID>TESTONLY</OEMTableID></OEM></MachineData>   <Software><Office><Result>100</Result><Products><Product GUID="{90120407-6000-11D3-8CFE-0050048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office XP Standard</Name><Ver>10</Ver><Val>A92D0FCC4D735E</Val><Hash>ASk7G3cC3tJBpN8b9EBNM4IjTXQ=</Hash><Pid>54213-640-0721112-17750</Pid><PidType>14</PidType></Product></Products></Office></Software></GenuineResults> 

    ------------------------------------------------------------------------------------------------------------------------

    Is there a way to bypass or reset these wrong SLIC data to use KMS activation?

    Regards

    KME

    Thursday, March 22, 2007 10:40 AM
  • Unfortunately, because this is a validation issues forum we don't have this much information on activation.  Could I ask you to contact Product Support Services ?  Thank you!
    Thursday, March 22, 2007 11:31 PM
  • My understanding of this error is that KMS cannot be used on a system that contains the OEM slic table. This table is used by OEMs in conjuction with a license certificate file merged into the OS in order to provide offline activation. If that table exists, KMS will refuse to work. I am facing the same issue. Technically, if the table exists, it should indicate that your OEM PC already has the license for the Vista, but in reality, there are many cases where this is not true. Some OEMs began to implement this with a certain BIOS revision. In my case, we have hundreds of new Dell pcs purchased with XP preinstalled but they cannot be upgraded to Vista via KMS. Rather, we can use a Dell Vista OEM disc to install without the need for any future activation. Alternatively, Vista can be installed and a dell OEM certificate can be merged into the OS using a native vbscript. It seems we are forced to violate Microsofts own licensing in order to use the software we paid for...
    Tuesday, March 27, 2007 5:40 PM