VMware Workstation/ESXi BIOS/EFI SLIC Mod

Discussion in 'Virtualization' started by pantagruel, Aug 26, 2015.

  1. pantagruel

    pantagruel MDL Addicted

    Aug 30, 2007
    523
    1,915
    30
    Name: VMware Workstation 12.5.9 Pro/Player for Windows.
    Release Date: 2018-01-10
    Build Number: 7535481

    New EFIs, the BIOS is the same as previous 12.x versions.

    BIOS BUILD 429
    EFI ROM version: VMW71.00V.0.B64.1706210604 (64-bit RELEASE)
    EFI ROM version: VMW71.00V.0.B32.1706210604 (32-bit RELEASE)

    I created a new package which includes the modded BIOS, EFIs, and the 12.5.9 vmware-vmx modded with all three. A how-to-use guide is also included.

    Added to the first post.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. amir123

    amir123 MDL Novice

    Sep 5, 2015
    11
    2
    0
  3. alkado

    alkado MDL Novice

    Jan 15, 2017
    8
    11
    0
    #103 alkado, Mar 4, 2018
    Last edited: Mar 4, 2018
    Question regarding manually modification for bios440, as far as i understand it can be done by following steps:
    1. Get Tool to Insert/Replace SLIC in Phoenix / Insyde / Dell / EFI BIOSes (phoenixtool273.zip)
    2. Get RW Everything (RwPortableX64V1.7.zip)
    3. Get original bios440:
    Using 7zip open C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe
    then extract ".rsrc\1042\BINRES\6006" file - that's bios440​
    4. Get RW Everything reports (are this step needed?)
    Open rw.exe,
    then goes to Access -> ACPI Tables,
    than press "Ctrl + F2" - to save All to AcpiTbls file​
    5. Open PhoenixTool
    Original Bios - Load original Bios (i.e. 6006 file)
    Manufacturer - What i must select in manufacturer field????
    SLIC File - for SLIC 2.1 which one are good choice? (DELL[QA09]2.1-853747C5.BIN)
    Select RW file - AcpiTbls.rw (are this step needed?)
    Method - SSV2​

    P.S.
    As far as i can see:
    AcpiTbls.rw are diffrent between each VM resided on same VMware Workstation host...
    i.e. i'm have 4 windows VM, dump AcpiTbls, and obtain 4 different AcpiTbls.rw files...
     
  4. pantagruel

    pantagruel MDL Addicted

    Aug 30, 2007
    523
    1,915
    30
    You can do the mod without the AcpiTbls. From Andy's readme.pdf:

    Advanced Mode
    To enable advanced mode create a file called PhoenixTool.ini in the tool directory. It can be blank
    ** This enables some modification methods that are potentially not safe, USE AT YOUR OWN RISK **
    It also allows all mods (except some Dell) to occur without a RW report.

    I don't think you can do any damage with a virtual bios.

    For the rest, you can use any 2.1 SLIC as long as you have the corresponding certificate, and select 'other' for manufacturer. You should be OK.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. alkado

    alkado MDL Novice

    Jan 15, 2017
    8
    11
    0
    #105 alkado, Mar 4, 2018
    Last edited: Mar 4, 2018
    @pantagruel - Thank you for explanation
    @mxman2k - Thank you for explanation too (in different thread, and already deleted)
    I'm created bois using AcpiTbls.rw from different VM...
    Then created bios without AcpiTbls.rw at all (by creating PhoenixTool.ini)...
    All produced bios file are identical!!!
     
  6. joat786

    joat786 MDL Novice

    Mar 13, 2018
    1
    0
    0
    #106 joat786, Mar 13, 2018
    Last edited: Mar 27, 2018
    I replaced the BIOS.440.ROM, EFI32.ROM and EFI64.ROM from 1st post, and all Windows VMs activated with cert and slmgr.
     
  7. JeanYuhs

    JeanYuhs MDL Member

    Feb 16, 2010
    196
    127
    10
    If one uses this VMware 14/14.1 BIOS/EFI for Windows 10 and gets the "The activation server determined the specified product key is blocked." error means it's pretty much dead in the water, correct? Attempting to get Windows 10 Professional with the Dell BIOS/EFI working for some testing, and yes it's the April Update build 1803 as of earlier today.

    Just curious, thanks for any assistance.
     
  8. pantagruel

    pantagruel MDL Addicted

    Aug 30, 2007
    523
    1,915
    30
    It isn't possible to activate Windows 10 with a BIOS/EFI SLP mod. Have a look at the KMS solutions.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. JeanYuhs

    JeanYuhs MDL Member

    Feb 16, 2010
    196
    127
    10
    *facepalm* Yeah, I should have known that one, hence the LTSB thing being so popular, my bad, my bad, thanks for the reminder. :)
     
  10. pantagruel

    pantagruel MDL Addicted

    Aug 30, 2007
    523
    1,915
    30
    Name: VMware Workstation 14.1.2 Pro/Player for Windows
    Release Date: 2018-05-21
    Build Number: 8497320

    The BIOS/EFIs are the same as 14.1.0

    BIOS BUILD 464
    EFI ROM version: VMW71.00V.6997262.B64.1710270607 (64-bit RELEASE)
    EFI ROM version: VMW71.00V.6997262.B32.1710270607 (32-bit RELEASE)

    The modded BIOS/EFIs can be found on the first post.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. ivandurak

    ivandurak MDL Novice

    Mar 10, 2017
    11
    0
    0
    Hello, all

    Please help me

    Need a modded BIOS for old VMWare Workstation - 7.1.6 build-744570 (guest OS will be Windows 7 32-bit)

    Not sure, BIOS build 3.14 or 3.15 I needed

    Searching in old threads, ROM Mega Packs and Collections - all links are dead :(

    Also, can't extract original bios440 from vmware-vmx.exe with 7-zip

    Thanks!
     
  12. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,773
    19,323
    180
    #112 mxman2k, Jun 9, 2018
    Last edited: Jun 9, 2018
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. ivandurak

    ivandurak MDL Novice

    Mar 10, 2017
    11
    0
    0
    Thank you!

    I didn't know about this option

    Will try now
     
  14. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,773
    19,323
    180
    I use the acpi.table line when testing the MRP project for different slic testing so i know it works.

    I think you have to have the bios440.filename with the vm's bios to allow the other acpi.table option to work, i always add both to make sure. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,773
    19,323
    180
    #115 mxman2k, Jun 9, 2018
    Last edited: Jun 9, 2018
    I am not sure if it is a documented 'feature' or a hidden one, but it does save messing about editing the bios and risk having the VM screw up.

    I mention to not have spaces in the filenames as it can cause VMware to get funny and crash out with exceptions etc.

    Place the two (VMBios.Rom and your SLIC bin) files in the same folder/area as the main VM's HDD image and the .vmx config file is stored. This saves having paths that can cause other strange problems if any spaces are in them.

    using the acpi.table way you can have as many different SLIC's as you wish, but only one can be used at any one time. I just name the Slic's like Acer21.bin, Dell24.bin etc that way you can tell what slic brand and the type 2.1 or 2.4 as in the example.

    **edit**
    Just realized you are using VMware v7.x i know the acpi.table bit works on v12 and above which i have and the VMplayer too.

    But you now have a extract bios rom that can be edited with the Phoenix Tool if need be, if the acpi.table line not work on that older VMware version.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. briseis

    briseis MDL Novice

    Nov 30, 2009
    14
    0
    0
    (Again,) I would love to have a bios440 (6006.rom) for vmware 14.1 modded with the Asus slic. The toolkit just shows how to mod the EFI version. So could someone (Pantagruel?) please mod the 6006.rom?
     
  17. pantagruel

    pantagruel MDL Addicted

    Aug 30, 2007
    523
    1,915
    30
    #118 pantagruel, Jul 22, 2018
    Last edited: Aug 31, 2018
    (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. briseis

    briseis MDL Novice

    Nov 30, 2009
    14
    0
    0
    @pantagruel

    I'm trying to comprehend how you modified the 6006.rom, given the discussion you had with alkado, so that I can modify the bios by myself next time.
    I have understood that one doesn't need to build ACPI tables with RW Everything.

    So what I would try is to

    1. Extract 6006.rom from vmware-vmx.exe with a ressource editor
    2. Load it into Andy's tool which I have put into 'advanced' mode.
    3. Load the Asus SLIC provided with Andy's tool and choose 'other' as vendor tag
    4. ??? Any additional steps???
    5. Run Andy's tool

    How did you actually modify the bios?
     
  19. pantagruel

    pantagruel MDL Addicted

    Aug 30, 2007
    523
    1,915
    30
    @briseis

    As of VMware 14 it's not necessary or even possible to extract BIOS.440.ROM from vmware-vmx.exe. You can find BIOS.440.ROM in the same directory as vmware-vmx.exe:

    C:\Program Files (x86)\VMware\VMware Workstation\x64\BIOS.440.ROM

    If you don't want to use a RWEverything report you'll need to create an empty file called PhoenixTool.ini and add it to the PhoenixTool directory. This will allow you to proceed without the AcpiTbls.rw report.

    To mod the BIOS with a SLIC:

    1. load BIOS.440.ROM into PhoenixTool
    2. select 'other' as Manufacturer
    3. load SLIC file (ASUS.BIN in Andy's Tool)
    4. skip the RW file
    5. optional - verify certificate (_ASUS_-E1948081.XRM-MS)
    6. Method - select SSV2
    7. press 'GO' - no need to use 'Advanced' options
    8. the modded BIOS will be named 'BIOS.440_SLIC.ROM'

    That's it.

    Tip: Create a new working folder and place a copy of unmodded BIOS.440.ROM, the certificate, and a copy of the entire PhoenixTool folder in it. It keeps things organized and easy to work with.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...