VMware Workstation EFI Network Timeout: Fixes

If your VMware Workstation virtual machine stops at an EFI network timeout message during boot, it usually means the VM is trying to boot from the network (PXE) because it cannot find a bootable operating system on its virtual hard disk. The fix is to either correct the boot order in the VM’s firmware settings or ensure the virtual disk is properly attached and contains a bootable OS.

Why Does the EFI Network Timeout Happen?

When a VM is configured to use EFI (Extensible Firmware Interface) instead of legacy BIOS, it uses the same UEFI boot process as a physical computer. If the VM’s boot order lists the network adapter before the hard disk, or if the hard disk is not recognized as bootable, the firmware attempts to boot from the network using PXE (Preboot Execution Environment). Because no PXE server is available on your network, the VM waits for a DHCP and TFTP response until it times out, then displays an error like “EFI Network: Timeout” or “Start PXE over IPv4”.

How VMware Workstation Handles EFI Boot

VMware Workstation creates a virtual NVRAM file (with a .nvram extension) that stores the VM’s firmware settings, including the boot order. Unlike a physical PC where you can press a key to enter setup during boot, VMware Workstation does not show a splash screen by default. To access the EFI setup menu, you must tell the VM to enter firmware setup from the VMware Workstation menu. The process is simple but not obvious to many users.

Step-by-Step Fixes for the Timeout

1. Enter the EFI Setup Menu

1. Shut down the virtual machine completely (not just suspend).
2. Select the VM in the VMware Workstation library.
3. Click VM > Power > Power On to Firmware.
4. The VM will boot into the EFI setup utility (similar to a PC’s BIOS).

2. Change the Boot Order

1. In the EFI setup, navigate to the Boot menu (or Boot Configuration depending on the firmware version).
2. Use the arrow keys to select the EFI VMware Virtual SCSI Hard Drive (or SATA, depending on your disk type) and move it to the top of the list, above the network adapter.
3. Save changes and exit (usually F10 or via the Exit menu).

3. Check the Virtual Disk Settings

• Ensure the virtual disk is connected: In VM Settings, under Hard Disk, check that Connect at power on is enabled.
• Verify the disk is not accidentally detached or set to a non-existent file.
• If you cloned or moved the VM, confirm the .vmdk file path is correct.

4. If the Hard Disk Is Not Bootable

If the boot order is correct but the VM still times out, the operating system on the disk may be corrupted or missing the EFI boot loader. In that case, you need to boot from an OS installation ISO and repair the boot loader (e.g., using Windows Recovery or a Linux live CD).

Common Variations and Misconceptions

Many users think the timeout indicates a network problem or a VMware bug, but it is almost always a boot order issue. Another misconception is that you need to disable the virtual network adapter entirely. While that would work, it is not necessary and would prevent the VM from accessing the network after boot. Also note that the EFI firmware in VMware Workstation is a custom implementation, so it may look slightly different from the UEFI on a physical PC, but the navigation principles are the same.

Preventing the Timeout in the Future

• Always install the OS with the disk as the first boot device in the EFI setup.
• If you use EFI for a VM, avoid changing the disk controller type (e.g., from SATA to SCSI) after installation, as this can break the boot loader.
• When creating a new VM, choose the firmware type (BIOS vs EFI) based on the OS requirements. Windows 11 requires EFI, but many Linux distributions work fine with BIOS.

Comparing EFI vs BIOS in VMware Workstation

Legacy BIOS is simpler and more forgiving: it scans for bootable devices in a fixed order and does not attempt network boot unless the option is explicitly enabled. EFI is more flexible, supports secure boot and larger disks, but it also introduces the network boot entry by default. For most users, BIOS is the safer choice unless they specifically need EFI features. If you are not sure which one your VM uses, check the VM’s .vmx file for the line firmware = "efi".

Frequently Asked Questions

How do I enter the EFI setup if the VM boots too fast?

You cannot press a key during boot like on a physical PC. Instead, shut down the VM and use VM > Power > Power On to Firmware in VMware Workstation. This forces the VM to enter the setup utility on the next boot.

Can I disable the network boot entry entirely?

Yes, in the EFI setup you can often remove or disable the network boot option. Alternatively, you can set the hard disk as the first boot device, which achieves the same effect without disabling the network adapter.

Why does the timeout take so long?

The firmware waits for a DHCP server to respond to its PXE request. The default timeout is typically 30 to 60 seconds per network interface. If you have multiple virtual network adapters, the wait could be longer.

Will changing the boot order affect my installed OS?

No. The boot order only determines which device the firmware tries to boot from first. As long as your OS is installed correctly on the virtual disk, it will boot normally once the disk is first in the list.

I see “PXE over IPv4” and “PXE over IPv6” messages—what’s the difference?

These are just two network protocols the firmware tries. IPv4 is the standard, and IPv6 is the newer protocol. Both will time out if no PXE server is present. The fix is the same: put the hard disk first in boot order.

Is it safe to convert a BIOS VM to EFI?

No, VMware Workstation does not provide a supported way to convert a VM from BIOS to EFI without reinstalling the OS. If you need EFI, create a new VM with EFI firmware and install the OS fresh.

Related

• 5G Business Impact: 7 Ways It Changes Work
• Best Multiplayer Games for Chromecast
• Keep Me Signed In: What It Means & How It Works