VMware Workstation Pro/Player 17.0 | 17 NOV 2022 | Build 20800274 BIOS.440.ROM: build 497 *unchanged since 16.2.0* EFI64.ROM: version VMW71.00V.20648489.B64.2210180824 (64-bit RELEASE) *new* EFI20-64.ROM version: VMW201.00V.20648489.B64.2210180829 (64-bit RELEASE)*new* You can get the latest modded BIOS/EFIs on the first post. * UPDATE * All EFI based VMs created with Workstation 17.0 will use EFI20-64.ROM (TPM support). These VMs cannot specify a (modded) EFI.rom in the .vmx (potential tpm issues?), the feature is disabled, but is is possible to replace C:\Program Files (x86)\VMware\VMware Workstation\x64\EFI120-64.ROM with a modded EFI120-64.ROM for an OEM:SLP solution. If you go this route it's not necessary to modify the .vmx, or to copy the modded EFI20-64.ROM into the virtual machine's folder. Existing EFI VMs can continue to use modded EFI64.ROMs via .vmx entry. Both newly created and existing BIOS VMs can continue to use modded BIOS.440.ROMs via .vmx entry. The download pack has been updated to include the modded EFI20-64.ROM.
Made a mistake, to use a modded EFI in Workstation 17.0 you must specify: efi20-64.filename = "name of modded efi.rom" not efi64.filename = "name of modded efi.rom" then it works.
Depends on the hardware version defined in the vmx file. If you don't upgrade your VM, than it will still use efi64.filename.
OK, to make things more clear, if the vmx entry is virtualHW.version = "20" use efi20-64.filename, otherwise use efi64.filename. Thanks for the input.
I hope I understood you correctly: I renamed your file "WORKSTATION_17.0_DELL_2.6_EFI20-64.ROM" to "EFI20-64.ROM" and replaced it with the original file in C:\Program Files (x86)\VMware\VMware Workstation\x64\ folder. It worked: my Server 2016 (HW-version 17.0) was OEM:SLP activated. After updating to VMware Workstation 17.01, I had of course to repeat the procedure, but before that I noticed that the original file "EFI20-64.ROM" has changed in version 17.01, I don’t know why and in what sense. Nevertheless, after replacing it with your (renamed) file "WORKSTATION_17.0_DELL_2.6_EFI20-64.ROM" the activation works again.
Yes, you understand correctly and you're right, the EFIs been updated for 17.0.1 - thanks for pointing that out. And, as you see, the modded 17.0 EFI64.ROM works in 17.0.1 but it's probably best to update to the new EFI version (see below).
Any idea why I would get error "This host does not provide the ACPI SLIC table required to run this vm" when trying to run VM on a Dell XPS 15, but the same VM runs fine on a Dell Alienware PC? VMWare 16.2.5
My guess is that you're trying to use the host SLIC for guest activation (acpi.passthru) and the Alienware O/S supports OEM:SLP 2.x activation (e.g. Windows 7 - SLP 2.x - host O/S provides a SLIC), but the XPS O/S does not (e.g. Windows 10 - SLP 3.0 - host O/S does not provide a SLIC). In this case comment out the following entries in the XPS guest vmx: acpi.passthru.slic = "TRUE" acpi.passthru.slicvendor = "TRUE" SMBIOS.reflecthost = "TRUE" and set up the XPS guest with a modded rom - place the modded ROM in the VM directory and specify: bios440.filename = "modded_BIOS.440.ROM" or efi64.filename = "modded_EFI64.ROM" in the vmx (the filename must match the modded ROM name). Hope this helps
VMware Workstation Pro/Player 17.0.2 | 25 APR 2023 | Build 21581411 The BIOS and EFIs are not changed for 17.0.2: BIOS build 497 *unchanged* EFI64.ROM version: VMW71.00V.20904234.B64.2212051115 (64-bit RELEASE) *unchanged* EFI20-64.ROM version: VMW201.00V.20904234.B64.2212051119 (64-bit RELEASE) *unchanged* You can get the latest modded BIOS/EFIs on the first post.
ESXi 8.0 Update 1c | 27 JUL 2023 | Build 22088125 BIOS/EFI ROM Version BIOS.440.ROM BIOS Build 497 EFI64.ROM VMW71.00V.20829224.B64.2211211837 (64-bit RELEASE) EFI20-64.ROM VMW201.00V.20829224.B64.2211211842 (64-bit RELEASE) Note: ESXi 8.0 Updates 1 & 1a have the same BIOS/EFIs as ESXi 8.0 Update 1c. Get the latest modded BIOS/EFIs on the first post.
The BIOS.440 mod has many OEMBIOS strings including the 'Compaq Computer Corporation OEMBIOS.CAT CRC32=A5E32571' incorporated . Don't know if that's the one your recovery needs, tho. I think running Compaq recoveries in a VM requires more than just the OEM string anyway, likely locked to specific hardware, so VMware is out. EDIT: FWIW, the SLP OEMBIOS set used by this particular Compaq Quick Restore installation is 'Hewlett-Packard Company OEMBIOS.CAT CRC32=CD4E1902' (HP merged with Compaq in 2002) and it too is supported by the BIOS.440 mod. So, if you get this running in VMware, it will be activated.