Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

Fix PXE Boot Stuck or No Boot Image was found for HyperV VM

Posted on 17/10/202430/06/2026 Christian By Christian No Comments on Fix PXE Boot Stuck or No Boot Image was found for HyperV VM
  1. Home
  2. Virtualization
  3. Fix PXE Boot Stuck or No Boot Image was found for HyperV VM
PXE Boot Stuck or No Boot Image was found - Te bootloader did not find any operating system

In this article, we shall discuss how to “fix PXE Boot Stuck or No Boot Image was found for HyperV VM. The bootloader did not find any operating system”. This means that the bootloader could not find a bootable image from the network to boot the VM. Please see Linux Boot Process Explained Step by Step for Beginners, and how to Fix Windows Stuck on System Restore. Here is how to Fix Hyper-V VM Stuck in Stopping State.

Also, see “Measured Boot, Secure Boot, Trusted Boot, and Early Launch Anti-Malware: How to secure the Windows 10 boot process“. Here is also a guide on “MDT deployment failed and Stuck at Command Prompt: Windows installation does not proceed via PXE boot“.

Why was this error prompted “Bootloader did not load the OS”

Due to the boot order set on a VM on HyperV. You may get the following errors as shown below.

Boot Order

You will get the Below when the Hard Drive is selected first.

No boot image found

When the Network adapter is moved above the Hard drive. Then you may be stuck at the PXE boot window as shown below.

PXE over IPv4

With all the scenarios mentioned above. Basically, you have set up the VM and forgot to install the Operating System (OS).

Please see How to Create a Windows Server VM on HyperV, and How to start HyperV VMs in safe mode. Also, see Generation 2 VM: Set up a HyperV VM through PXE boot, and How to set up a VM via PXE boot on a Generation 1 VM.

Solution to No Boot Image was found

Here is a similar error for “The error “boot image was not found for Hyper-V””. In this case, the WDS service was not running.

As you can see, there could be numerous reasons for this error such as not having the right PXE Server Setup to assign IP address etc., routing?firewall issues, and as mentioned above, it could also be that the WDS service is not running.

To Fix issue, launch the Hyper-V Manager and select the VM and then click on settings.

VM settings

Please see How to deploy images to computers using PXE Boot, and how to Migrate Veeam Configuration Database to PostgreSQL Server. Here is How to configure Windows LAPS.

Add CD/DVD Drive drive on Hyper-V

The SCSI Controller in Hyper-V is a virtual device used to connect storage devices such as the virtual hard disks (VHDs) and DVD drives to a virtual machine. This provides necessary storage access for tasks such as installing an operating system from a DVD or ISO image.

Navigate to the SCSI Controller and select the DVD Drive and click on add.

SCSI Controller

Under specify the media to use, click on the “Image file” and browse to your image.

Browse iso image

Select your desired ISO File and click on open.

Select ISO

Ensure you move the DVD Drive up. Else, you might get stuck with the errors above due to the boot order set.

Boot from DVD - move Up

Click on Ok to continue.

Image attached for VM

Also, see Cybersecurity Tips to Secure Synology NAS against Ransomware, and how to Enable Autologon and Autostart for user session. Here is How to Diagnose a Windows Hardware Issue.

Connect to the VM and Install the OS

You can also right click on the said VM and select connect as shown below.

connect to VM

The image will be loaded

Loading files

Ensure you set your desired parameters, language, time and keyboard to install and click on Next.

Install windows

Click install now. Here are some similar guides “How to migrate WDS and MDT to a new Windows Server, “ADK|WinPE|MDT: Deploy Windows with WDS“, and How to update Microsoft Defender Antivirus into the install image of Windows (install.wim).

Instal windows server 2022

Select the OS to install

Data center desktop experience

Accept the license terms and click Next to proceed

Accept license

Please select Custom: Install Microsoft Server Operating System Only (Advanced).

Custom install

I only one drive, so the decision is simple lol!

Select disk to install

