Message says Fatal; No bootable medium found! System halted.

I'm trying to set up a new VM, and am having problems. I have done it before, but it was a long time ago. I'm using Oracle VM VirtualBox Manager. I have the Windows 10 reinstall DVD in the computer. I also tried Windows 7 reinstall DVD. It said the same thing for both.

Fatal; No bootable medium found! System halted.

My computer is a Dell Laptop and is Inspiron 17. I don't know what series. The numbers are faded. I posted a log below. I hope that helps.

https://www.bleepingcomputer.com/forums/t/698076/attaching-files-to-posts-on-bleepingcomputer/  3 step proccess

Oops, I made a mistake. It was late, and I was fixing to go to bed. I hope this works.  10Win Now.-2022-08-28-01-24-01.log   130.16KB   1 downloads

Here it is again, maybe not again, since it didn't post the last time.

The message indicates you haven't selected a bootable medium, or didn't select the correct one. You may also get that error if you selected the wrong version of the image you are trying to install.

https://askubuntu.com/questions/413594/what-does-no-bootable-medium-found-mean-in-virtualbox

Thanks for helping me out. I'm going to work on it some more on Friday night. Been busy the past couple of days.

Today, I tried installing from a USB stick. But still not working. I checked the settings, and here is what they show for storage.

Controller;SATA.

Yield sign next to usbdisk.vmdk

Empty.

New Win10_vhd

Attributes

Name;SATA

Type AHCI

Port count 4

So thats what it is showing. I think I made a mistake somewhere.

Looks like the vmdk image is damaged or unbootable. How did you create the vmdk on the USB drive?

You might want to have a look at this.

https://www.howtogeek.com/187721/how-to-boot-from-a-usb-drive-in-virtualbox/

Right now I'm using a recovery DVD. When I turn the computer on, it shows a black screen, and start PV6. I press escape, and that brings back Windows. But while I use a DVD, it still shows usbdisk.vmdk. I just removed usbdisk. Going to see what that will do. In empty, I checked CD/DVD. Ok, still the same message. I will try some more tomorrow night.

Forgot to ad.

Under storage, it now has this.

Controller;SATA.

Empty.

New Win10_vhd

For empty, SATA port 1 is used.

Edited by Sam Gunn, 08 September 2022 - 09:29 PM.

I did a search on VM, and I found out something about if my computer can support a VM. I did a search in Powershell. Here are the results.

=====================================================

Hotfix(s):                 15 Hotfix(s) Installed.

                           [01]: KB5017022

                           [02]: KB4562830

                           [03]: KB4570334

                           [04]: KB4580325

                           [05]: KB4586864

                           [06]: KB5003791

                           [07]: KB5012170

                           [08]: KB5017308

                           [09]: KB5011352

                           [10]: KB5011651

                           [11]: KB5014032

                           [12]: KB5014035

                           [13]: KB5014671

                           [14]: KB5015895

                           [15]: KB5016705

Network Card(s):           3 NIC(s) Installed.

                           [01]: Realtek PCIe FE Family Controller

                                 Connection Name: Ethernet

                                 DHCP Enabled:    Yes

                                 DHCP Server:     192.167.1.1

                                 IP address(es)

                                 [01]: 192.168.1.2

                                 [02]: fe80::512a:b668:5fc5:1e61

                                 [03]: 2603:6080:a60b:1d46:49bd:14f9:deda:c866

                                 [04]: 2603:6080:a60b:1d46:512a:b668:5fc5:1e61

                                 [05]: 2603:6080:a60b:1d46::1000

                           [02]: Qualcomm QCA9377 802.11ac Wireless Adapter

                                 Connection Name: Wi-Fi

                                 Status:          Media disconnected

                           [03]: VirtualBox Host-Only Ethernet Adapter

                                 Connection Name: VirtualBox Host-Only Network

                                 DHCP Enabled:    No

                                 IP address(es)

                                 [01]: 192.167.56.1

                                 [02]: fe80::39f2:5b96:6f7d:faf8

Hyper-V Requirements:      VM Monitor Mode Extensions: Yes

                           Virtualization Enabled In Firmware: Yes

                           Second Level Address Translation: Yes

                           Data Execution Prevention Available: Yes

===============================================

Under DHCP Enabled, it says no. But it looks like my computer can host a VM.

An update. I just tried to setup a VM again, but came across this problem.

=============================================

The VM session was closed before any attempt to power it on.

Result Code:

E_FAIL (0x80004005)

Component:

SessionMachine

Interface:

ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

============================================================

I found an ISO file on my desktop. I had downloaded it back in March. I named the VM Abba. Here is how storage is setup.

Abba.vdi SATA Port 0

Host Drive D SATA Port 1

Windows.iso SATA Port 2.

I hope I did it right this time. But I don't know what the problem is.

Ok, another update.  I checked the settings for another VM, and I put Windows.iso on there. That one worked. Windows got installed. But I now have another problem. It is showing a black screen, with the Windows logo. And it says on there getting ready. It has been showing that message for a while. Also has the spinning circle above getting ready. Anybody know what to do next? It might be Monday, or Friday before I can work on the VM again.

RE the E_FAIL (0x80004005) error, that can indicate a missing virtual machine file, or issues with the hardware/settings on your computer.

https://helpdeskgeek.com/help-desk/6-ways-to-fix-virtualbox-result-code-e_fail-0x80004005-error-in-windows/

I suspect the issue with the Windows VM you outlined in your other post may be something similar. Or the Windows image is old, and there are a large number of updates that need to be installed. One of these references VMs on Azure, but it is still valid. Second post, user had to wait several hours for the VM to be ready.

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-vm-boot-configure-update

https://www.reddit.com/r/HyperV/comments/o77l75/windows_10_vm_stuck_on_getting_ready_infinitely/

I will download another Windows 10 tomorrow. If I can, I will rename it NewWindows10.iso. And then see if that will work. Won't have to create another VM. Just check the settings, and then change the iso. Thanks for helping me out.

I downloaded a new ISO, and I created a new VM. But I keep getting this message. I don't know what it means.

=======================================================

Failed to open the disk image file C:\Users\Owner\Desktop\NewWindows10.iso.

Could not get the storage format of the medium 'C:\Users\Owner\Desktop\NewWindows10.iso' (VERR_NOT_SUPPORTED).

​​

There seems to be an issue with the .iso file, or the way it is formatted.

Where did you download the file from? Did you convert it to an .iso format, or was it downloaded in that format? Did you have problems with the download?

Is your version of VirtualBox up to date?