If you continuously encountered the “VirtualBox FATAL: No bootable medium found, System halted” error when you try to install Windows 10 in VirtualBox, read on as this post will give you some potential fixes to resolve the problem – you will be guided on how to choose the ISO image to fix this error in VirtualBox. This kind of error is a very common one especially if you have a corrupted ISO file or if you have not selected an ISO file for your virtual machine.
Like pointed out, this error pops up when you have a corrupted ISO file or if the ISO file is not attached to the virtual machine. You have to select the ISO file while you create the virtual hard disk, else, you will most likely face this problem, and to fix it, you need to download fresh Windows ISO, create a new IDE Controller, assign Windows ISO to the IDE Controller and then boot your virtual machine. For detailed steps, follow the instructions below but before you start, make sure that you have a valid and uncorrupted Windows ISO.
Step 1: First, you need to open the VirtualBox program on your computer and select the virtual machine.
Step 2: Next, click on the Settings button or you can also right-click on the virtual machine and select Settings from the context menu.
Step 3: Once you’re in the Settings panel, go to the Storage section and from there, create a Controller: IDE.
Step 4: To create a Controller: IDE, click the Add new storage controller icon and select the “Add IDE Controller” option.
Step 5: After that, click the Add optical drive icon and click on the Choose disk button. You will then see all the attached and non-attached ISO files. However, you have to add the new ISO file that you just downloaded.
Step 6: To add the new ISO file, click the Add button and select the ISO file and then select the .iso file from the Non Attached section.
Step 7: Now click the Choose button and afterward, make a checkmark in the Live CD/DVD checkbox and then select the IDE Primary Master from the drop-down menu of the Optical Drive.
Step 8: Once you’re done, save the changes made and try booting into your virtual machine again.