Empty disk list, install stopped. This is the most common ESXi Windows problem there is, it has nothing to do with your disk, and the fix takes two minutes once you know where VMware hides the driver.
You created the VM, the ISO booted, and then Setup asks Where do you want to install Windows? over an empty list. Before you delete anything or re-download the ISO, read this: your disk is not missing - its controller's driver is. Here is the two-minute fix, plus the honest alternative route and why this screen exists at all.
Your virtual disk is fine and ESXi can see it. The problem sits one layer lower: the disk is attached to a VMware Paravirtual (PVSCSI) controller, and the Windows installation media ships with no driver for that controller. Setup can only list disks whose controller it can talk to, so the list comes up empty with the message We couldn't find any drives. This is the documented, expected behaviour for modern Windows guests on ESXi - not corruption, not a bad ISO, not a broken host.
Every ESXi host carries the driver as a floppy image. Power the VM off or edit it live, and add the device:
/vmimages/floppies/pvscsi-Windows2008.flp from the hostIf the driver entry does not appear, untick Hide drivers that are not compatible with hardware on this computer and browse again - and double-check the floppy shows as connected in the VM settings. Nine out of ten failures here are simply an unconnected floppy.
If you would rather not touch floppies: rebuild or edit the VM with the SCSI controller set to LSI Logic SAS. Windows carries that driver in-box, so Setup sees the disk immediately. Install Windows, install VMware Tools, shut the VM down, then change the controller to VMware Paravirtual and boot. Windows keeps working because Tools already installed the PVSCSI driver. This route takes longer and earns you nothing extra on a fresh build - it is a fallback, not the better method. What you should not do is stay on LSI Logic forever out of habit: PVSCSI has lower CPU overhead and higher throughput, which is why ESXi defaults to it.
Every click shown live - creating the VM, loading the driver and installing VMware Tools.
Watch Full VideoIt ships with the host as a floppy image at /vmimages/floppies/pvscsi-Windows2008.flp. Add a floppy drive to the VM, connect that image, and in Windows Setup use Load driver to select the VMware PVSCSI Controller.
Check that the floppy is ticked Connected in the VM settings, and in Setup untick the option that hides incompatible drivers, then browse the floppy again. Also confirm the VM actually has a virtual disk attached and that it sits on the PVSCSI controller.
Yes. Windows includes the LSI Logic SAS driver, so Setup sees the disk without extra steps. The trade-off is performance: PVSCSI is faster with less host CPU. The clean pattern is install with whichever you like, install VMware Tools, then switch the controller to PVSCSI.