When installing Windows Server 2012 R2 on a VM (vSphere or Hyper-V) configured for EFI you may receive the following error when booting to the ISO. “Windows failed to start. A recent hardware or software change might be the cause. To fix the problem… File: \EFI\Microsoft\Boot\BCD. Status: 0xc000014c. Info: The boot Configuration Data for your PC is missing or contains errors.”
When loading the VMware Paravirtual SCSI driver you receive an error that says, “No new devices drivers were found. Make sure the installation media contains the correct drivers, and then click OK.”
The installation cannot load any SCSI driver & says, “A media driver your computer needs is missing.”
“No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.”
Cause – Corrupted ISO
Solution – Re-download the ISO & try again. In my experience ISOs can become corrupt if you pause them when downloading.
Windows 8.1 Pro with the Hyper-V Role installed. One physical NIC with a static IP address.
Configure an External Virtual Switch bound to the physical adapter.
Virtual machines can get to the Internet just fine but the Hyper-V server cannot.
Hyper-V server can’t even ping Bing.
Hmmmm…can’t even resolve bing.com. Looking at the IPv4 properties of the vEthernet (External) NIC there is no DNS configured.
Add the IP of the router (or whatever DNS server you use) back in for the DNS server(s). Now the Hyper-V server can access the Internet.
When creating the External Virtual Switch a dialog box popped up that said, “Pending changes may disrupt network connectivity. This computer may loose blah, blah, blah”. But then it says, “These changes also may overwrite some static changes. If that happens, you must reapply the static changes to restore network connectivity.”
So there you go. When configuring Hyper-V to use a NIC that has a static IP configured you may loose some or all of it when it moves those settings to the vEthernet NIC.