Error: No Operating System Was Loaded in Hyper-V
When you boot a newly created virtual machine, you receive an error message about no operating system was loaded in Hyper-V. The causes vary, and you can refer to the information in the following article to fix this error.
Case: No operating system was loaded in Hyper-V
I need a Hyper-V machine to run a win10 32 bits machine on a win10 64 bits pro I uploaded an official win10 32 bits .iso. I created a Hyper V using this .iso. Everything went smoothly. I started the machine, then it repeatedly stops on:
1. SCSI DVD (0,1) the boot loader did not load an OS
2. SCSI disk (0,0) the boot loader did not load an OS
3. Network adapter (00155D004E00) a boot image was not found No OS was loaded. Your virtual machine may be configured incorrectly. The VM does not see the .iso or the .iso has not the right format or something is wrong in the VM configuration?
Hyper-V is a type 1 hypervisor which cannot run without OS. So it requires you to install an operating system on Hyper-V virtual machine. But as stated in the case above, the "no operating system was loaded" error may happen, not only on 32-bit systems, but also on 64-bit systems occasionally. How can we deal with it and make the virtual machine work normally?
In this article, I will analyze the possible causes for the error, and offers you some effective solutions.
Possible causes for no operating system was loaded in Hyper-V
The error in the case - no operating was loaded in Hyper-V may occur when the configuration for the VM in Hyper-V is incorrect. To be specific, you can consider the following causes:
Cause 1. ISO file was modified or moved.
You should make sure the downloaded ISO file was complete, and you cannot move the ISO from the selected location to a new location, since Hyper-V cannot recognize the new location automatically.
Cause 2. Mismatched Hyper-V Generation.
Generation 1 virtual machines support most guest operating systems, and Generation 2 virtual machines support most 64-bit versions of Windows. Also, the Generation 1 supports BIOS boot mode while Generation 2 supports UEFI. If these items were mismatched, you will likely encounter the no operating system was loaded error in Hyper-V virtual machine.
For example, if you encounter this error on a Generation 2 virtual machine with 32-bit Windows installed, you can create a Hyper-V 32-bit guest instead, and disable Secure Boot to solve the issue.
Cause 3. The virtual hard drive is not intact.
These are some possible reasons for the "no operating system was loaded" error in Hyper-V. Now you can try to manually reinstall the operating system on virtual machine and reconfigure the settings.
How to fix Hyper-V no operating system was loaded error
After knowing the possible reasons, then you need to try fixing the error and configure Hyper-V virtual machine correctly. I will mainly introduce 2 ways:
- Create a Generation 1 virtual machine in Hyper-V
- Relocate ISO in Hyper-V
Fix 1. Create a Gen1 Hyper-V virtual machine
Due to the incorrect Hyper-V UEFI, no operating system was loaded in Hyper-V VM. So you should recreate a new virtual machine in Hyper-V and pay attention to the following steps.
1. On Specify Generation section, select Generation 1 instead of Gen 2.
2. On Installation Options section, select Install an operating system from a bootable CD/DVD-ROM >> Image file(.iso), then click Browse to locate the ISO file.
Many people often choose Install an operating later while setting up the virtual machine, and forget about it while booting up the machine.
Fix 2. Relocate ISO file in Hyper-V
If you configured the virtual machine correctly when setting up, it is also possible that a boot image was not found in Hyper-V due to some internal conflicts, so you are required to relocate the ISO and boot Hyper-V from ISO.
Steps to fix a boot image was not found in Hyper-V:
1. Open Hyper-V Manager and right-click a virtual machine, then select Settings.
2. Navigate to SCSI Controller >> DVD Drive. Choose image file option and click Browse to relocate the ISO file.
3. Click OK, then restart Hyper-V VM.
For Gen2 Hyper-V virtual machine, some factors may fail to boot VM from ISO file such as UEFI boot issue. Please try disabling EUFI in the BIOS settings.
Uncertain Hyper-V internal factors may cause that virtual machine to fail to boot. It’s also possible to result in data loss forever. For businesses, data loss can pose serious financial damages or even a business crisis. So, facing the increasing data, having a reliable automatic backup plan will protect your business data from security threats and saves you a lot of time.
Important: Always backup Hyper-V to protect VMs from errors
AOMEI Cyber Backup is a reliable assistant to protect Hyper-V virtual machines. It schedules backup for multiple Hyper-V VMs simultaneously, which reduce the time cost and human errors. Besides, without any complicated configuration, you can restore a virtual machine to the same or new location easily when your original VM system corrupted.
With the free backup software, you can easily enjoy:
Perpetual Free: No time limit for AOMEI Cyber Backup Free Edition.
Easy-to-use: Backup numerous virtual machine with flexible backup strategies based on a few clicks.
Auto VM Backup: Run multiple VM backups automatically without human intervention and business downtime.
Fully Compatible with Hyper-V & VMware: Backup the entire Hyper-V or VMware virtual machine including OS, configuration, application, personal data and system state.
Offsite Restore: According to 3-2-1 backup rule, it can backup VMs to different places easily and offers instant recovery based on a few clicks.
Please hit the button below to download and use AOMEI Cyber Backup for free:
*You can choose to install this VM backup software on either Windows or Linux system.
Automate Hyper-V backup for free:
1. Launch AOMEI Cyber Backup and bind your Hyper-V device.
2. Create New Task: set up Backup Target and Schedule.
✦ Target: specify the backup location by entering a network or local path. It allows you to back up VM to different locations such as backing up VM to NAS.
✦ Schedule: set up the backup task with full/incremental backup and select the time to run each backup automatically.
✦ Click Start Backup. From the drop-down menu, you can decide to perform backup later or now.
3. Restore: Select backup content and recovery destination. You can restore the entire VM securely hitting Restore to original location, which saves time to reinstall and configure the applications and simplifies the procedures of data recovery.
✍ While the Free Edition covers most of the VM backup needs, you can also upgrade to enjoy:
✦ Batch VM backup: batch backup large numbers of VMs managed by vCenter Server or on standalone ESXi hosts.
✦ Backup Cleanup: Configure retention policy to auto delete the old backup files and save storage space.
✦ Restore to new location: Easily make a clone of a virtual machine in the same or another datastore/host, without reinstalling or configuring a new VM.
AOMEI Cyber Backup's automated backup policy secures data of virtual machines, meanwhile, its instant recovery enhances business continuity. Facing with the massive growth of data, a professional backup tool is ideal for your virtual environment.
Sometimes there could be some problems when using Hyper-V. For example, you may get the error of “no operating system was loaded” in Hyper-V, so you can refer to the methods in this article. Or if you get “Not enough memory in the system to start the virtual machine” error, which means Hyper-V VM ran out of memory, so you should do to reassign the Hyper-V memory.