How to Download and Install VMware ESXi
Learn how to download VMware ESXi, prepare bootable USB or optical media, install it on a physical server, configure firmware, and verify first-boot management access.
ESXi installation overview
VMware ESXi is a bare-metal hypervisor. It runs directly on physical server hardware instead of running inside Windows, Linux, or another desktop operating system. A hypervisor abstracts CPU, memory, storage, and networking so multiple virtual machines can share one physical host.
A typical installation follows this sequence:
- Obtain the correct ESXi ISO installer from the authorized vendor portal.
- Verify the download and create bootable USB or optical media.
- Check hardware compatibility and prepare the server.
- Configure BIOS or UEFI boot settings.
- Boot the server from the installation media.
- Run the interactive installer and select the ESXi destination disk.
- Reboot from the newly installed ESXi boot device.
- Record or configure the management IP address and verify browser access.
Licensing, access, and downloading the installer
Evaluation licensing and download availability depend on current VMware and Broadcom portal policies. Product versions, registration requirements, and available license options can change. Use the authorized vendor portal and review the licensing terms that apply to your account and intended deployment.
- Sign in to the vendor portal, or register an account if the portal requires one.
- Locate the ESXi download section.
- Select the release intended for your hardware and environment.
- Download the ESXi ISO image. An ISO image is a disk-image file used to create bootable installation media.
- When the vendor provides a checksum or digital signature, validate the downloaded file before writing it to media.
A checksum mismatch can indicate an incomplete, damaged, or altered download. Do not use an image that fails the vendor's published verification.
Planning and hardware readiness
Before installing, confirm that the server and its components are supported by the selected ESXi release. Hardware compatibility means that the server model, drivers, and components are supported together for that release.
Review the hardware compatibility documentation for the exact ESXi release. Server manufacturers may also provide a vendor custom image, which is an ESXi installer containing platform-specific drivers and components. Use such an image when the hardware vendor recommends it.
Update the server BIOS or UEFI, storage-controller firmware, and network firmware when required by the hardware vendor. Do not update firmware casually on a production server; follow the vendor's maintenance and recovery procedure.
Decide which device will contain ESXi before starting. Do not select a disk intended for a VM datastore, which is storage used for virtual machine files, or a disk containing a valuable operating system.
Create ESXi installation media
Bootable media is a CD/DVD or USB device prepared to start the server and launch the installer. Simply copying an ISO file onto a USB drive is not sufficient. The ISO must be written to the device with an ISO-writing utility so the required boot structure is created.
Example: optical installation media
- Download the authorized ESXi ISO.
- Verify its checksum or signature when available.
- Write the ISO to a blank optical disc using a disc-image writing function, not ordinary file copying.
- Insert the disc into the server's optical drive.
- Configure the optical drive as the temporary or first boot device.
- Boot the server and follow the interactive installer.
Example: USB installation media
- Use a blank or disposable USB drive with enough capacity for the ISO-writing utility.
- Open the utility and select the verified ESXi ISO.
- Select the correct removable drive and write the image.
- Safely eject the drive after the operation completes.
- Insert it into the server and use the one-time boot menu to start from USB.
- During installation, select the intended internal disk as the ESXi destination. Do not select the USB installer unless that is specifically supported and intended for the deployment.
Configure BIOS or UEFI boot settings
BIOS is legacy motherboard firmware that initializes hardware and controls startup settings. UEFI is modern firmware that replaces or supplements legacy BIOS boot functionality. The boot order is the priority sequence of devices checked during startup.
- Restart the server and press the firmware setup key shown during startup. The key varies by server or motherboard vendor.
- Alternatively, open the one-time boot menu and select the installation device without permanently changing the boot order.
- Set the CD/DVD drive or USB device as the temporary boot target or highest-priority boot device.
- Use a firmware mode compatible with the prepared media. Do not prepare media for one mode and select an incompatible mode without checking the server and ESXi requirements.
- Save the firmware changes and reboot.
If the server boots from its existing disk instead of the installer, use the one-time boot menu first. If the installer device is absent, recheck the media, port, firmware mode, and boot configuration.
Interactive ESXi installer workflow
After the server starts from the media, the ESXi installer loads files and initializes the installation environment. This loading stage may display diagnostic text before the main installer screens appear. Wait for the welcome screen.
Selecting the correct disk
When multiple disks are displayed, compare capacity, model name, controller location, and existing contents. A dedicated boot disk is normally preferable to a disk reserved for VM datastores.
Pause when two or more disks have similar sizes. If possible, disconnect nonessential disks or label the dedicated boot device before installation. Never assume that the first disk listed is the correct target.
Setting the root password
The root account is the built-in ESXi administrative account with full host privileges. Use a unique, long password that is not reused elsewhere. Store it in an approved credential-management system and restrict knowledge of it to authorized administrators.
First-boot verification
After installation and reboot, ESXi displays the Direct Console User Interface, commonly called the DCUI. The DCUI is the local console used for basic host status and management configuration.
- Confirm that the server booted from the intended ESXi device rather than the installer media or another disk.
- Check that the expected physical network adapter is detected and has an active link.
- Record the displayed management network status and IP address if one was obtained through DHCP.
- If no usable address is available, open the DCUI network configuration and set the required values.
- From an authorized management workstation, open the ESXi Host Client using the HTTPS management address displayed by the host.
The Host Client is the browser-based management interface for a standalone ESXi host. Browser access requires functioning management networking and an HTTPS connection. A certificate warning may appear when the host uses a newly generated or locally trusted certificate; follow your organization's certificate policy rather than ignoring security warnings blindly.
Basic management network configuration
The management network is the network path used to administer the ESXi host. DHCP may provide an address automatically, but many managed environments use a static configuration.
Through the DCUI, configure the following as required:
- A static IPv4 or IPv6 address.
- The subnet mask or IPv6 prefix.
- The default gateway.
- DNS servers.
- The hostname and DNS domain.
- The management VLAN, if the switch design requires one.
After changing network settings, test access from a workstation on the authorized management network. Confirm the switch port, cable, VLAN, gateway, routing, and firewall rules if access fails.
Post-installation security and operations
- Use a unique strong root password and protect it in an approved credential-management system.
- Restrict ESXi management access to trusted administration networks; do not expose the management interface directly to untrusted networks.
- Configure DNS, the default gateway, NTP, and certificates according to the environment.
- Document the ESXi version, installation disk, management IP address, hostname, server model, storage controller, and network adapters.
- Plan a patching and upgrade process that accounts for hardware compatibility and maintenance windows.
- Back up the host configuration using an approved operational process.
- Plan lifecycle management for firmware, drivers, ESXi releases, and eventual hardware replacement.
For standalone host administration, continue with basic ESXi configuration and learn about the VMware ESXi online course. If the host will be centrally managed, review how to add an ESXi host to vCenter Server inventory.
Troubleshooting installation problems
The server does not boot into the ESXi installer
Likely causes include an incorrect boot order, media that was not created as bootable, a UEFI and legacy BIOS mismatch, a damaged ISO, or faulty removable media.
- Use the one-time boot menu and select the installer device directly.
- Recreate the media from a verified ISO using an ISO-writing utility.
- Try the firmware boot mode appropriate for the prepared media and supported by the server.
- Test another USB port, USB drive, optical disc, or optical drive.
The installer cannot see the intended local disk
The storage controller or its driver may be unsupported. The controller may also be configured in an unsuitable mode, have outdated firmware, or require the vendor's custom image.
- Check compatibility for the exact ESXi release and storage controller.
- Review the server's storage-controller settings according to the hardware vendor's guidance.
- Update supported controller firmware during an approved maintenance window.
- Try the hardware vendor's custom ESXi image when applicable.
The installer reports unsupported hardware or no compatible network adapter
The NIC or platform may not be supported by the chosen release, or the required driver may be absent from a generic ISO.
- Consult the compatibility information for the server and adapter.
- Use a supported network adapter or vendor-customized installer when appropriate.
- Choose an ESXi release supported by the platform.
The host boots but cannot be managed over the network
Check for an inactive physical link, a missing management address, incorrect VLAN, gateway, DNS, or subnet settings, and firewall or routing restrictions.
- Use the DCUI to verify the management NIC and configure the management network.
- Confirm the switch port, VLAN, cable, and upstream network connectivity.
- Test from a workstation connected to an authorized management network.
- Verify that the HTTPS address and hostname resolve as expected.
The wrong disk was selected
Multiple disks that looked similar may have been present, or existing data disks may not have been removed before installation.
- Stop further writes where possible.
- Assess available backups and recovery options before attempting changes.
- For future installations, disconnect nonessential disks or clearly label the dedicated boot device.
Installation validation checklist
Exam-relevant notes
- ESXi is a bare-metal hypervisor; it is installed directly on physical server hardware.
- An ISO image is not bootable on a USB drive merely because the file was copied there; the image must be written with an appropriate utility.
- The destination disk selection is destructive and must be verified carefully.
- BIOS and UEFI are firmware modes, while boot order controls which device starts first.
- The DCUI provides local access for basic status and management network configuration.
- The Host Client provides browser-based administration after management networking is functional.
- A supported network adapter, storage controller, firmware combination, and ESXi release are essential for a reliable installation.