VM Won't Boot: 'Boot Image Not Found' on Hyper-V 2019

When this error shows up

You're running Hyper-V on Windows Server 2019 or 2022. You go to start a VM — maybe a Windows Server 2016 guest — and it just sits at a black screen. The error says something like "Boot image not found" or "Boot device not found" (error code 0x00000001). This usually happens after a power outage, a failed Windows update on the guest, or when you moved the VHDX file to another host without properly shutting down the VM.

Root cause in plain English

The VM can't find a bootable partition on its virtual hard disk. Two things cause this 90% of the time:

• Corrupted boot sector — The VHDX file got written to during a crash or unexpected shutdown. The boot configuration data (BCD) gets corrupted.
• Wrong boot order — Someone fiddled with the VM settings and set the DVD drive or network boot first. That drive is empty, so it fails.

Less common? The VHDX file is actually missing or the path got broken in the VM settings. But that's rare — you'd see a different error.

Fix it in 5 steps

Let's get this working. You'll need the VM stopped for all of this.

Step 1: Check the boot order

This is the easiest fix. Open Hyper-V Manager, right-click the VM, go to Settings. Under BIOS, check the boot order. Make sure the VHDX file (usually labeled "SCSI controller" or "IDE controller 0") is first in the list. Move DVD drive below it. Apply and try booting.

If that works, you're done. Skip the rest. If not, move on.

Step 2: Boot from an ISO and repair

You need a Windows installation ISO matching the guest OS version. Mount it in the VM's DVD drive. Then set the DVD drive as first boot device temporarily. Start the VM. When you see "Press any key to boot from CD or DVD", hit a key.

Once the setup loads, click Next, then Repair your computer at the bottom-left. Choose Troubleshoot > Advanced options > Command Prompt.

Step 3: Rebuild the boot sector

In the command prompt, run these three commands in order:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

The first two usually succeed. The last one might say it scanned for installations and found none. That's okay.

If bootrec /fixboot gives an "access denied" error, run this instead:

bootsect /nt60 sys

Then try bootrec /fixboot again.

Step 4: Check the VHDX file integrity

If bootrec didn't help, the VHDX itself might be corrupted. Shut down the VM, open PowerShell as admin, and run:

Optimize-VHD -Path "C:\Path\To\Your\VM.vhdx" -Mode Quick

This trims unused space but also checks the file structure. If it reports errors, run a full compact:

Optimize-VHD -Path "C:\Path\To\Your\VM.vhdx" -Mode Full

Still broken? Try mounting the VHDX in another VM or attaching it as a disk in Hyper-V Manager to see if the partition is visible. If you see RAW filesystem, the disk is toast.

Step 5: Restore from backup

At this point, if you've got a backup (you do, right?), restore the VHDX from the last known good state. If not, you're looking at rebuilding the guest OS. Sorry — that's the hard lesson.

What to check if it still fails

• Generation mismatch — A Gen2 VM won't boot from a Gen1 VHDX. Check the VM's generation in settings. If it's Gen2, the disk needs to be GPT, not MBR. Use diskpart to check the partition style from a repair ISO.
• Secure Boot — On Gen2 VMs, Secure Boot is on by default. If your ISO or disk doesn't support UEFI, it fails. Try disabling Secure Boot under Security in VM settings. I've seen this catch people after a Windows update.
• Storage path — Did you move the VHDX file? Hyper-V remembers the old path. In VM settings, check the location under IDE Controller 0 or SCSI Controller. If it's wrong, point it to the new location.
• Snapshot issues — If the VM had snapshots (checkpoints), the VHDX might be in a weird state. Delete all checkpoints via the VM's snapshot tree, then try again.

One last thing — if this happened after a power failure, also check the host's disk health. Use chkdsk /f on the host drive where the VHDX lives. Corrupted host filesystem can cause boot errors in the guest. Seen it twice in 14 years, but it's a quick check.

That's it. Nine times out of ten, it's the boot order or a minor BCD corruption. Don't panic — work through these steps and you'll have that VM back up in 20 minutes.