You do not need a costly rack server to learn VMware. A normal desktop PC can run ESXi very well — but only if three hardware facts are in your favour before you begin. This guide does the checks first and the install second, so you never burn an evening on a machine that was never going to work.
A rack server is the textbook home for ESXi, but the textbook is not the only way to learn. Thousands of good home labs run on ordinary custom PCs — a gaming motherboard, a mid-range CPU, a couple of SSDs. The catch is that ESXi is far pickier than Windows or Linux: it ships only a short list of built-in drivers, and if your network card is not on that list, the installer simply refuses to continue. So this guide starts where the video starts — with the hardware checks — and only then walks through the install itself. Everything is stated honestly: what works, what is acceptable only in a lab, and where the smarter answer is a different hypervisor.
👆 The most famous screen in whitebox ESXi. It does not mean your PC is broken — it means ESXi has no built-in driver for your network card (panel recreated as an illustration, with the installer's real wording).
ESXi includes native drivers only for a fixed set of enterprise-class hardware — Intel server and many Intel desktop NICs, Broadcom NetXtreme adapters and similar. Realtek, the chip on most budget and gaming motherboards, has no native driver at all. Before anything else, find your exact NIC model in Windows Device Manager or on the motherboard's specification page. A supported Intel chip means you are in business. A Realtek chip means you should plan on adding a PCIe Intel NIC (an i210 or i350 class card is the community favourite) — or read the NIC case guide in this series before you decide.
Boot into the BIOS or UEFI setup and enable Intel VT-x (or AMD-V / SVM Mode on a Ryzen board), plus VT-d or IOMMU if you ever want to pass a device through to a VM. The CPU also has to be a 64-bit part, which in practice means anything from roughly the last decade. During installation, some older and some very new CPUs draw a warning that the CPU may not be supported in a future release — that is a note about VMware's support roadmap, not a failure, and the install continues. What is not optional is the virtualisation switch itself: with it off, ESXi installs but virtual machines run crippled or refuse to start.
8 GB of RAM is the practical floor for a useful lab — ESXi itself takes a few GB before your first VM starts — while 16 GB is comfortable and 32 GB is the sweet spot. You also need a boot device, ideally a SATA or NVMe SSD. And you must accept the installer's one big rule: it claims the entire disk it installs onto. Never point it at a disk holding data you want to keep. ESXi writes its own partition layout — a system area called ESX-OSData, and a VMFS datastore when the disk is large enough — and that repartitioning is destructive.
👆 The installer lists every disk it can see, including the USB stick you booted from. Read the model names slowly and pick like you mean it (illustration).
Download the ESXi installer ISO from VMware's official portal. At the time of writing, Broadcom asks for a free support-portal account to reach the downloads, and the terms have already changed more than once — check the licensing page in this series for the current picture before you plan around it. Write the ISO to a USB stick with Rufus, or add it to a Ventoy stick if the same stick serves other installers. Do not write it to the disk you plan to install onto.
After the reboot you land on the DCUI — the plain grey-and-yellow console screen. That unglamorous screen means success. ESXi is a tiny operating system, and this console exists only for basic network setup and rescue work.
👆 The grey-and-yellow DCUI is not a broken install — it is the whole console. Everything else happens from the web interface (address and build are examples, recreated as an illustration).
On the DCUI, press F2, log in as root, and open Configure Management Network. Under Network Adapters, confirm your supported NIC is the selected one. Then set a static IPv4 address on your home or office range, with the subnet mask, gateway and a hostname you will remember. A static address matters: the host's web address should not wander every time the router hands out new DHCP leases. Restart the management network when the console asks.
From any computer on the same network, open https://192.168.1.50 — your own address — and log in as root. The browser will complain about the certificate because ESXi generates its own self-signed one. On your own LAN, for a host you just installed, that warning is expected: verify the address is the one you set, then proceed. You are now in the ESXi Host Client, where VMs, storage and networking are all managed. Create your first VM — or read the honesty note below first.
The video shows the checks and the full install on a real custom PC — every screen, in order, including the BIOS settings.
▶️ Watch Full VideoYes, many home labs do exactly this. Three things decide it: a network card ESXi has a native driver for (Intel is the safe bet, Realtek is not supported), virtualisation extensions enabled in the BIOS, and enough RAM — 16 GB or more makes a comfortable lab. If the NIC fails the test, a PCIe Intel card usually fixes the whole build.
Because ESXi ships only a fixed set of built-in drivers and none of them matches your network chip. The card is not faulty — it works fine in Windows — but ESXi cannot use it, and a hypervisor without networking is useless, so the installer stops instead of installing something broken. The NIC case guide in this series covers the fixes.
The old free ESXi licence was withdrawn after Broadcom took over VMware, and downloads now sit behind a Broadcom account. Fresh installs run in a fully featured evaluation mode for 60 days. The licensing page in this series explains what changed and what your honest options are — and the exact terms keep moving, so check the official portal before relying on any summary, including this one.