VMWare Workstation 16 guest configured as UEFI fails to boot Windows 10 installation media.
I've set up a very simple Workstation 16 guest with the default Windows 10 settings. I've changed the "Firmware settings" (under Options > Advanced) from BIOS to UEFI (without the "secure boot" option set).
When I attach the standard Windows 10 1909 installer ISO (volume license download), the VM refuses to boot from the ISO.
The displays shows that it's trying to boot first from the "VMWare virtual NVME...", then the Network. Both of which, of course fail. If I "Power on to firmware", and use the boot menu to select the "SATA CDRom" device, the screen just refreshes - the VM does nothing else.
If I switch the same guest into BIOS firmware, it boots the device just fine and begins the installation. Unfortunately, I don't want a BIOS guest, I want to handle the install with UEFI configured from the get-go... So running some sort of tool to "convert" from BIOS/MBR to UEFI/GPT isn't an option for me.
This same Windows 10 installer ISO works fine when I use Hyper-V (which defaults to UEFI mode) to build a VM.
What am I missing? I've pasted in a copy of the VMX file for reference.
do you have 2 cd devices connected? maybe it's booting off the wrong iso?
Bryan Woods
ASKER
Seth, you bring up a good point.
I had tried booting a couple of different ISOs with this guest, and had tried setting the CD-ROM as a SCSI device as well (which still didn't boot). Not sure why those config lines are still in the VMX file, but there is only one CD-ROM (SATA) showing in the GUI config: So I can go ahead and create a new Windows 10 guest using the "wizard", set the RAM to 4GB, remove the printer, change Net adapter to "Bridged", firmware type to UEFI... and get the same (failure to boot) results. Here's the VMX file for this new guest:
Actually, I did use the "new virtual machine" wizard. I just opted to "install operating system later", rather than point it to my Windows 10 installer media.
Bryan
Bryan Woods
ASKER
So I definitely appreciate all of the good feedback on this.
As a test, I installed VMWare Workstation 16.1 on my laptop (a 6th generation HP Elitebook with 8th gen Intel i5). When I created a Windows 10 x64 virtual machine, it not only was able to boot the same installer ISO that I had been trying unsuccessfully to boot on my desktop system, it actually defaulted the VM to UEFI firmware (the desktop system was always defaulting to BIOS). This is an older HP desktop with an older i7 2600. There's nothing in the BIOS (the host doesn't support UEFI) that allows me to disable/enable VT-x, but when I run CPU-Z, it shows VT-x capability listed in the "instructions" section:
Regardless, it seems that there's something either lacking in the hardware capability or some feature that's disabled in the BIOS (there's not a lot of options in this thing's antique BIOS). Now that I think about it, I realize that I originally set this box up with Workstation v6. Yikes! Time to upgrade. It's possible that "antiquated hardware" is my biggest problem.
do you have 2 cd devices connected?
maybe it's booting off the wrong iso?