Skip to content

TechDirectArchive

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

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

Fix No bootable media found system halted: Unable to PXE boot

Posted on 27/05/202023/11/2025 IT Expert By IT Expert No Comments on Fix No bootable media found system halted: Unable to PXE boot
  1. Home
  2. Virtualization
  3. Fix No bootable media found system halted: Unable to PXE boot
No bootable media found

Oracle VM VirtualBox is a free and open-source hosted hypervisor for x86 virtualization, developed by Oracle Corporation. It was created by Innotek and was acquired by Sun Microsystems in 2008, which was in turn acquired by Oracle in 2010. In this article, we shall discuss how to fix “No bootable media found system halted: Unable to PXE boot WDS to Virtualbox”. Please see”the virtual machine has terminated unexpectedly during startup with exit code 1 (1×0)“, and Windows failed to start, a recent hardware or software change might be the cause.

For similar errors, see the following articles, HyperV – A boot image was not found and why does the legacy PXE not does work on Generation 2 VM.

Why was the error “No bootable media found system halted” prompted?

When you try to boot a VirtualBox VM into PXE (Microsoft WDS), using the default Intel PRO/1000MT Desktop adapter. You may have seen the error message.

system halted

Solution

To resolve the following issues “Fatal!, No bootable media found system halted! follow the steps below.

This extension pack includes the required files for the boot to continue normally, a few screen shots are shown below detailing what you need to do.

Navigate to the following link to download VirtualBox 6.1.8 Oracle VM VirtualBox Extension Pack. Click on the All supported platform as shown below.

PXE boot

This will ensure the VM VirtualBox Extension Pack is downloaded to your system. In my case I am using macOS.

Virtualbox

However, Double click on the installer to install the VM Extension pack. Click on install

No bootable media found

Moreover, Accept the license as shown below

Nonetheless, You will be prompted to enter your password to proceed.

Enter the username and password as shown below

Note: I got an error! You may also get compatibility issues.

Consequently, Please ensure your VirtualBox is updated to date!

After updating VirtualBox, ran the VirtualBox Extension Pack again, it was successful as shown below.

Now you can select the boot order. Select the VM and right click on it and select Settings. This will open the settings windows and click on System.

Note: You also have to ensure you are on the same network

Now the error is no more present and we can boot over the network.

For how to add images to WDS, see Windows Deployment Services: How to add boot and install images to WDS and configure Multicast transmission via the GUI and WDSUTIL and how to set up and install WDS role

I hope you found this blog post on how to fix “No bootable media found system halted: Unable to PXE boot WDS to Virtualbox” helpful. If you have any questions, please let me know in the comment session.

5/5 - (1 vote)

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
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:VirtualBox, virtualization, WDS, WDSUTIL, Windows 10, Windows Deployment Services

Post navigation

Previous Post: Add boot and install images to WDS and configure Multicast transmission via the GUI and WDSUTIL
Next Post: How to deploy images to computers using PXE Boot

Related Posts

  • VMware and HyperV are not compatible
    How to fix VMware and HyperV are not compatible Virtualization
  • OpenVz
    OpenVZ template on Proxmox Server: How to Guide Virtualization
  • Disaster Recovery Test Checklist: What to Capture Before You Start Backup
  • ESXi
    How to install ESXi on VirtualBox Virtualization
  • 1723152 3cc3 2 750x405 1
    Cluster creation in Proxmox VE Virtualization
  • VMware Aria
    VMSA-2022-0026: An arbitrary file read vulnerability in VMware Aria Operations Security | Vulnerability Scans and Assessment

More Related Articles

VMware and HyperV are not compatible How to fix VMware and HyperV are not compatible Virtualization
OpenVz OpenVZ template on Proxmox Server: How to Guide Virtualization
Disaster Recovery Test Checklist: What to Capture Before You Start Backup
ESXi How to install ESXi on VirtualBox Virtualization
1723152 3cc3 2 750x405 1 Cluster creation in Proxmox VE Virtualization
VMware Aria VMSA-2022-0026: An arbitrary file read vulnerability in VMware Aria Operations Security | Vulnerability Scans and Assessment

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • 33
    The wim file needs to be remounted: Fix error 0xc1510114 Windows Server
  • maxresdefault 2 3
    How to configure WatchGuard WebCenter Network | Monitoring
  • SSL on WAMPServer
    Setup VirtualHost with SSL on WAMP Server Linux
  • SUBVERSION FEATURE
    How to Install Apache Subversion on a Linux System Linux
  • how to fix the sorry this file type is not permitted for security reasons error in wordpress 5e4a5632967c7
    Error 1707: Network address invalid when trying to connect remotely Windows
  • ntp server testen
    Enable or disable Linux System’s Clock Sync with NTP Server Linux
  • ERRORFEATURE
    Fix 404 Not Found Repository Errors in Ubuntu/Debian distribution Linux
  • hero windowsadmincenter
    Failed to create a scheduled task: There is no disconnected command associated with the runspace Windows Server

Subscribe to Blog via Email

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

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

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.