When this happens, the virtual machine refuses to stop, and thus, it can’t be started which isn’t something you want. This can happen due to a number of reasons that we will mention down below. However, before we begin, it is important to mention that, at times, the issue is simply caused by an outdated Windows host machine. Therefore, before you start off with this article, make sure that you have installed all of the Windows updates available. With that said, let us get started. Now that we are done with the possible causes of the issue, let us get started with the methods through which you can get your virtual machine back up again.
Method 1: Kill the Virtual Machine
By killing, we don’t mean to completely get rid of the virtual machine. Rather, it means to end the process of the virtual machine that is stuck and so that you can start it up normally again. This is a rather simple process if you have a single virtual machine running on the host machine. If you do, you can skip through some of the steps that we are going to list down below which helps in finding the GUID of the problematic virtual machine. In case you have multiple virtual machines, you can’t just simply kill the Virtual Machine Worker Process or vmwp.exe without knowing the GUID of the stuck virtual machine as the process appears multiple times in Task Manager. Once you have the GUID, you can find the process corresponding to that ID and kill it without any worries. Follow the instructions below to do this:
Method 2: Change Power Options
As it turns out, the power options of your host Windows machine can also affect the state of your Hyper-V virtual machines. One of the facing the same problem said that changing the display to never turn off fixed the problem for them. Thus, it is worth a shot. Here’s how to do it:
Method 3: Disable RRAS
A misconfigured remote access service can also result in the issue. As we have mentioned earlier, your network interface might be messing up the service which causes the virtual machine to get stuck. Therefore, an easy way of fixing this would be to disable the Routing and Remote Access service. Here’s how to do it:
Method 4: Reboot the Host Machine
In most cases, an issue as such can be easily resolved by simply rehosting the host machine. Once you have rebooted the host machine, the VM will clear out and start normally. Also, make sure that your system is up to date as the issue might also be caused by a Windows bug which is often patched in the follow-up updates.
Fix: Hyper-V Virtual Machine Stuck in Saved StateFix: Ethernet Switch Error Virtual machine failed to start in Hyper-V 2019Fix: Logon Failure when Starting Virtual Machine in Hyper-V 2019How to Create and Run a Virtual Machine With Hyper-V
