Info2soft use cookies to help you have a superior and more admissible browsing experience on our website. Privacy Policy
When configuring a Hyper-V virtual machine, you may need to add a new boot device, attach an ISO image, or change the startup order to load an operating system from a specific source. However, the available boot options are not exactly the same for every virtual machine.
Hyper-V uses two VM generations, Generation 1 and Generation 2, and each has different firmware and device requirements. Understanding these differences before changing the configuration can save time and help avoid boot errors.
In this guide, I’ll walk you through how to add boot devices in Hyper-V, configure the boot order using Hyper-V Manager and PowerShell, and troubleshoot common startup problems.
A boot device is a virtual or physical storage or network source that a virtual machine uses to load an operating system or start an installation process.
Depending on the VM generation and configuration, Hyper-V supports several boot options:
| Boot Device | Purpose |
|---|---|
| Virtual Hard Disk | Loads an installed operating system from a VHD or VHDX file |
| DVD Drive | Boots from an ISO image or supported installation media |
| Network Adapter | Starts the VM through a network boot (PXE) |
| Floppy Disk | Boots from a virtual floppy image (Generation 1 only) |
Before adding a device, it’s important to check which generation your virtual machine uses.
Hyper-V Generation 1 and Generation 2 virtual machines use different firmware architectures. Generation 1 uses legacy BIOS, while Generation 2 uses UEFI.
This affects which devices can be used for booting.
| Feature | Generation 1 | Generation 2 |
|---|---|---|
| Firmware | Legacy BIOS | UEFI |
| Virtual Hard Disk Boot | IDE | SCSI |
| DVD Boot | IDE DVD Drive | SCSI DVD Drive |
| Network Boot | Legacy Network Adapter | Standard Network Adapter |
| Secure Boot | Not supported | Supported |
| Virtual Floppy Boot | Supported | Not supported |
For most modern operating systems, Generation 2 is the recommended choice. However, if you’re working with an older operating system or an existing virtual disk that requires legacy BIOS, Generation 1 may be necessary.
Before changing the boot order, you need to make sure the required device is actually attached to the virtual machine.
For this example, I’ll use a DVD drive and a virtual hard drive, as these are two of the most common devices administrators need to add.
A virtual DVD drive allows you to mount an ISO image and boot a VM from installation or recovery media.
Follow these steps:
Open Hyper-V Manager on your host machine.
Select the virtual machine you want to configure.
Right-click the VM and select Settings.
Under Add Hardware, select the appropriate controller and add a DVD Drive. For a Generation 2 VM, use the SCSI controller. For Generation 1, use the IDE controller.
Select the newly added DVD Drive.
Under Media, choose Image file (.iso).
Browse to the ISO file you want to use.
Click Apply, then OK.
The ISO image is now attached to the virtual DVD drive.
If you’re using a Generation 2 VM, you can attach an ISO image to a SCSI DVD drive. You don’t need to add an IDE controller, because Generation 2 VMs don’t use IDE controllers.
If you want to connect an additional VHD or VHDX file to a virtual machine, you can add it through the VM settings.
Here’s how:
Open Hyper-V Manager.
Right-click the target VM and select Settings.
Select SCSI Controller for a Generation 2 VM, or an available supported controller for your Generation 1 configuration.
Click Hard Drive, then select Add.
Choose Virtual hard disk and browse to the existing VHD or VHDX file.
Click Apply and OK.
The virtual hard drive will now appear in the VM’s hardware configuration.
Keep in mind that attaching a virtual hard disk doesn’t automatically make it bootable. If you want to start the VM from this disk, it must contain a compatible bootable operating system and be supported by the VM’s generation.
Once the required devices are attached, the next step is to configure the boot order.
For example, if you’re installing Windows from an ISO image, you may want the VM to check the DVD drive before the existing virtual hard disk.
There are two ways to do this.
This is the easiest method if you only need to adjust the startup order of one virtual machine.
For Generation 2 VMs:
Open Hyper-V Manager.
Right-click the target VM and select Settings.
Select Firmware from the left-hand panel.
Under Boot Order, select the device you want to prioritize.
Use Move Up or Move Down to change its position.
Move the DVD Drive to the top if you want to boot from an ISO image.
Click Apply and OK.
For Generation 1 VMs:
The process is similar, but you’ll need to select BIOS instead of Firmware.
Under Startup Order, move the desired device to the top of the list and save the changes.
The first device in the list is checked first during startup. If it doesn’t contain a usable boot environment, the VM can continue to the next available device.
If you manage multiple Hyper-V virtual machines or prefer command-line administration, PowerShell provides a more direct way to configure boot devices.
First, open PowerShell as an administrator on the Hyper-V host.
For Generation 2 VMs
Use Get-VMFirmware to inspect the current firmware configuration:
Get-VMFirmware -VMName "TestVM"
To set an attached DVD drive as the first boot device, run:
$dvd = Get-VMDvdDrive -VMName "TestVM"
Set-VMFirmware -VMName "TestVM" -FirstBootDevice $dvd
This sets the DVD drive as the first boot device without replacing the entire boot order.
If you want to define a complete boot order, you can use -BootOrder:
$dvd = Get-VMDvdDrive -VMName "TestVM"
$disk = Get-VMHardDiskDrive -VMName "TestVM"
$network = Get-VMNetworkAdapter -VMName "TestVM"
Set-VMFirmware -VMName "TestVM" -BootOrder $dvd, $disk, $network
The -BootOrder parameter replaces the existing boot order. Any boot entries not included in the command will be removed. Check your current configuration before running it.
For Generation 1 VMs
Generation 1 uses BIOS rather than UEFI, so you’ll need Set-VMBios instead:
Set-VMBios -VMName "TestVM" -StartupOrder @("CD", "IDE", "LegacyNetworkAdapter")
This example configures the VM to check the CD drive first, followed by the IDE hard drive and the legacy network adapter.
The commands are not interchangeable: Set-VMFirmware is for Generation 2, while Set-VMBios is for Generation 1.
Adding a device is only part of the process. You also need to make sure the virtual machine can actually boot from the selected media.
Booting from an ISO image is commonly required when installing a new operating system, repairing an existing installation, or running recovery tools.
Here’s the process I recommend:
Make sure the VM has a virtual DVD drive.
Open the VM’s Settings and attach the required ISO image.
Open Firmware (Generation 2) or BIOS (Generation 1).
Move the DVD drive to the top of the boot order.
Apply the changes and start the VM.
If prompted, press a key to boot from the installation media.
The VM should now load the installation or recovery environment from the ISO image.
If it continues to boot from the virtual hard disk, double-check that the ISO is bootable and that the DVD drive is correctly configured.
This is a slightly different situation.
Unlike a physical computer, Hyper-V does not provide native USB passthrough that allows a VM to directly use a host-connected USB device in the same way as a physical machine.
Enhanced Session Mode can redirect supported USB devices into a guest operating system, but this is not the same as making a USB device available to the VM’s firmware during startup.
If your goal is to install an operating system from a USB-created installation drive, I recommend using the installation image to create or obtain a bootable ISO file and attaching that ISO to a virtual DVD drive.
If you need access to data on a physical disk, Hyper-V also supports attaching certain offline physical disks to a VM through a pass-through configuration. However, this should not be confused with standard USB boot support.
Even after adding a boot device and changing the startup order, a virtual machine may still fail to boot. In my experience, it’s best to check the device configuration first rather than immediately changing multiple firmware settings.
Here are some common issues worth checking.
The VM may still be trying to boot from its original hard drive instead of the newly added device.
Open Firmware or BIOS settings and confirm that the intended device is at the top of the list.
An ISO file isn’t necessarily bootable just because it can be mounted.
Make sure you’re using a valid bootable image and that the file isn’t corrupted or incomplete. If possible, test the image in another environment.
A virtual machine may fail to boot if its generation doesn’t match the boot method or operating system requirements.
For example, Generation 1 uses BIOS and IDE-based boot devices, while Generation 2 uses UEFI and supports booting from SCSI virtual disks and DVD drives.
Check the VM generation before troubleshooting other settings.
If you’re using a Generation 2 VM, Secure Boot may prevent an unsupported or incorrectly signed bootloader from starting.
Open Settings > Security and review the Secure Boot configuration.
For supported Linux distributions, you may need to select the appropriate UEFI CA template. If the installation media doesn’t support Secure Boot, you can temporarily disable it to test whether Secure Boot is causing the issue.
I recommend re-enabling Secure Boot when the guest operating system supports it.
Make sure the boot device is connected to a controller supported by the VM generation.
For example, Generation 2 supports booting from SCSI virtual hard disks and DVD drives, whereas Generation 1 uses IDE for its standard disk and DVD boot devices.
A controller mismatch can prevent the VM from recognizing the intended boot source.
Configuring boot devices is just one part of managing a Hyper-V environment. As infrastructure requirements change, you may also need to move virtual machines to another host or virtualization platform.
For these scenarios, i2Migration provides a solution for migrating virtual machines across different environments, helping IT teams simplify migration projects while minimizing business disruption.
Evaluate Your
Migration Options
Explore migration options for servers, virtual machines, databases, and data across different IT environments.
If you’re planning to move your Hyper-V workloads, you can learn more about i2Migration and its virtual machine migration capabilities.
Can I add a boot device to a running Hyper-V VM?
Some virtual devices, including supported SCSI devices on Generation 2 VMs, can be added while the VM is running. However, if you’re changing boot-related hardware or firmware settings, I recommend shutting down the VM first to make the configuration changes in a controlled manner.
How do I make a DVD drive the first boot device in Hyper-V?
Open the VM’s Settings, select Firmware for Generation 2 or BIOS for Generation 1, and move the DVD drive to the top of the boot order. You can also use PowerShell to set the first boot device.
Can a Hyper-V VM boot directly from a USB drive?
Hyper-V does not provide native USB passthrough for direct firmware-level USB boot. For operating system installation, using a bootable ISO attached to a virtual DVD drive is generally the simpler approach.
What is the difference between Generation 1 and Generation 2 boot options?
Generation 1 uses legacy BIOS and supports IDE-based boot devices, while Generation 2 uses UEFI and supports SCSI-based boot devices. Generation 2 also supports Secure Boot and standard network adapter PXE boot.
Adding boot devices in Hyper-V is straightforward once you understand how the VM generation affects device compatibility and firmware settings.
If you’re installing an operating system, attaching an ISO to a virtual DVD drive and moving it to the top of the boot order is usually all you need. For more advanced configurations, PowerShell offers a convenient way to manage boot devices without navigating through multiple settings windows.
Before making changes, always verify the VM generation, check the attached devices, and confirm the boot order. These simple checks can help prevent unnecessary troubleshooting and keep your virtual machines running as expected.
· Enterprise & Mid-market Customers Worldwide.
· Support team available to assist you throughout your trial.
· Start a 60-day free trial or view demo to see how Info2soft protects enterprise data.