As you can see, the OS is currently being installed.

Installing Windows server 2022

Enter your password and click on Finish.

Customize settings

Upon restart, you can now login in and start working with your VM.

Login to the VM

Lastly, do not forget to detach the ISO Image. Navigate to the VM settings and set the media to use to none.

Set DVD to none

Click on OK to close the VM settings window.

SCSI DVD set to none

Post VM Installation Configuration

I have discussed this section extensively here: Post OS installation: Configure the properties of Windows Server. As you can see, I have configured the right TCP/IP parameters and joined the server to the domain. Please see How to join a computer to the Domain.

TCPIP-Domain Join

Lastly, do not forget to search and apply windows updates to your VM.

Install Windows Updates

I hope you found this article on how to “fix PXE Boot Stuck or No Boot Image was found for HyperV VM. The bootloader did not find any operating system” very useful. Please feel free to leave a comment below.

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
Virtualization, Windows Server Tags:fix PXE boot failure Windows Server, Hyper V, Hyper-V Gen2 PXE boot issues, Hyper-V network boot troubleshooting, Hyper-V VM PXE boot stuck, hyperV, Microsoft Windows, no boot image found Hyper-V, PXE boot error resolution Hyper-V, PXE boot Hyper-V fix, Virtual Machine, VMs, WDS PXE boot Hyper-V VM, Windows 10, Windows 11, Windows deployment PXE boot fix, Windows Server 2016

Post navigation

Previous Post: Analyse Disks with Treesize: Defragment and Shrink VMware Workstation VM Disks
Next Post: Sync file and photos from iOS and Mac with Synology Drive

Related Posts

  • Check Virtualization
    Enable Virtualization in BIOS: Determine if the Intel VT-x or AMD-V Virtualization Technology is enabled in BIOS Virtualization
  • banner 1
    How to Create Shared Folder in Windows Sandbox Virtualization
  • Windows Server 2016 1
    All About Windows Server 2016 Windows Server
  • Hyper V VM creation
    How to Create a Windows Server VM on HyperV Windows Server
  • maxresdefault
    The following errors occurred attempting to join the domain: The specified domain either does not exist or could not be contacted Windows Server
  • a3a5a8be58fa09468cd4f70d36869e98
    Restore AD Objects: How to restore deleted user accounts in Active Directory with Microsoft LDP and PowerShell Windows Server

More Related Articles

Install Microsoft PKI ADCS Set up Microsoft PKI (ADCS) for SystoLOCK via PowerShell Windows Server
dns error Domain Name System Protocol: Client Registration Issue Windows Server
maxresdefault 1 DriveLock Components: Important DriveLock components to master Windows Server
Capture 37 How to Configure Network Load Balancing on Windows Server Backup
Entire VM restore Restore VM to Original location using Veeam Entire VM restore Backup
SCVMM setup fails because it cannot find the specific Windows ADK Deployment Tools files SCVMM setup Fails: Fix Missing Windows ADK Deployment Files Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

Top 30 Sysadmin blog

veeaam100

Veeam Vanguard

  • Enable Nexted Virtualization on VirtualBox
    ESXi VMB 411 Halting: Virtualbox Nested VT-X/AMD-V greyed out Virtualization
  • selinux in production
    How to locate directory file context and restore it with SELinux Linux
  • hero azure activedirectory
    How to add and verify a custom domain name to Azure Active Directory AWS/Azure/OpenShift
  • Veeam Virtual Appliance for Backup and Restore
    How to setup Veeam Software Appliance v13 Backup
  • enable WinRM
    WSManFault Message 2144108526 0x80338012: Fix the client cannot connect to the destination specified in the request Windows Server
  • mbamclient
    How to deploy MBAM Client as part of a Windows Deployment Windows Server
  • image 22
    How to clone a Windows Server running on VirtualBox Virtualization
  • computefeature
    How to use Azure Compute Gallery AWS/Azure/OpenShift

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,746 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Contact
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon
  • Bsky

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.