How to Fix Hyper-V Virtual Machine removed after reboot

Learn how to fix the issue of Hyper-V virtual machines disappearing after a reboot with our step-by-step guide. Troubleshoot and restore your VMs easily!

We discovered that after restarting the host computer, all or one Hyper-V virtual machine(s) were deleted. This might be highly aggravating because one may have to establish a new machine and repeat the tedious process. They might be either fresh or copied virtual machines. In this post, we will discuss the issue and what you can do if the Hyper-V Virtual Machine is uninstalled after a reboot.

Fix Hyper-V Virtual Machine Removed After Reboot

If the Hyper-V Virtual Machine is uninstalled after a reboot, make sure the host is updated. So, if you're on Windows 11/10 or Windows Server, be sure to check for updates. If the host machine has been upgraded, you can use the solutions outlined below.

1) Restart the Hyper-V Virtual Machine Management Service.

The Hyper-V Virtual Machine Management Service is an essential Hyper-V feature. It oversees the activities and status of virtual machines (VMs) on a Hyper-V host. If you are experiencing problems with Hyper-V, it is recommended that you restart the service. To do so, follow the instructions below.

• Open the Services app by searching for it in the Start menu.
• Now search for the Hyper-V Virtual Machine Management Service.
• Right-click on it and choose Restart.

If the service was stopped, right-click it, select Automatic as the Startup type, and then click Start. Once completed, reboot the machine to see if the problem has been resolved.

2] Create a new virtual machine using the existing hard drive.

The next step is to construct a new virtual machine utilizing the existing hard disk, as the existing virtual machine may be corrupted. If you uninstalled all of your virtual machines, you can probably avoid this option because it is unlikely that all of them are corrupted. Follow the steps below to establish a new computer using your existing hard disk.

• Open Hyper-V Manager by searching for it in the Start Menu.
• Now, navigate to the Actions area and select New > Virtual Machine.
• Then, input the machine's name and location, and click Next.
• You must then specify the generation, allocate the memory, and continue the on-screen instructions until you reach the Connect Virtual Hard Disk part.
• Select Use an existing virtual hard disk, click Browse, navigate to the location of your VHD or VHDX file, and pick it.
• Finally, follow the on-screen instructions to finish the process.

Once completed, open the machine to ensure that everything is in working order. If everything is fine, you can access the machine, restart the host, and observe if it is being removed. Hopefully, this time you will not encounter this problem.

3] Point to the virtual machine setup file.

You must check the location of the configuration file. Usually, the.The XML files are found in C:ProgramDataMicrosoftWindowsHyper-VVirtual Machines. Make a backup of your virtual machine configuration files before making any changes.

We will utilize symbolic links to generate a reference to the configuration file, making it appear to be in the original place. To proceed, enter the Command Prompt as an administrator and run the following command: mklink "C:ProgramDataMicrosoftWindowsHyper-VVirtual Machines.xml" "D:VMs.xml".

Replace with the virtual machine's actual GUID, and change the path D:VMs.xml to correspond to the correct location of the.XML file on your alternate disk.

Once that is completed, reboot the computer to see if the problem has been resolved.

4) Reinstall Hyper-V.

If all else fails, we must restore the Hyper-V function since if it is corrupted, you may experience strange troubles like the one in question. To do so, follow the instructions below.

• Open the Control Panel.
• Change the View to Large Icons.
• Click on Programs and Features.
• Now, select Turn Windows Features On or Off.
• Look for Hyper-V, untick it, then click OK.
• Now, select Hyper-V again and click Ok.

After you've restored Hyper-V, add all of your virtual machines and see if the problem is addressed.

---

---

---

---

---

---

---

---

---

---

---