Custom Windows ISO Installs Fine in a Virtual Machine but Fails on a Real PC
The VM said the ISO was perfect. The customer's PC disagrees — no disk in Setup, a boot failure, or an install that dies halfway. Virtual hardware is forgiving in ways real hardware is not, and each difference has a test.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 8 minute read
🎥 Watch the complete video — building a custom Windows ISO, removing unwanted components and setting the bypass options step by step
A virtual machine is a liar by kindness: it presents standard storage controllers with inbox drivers, a simple firmware, and hardware that never surprises Setup. A real PC brings Intel VMD storage, vendor RAID modes, Secure Boot policies, quirky USB controllers and OEM software expectations. When a custom ISO passes the VM and fails on metal, do not rebuild randomly — split the problem. Work through the differences below in order; the failure almost always lives in one of them.
Windows Setup — Select the driver to install / no drives found
No drives were found. Click Load driver to provide a mass storage driver for installation.
Where do you want to install Windows? — the list is empty
Cause in most real-PC cases: Setup (boot.wim) has no driver for this storage controller
The classic VM-pass real-fail symptom. The VM used a standard controller; the real PC is in VMD or RAID mode.
1
Difference 1 — Storage the Setup Environment Cannot See
Symptom: Setup boots, then shows an empty disk list or a "load driver" demand
Cause: modern laptops ship with Intel VMD or RAID mode enabled; the driver lives in neither boot.wim nor the VM's world
Fix properly: integrate the storage driver into boot.wim index 2 and install.wim (the DISM page in this series shows how), or load it from USB during Setup as a one-off
Switching the BIOS from RAID/VMD to AHCI also works, but know it changes how an existing Windows install on that machine boots — on a fresh install it is safe, mid-repair it can strand the old system
2
Difference 2 — Firmware and Media Realities
Secure Boot: a customised or rebuilt boot image that lost its proper signing is rejected by real firmware while the VM's permissive firmware waved it through. Keep boot files from the genuine image untouched where possible
FAT32 4 GB limit: if the ISO was written to a FAT32 stick, an install.wim over 4 GB must be split into .swm parts — a missing or wrong split shows up as a corrupt or missing image error only on the real install
USB port and stick quality: try a USB 2.0 port and a known-good stick before blaming the image; marginal sticks pass VM tests because VMs do not boot from them at all
3
Difference 3 — Your Own Customisations, Meeting Real Hardware
Removed component, needed here: something you removed is required by this machine's OEM utilities, touchpad stack, or the customer's printer and scanner software — read C:\Windows\Panther\setupact.log on the failed machine; Setup writes its reasoning there
Answer file disk instructions: a file written for the VM's single small disk can target the wrong disk or layout on a two-drive PC — one more reason disk sections get tested with paranoia
Driver conflicts: an integrated driver that is older than the one Windows Update would choose can misbehave on real hardware while the VM's virtual devices never load it
4
The Split-Test Order ⭐
Boot the untouched Microsoft ISO on the same PC: if it also fails, the problem is the machine or the stick, not your build
Boot your ISO with the answer file removed: if it now installs, the file was the fault
Install your ISO on a different real PC: if it works there, the first machine's storage mode or firmware is the fault
Only after those three splits, open the logs and rebuild — each test halves the suspect list, and rebuilding before splitting just shuffles the unknowns
The lesson to keep: VM testing proves the image is coherent. Only metal proves it is compatible.
🎥 Watch the Complete Video Guide
Every checkbox, removal and bypass option from this page is shown live in the full video — watch it end to end before you build your own ISO.
Why does the VM never show the missing disk problem?
Because virtual hardware uses standard controllers that Windows has shipped drivers for since forever. The missing-disk failure needs a controller Setup has never heard of — Intel VMD, a RAID mode, or an unusual chipset — and those only exist on real machines.
Setup fails at a percentage with a corrupt file error on the real PC only. What now?
Suspect the media first: an install.wim over 4 GB copied to FAT32 without splitting, or a tired USB stick. Recreate the stick with the split image or a better tool, verify the ISO hash, and retest before touching the image itself.
How do I read the setup log from a failed install?
Boot any Windows setup media, open a command prompt with Shift+F10, and read C:\Windows\Panther\setupact.log on the target disk (drive letters shift in the setup environment — check with diskpart's list volume). The final entries name the failing component or driver.
This guide is based on the Technical Anshu video on building your own Windows ISO and removing unwanted components • Stuck on a step? Ask in the video comments — you will get help 🙏