Cannot Disable Checkpoint Hyper V Upgrade and Try Again

How to Disable a Hyper-V VM Stuck in the Starting/Stopping Country

Hyper-V is a well-known hardware virtualization platform that is popular because information technology is the native Windows hypervisor. Virtualization provides many advantages and running virtual machines is user-friendly. However, errors tin can occur. It may happen that y'all go the "Hyper-5 failed to change state" error and the VM is stuck when trying to power information technology on or off. The commencement, stop and reset buttons don't work for the VM in this case. You cannot edit the VM settings and utilise the VM until you solve this outcome. If you are already looking for how to disable Hyper-V or how to uninstall Hyper-V, don't hurry up. This blog mail explains the possible reasons for getting the "Hyper-V failed to change land" error and methods to resolve this issue.

Explanation of the Error

Get-go, stop, reset buttons are commonly not available in the graphical user interface. If you try to click these buttons, the error bulletin is displayed. The complete text of the Hyper-V VM stuck error message displayed when y'all endeavor to kickoff or finish a virtual auto in Hyper-Five is displayed beneath:

The awarding encountered an error while attempting to change the land of the virtual machine.

VM-name Failed to change state.

The operation cannot exist performed while the object is in its current state.

The "Hyper-5 failed to change state" message can also contain this phrase:

The status cannot be changed.

Common reasons for the start/terminate VM fault are storage failure, incorrect network configuration, Routing and Remote Access configuration, VM power options, and insufficient permissions to access VM files.

Killing the Procedure of the Problematic VM

When you encounter a start/cease VM fault, you cannot just impale the VM traditionally by killing the Virtual Machine Worker Process (vmwp.exe), which is one of the important Hyper-V services / processes. You need to know the Globally Unique Identifier (GUID) of the problematic VM considering multiple instances of the vmwp.exe procedure are running in Windows and each example is related to the appropriate VM. If yous try to guess the needed vmwp.exe and impale each vmwp.exe case, you lot tin can impale an unknown VM each time, and yous could end up killing almost all of the VMs earlier you lot find the right one.

Method 1: Using native GUI tools

You can use the graphical user interface (GUI) of Windows and Hyper-V to identify the needed vmwp.exe procedure and stop this process. Hyper-V Manager is a tool with a GUI for virtual motorcar management in the Windows Hyper-Five environment.

Go the VM GUID in Hyper-V Managing director. Right-click the proper name of your Hyper-V host in Hyper-V Managing director and in the context bill of fare select Hyper-V Settings.

In the Hyper-V Settings window, click Virtual Machines in the left pane to find the path where VM files are located by default on the Hyper-V host. In our example, the path is E:\VMs\.

When you know the location where VM files are stored, become to this folder in Windows Explorer. Observe the subfolder where the files of the frozen VM are located. In my case, the VM proper noun is "Ubuntu Hyper-V". Open the VM binder, and you lot should encounter a subfolder and files with a long name consisting of digits and letters. This is the VM GUID needed to identify the vmwp.exe process and force the VM stop. In my example, the VM GUID is 3C555937-A999-4542-B77E-FD69488B8579.

If yous cannot find the VM GUID in the graphical user interface of Windows and Hyper-5, y'all can use Process Explorer or PowerShell (see sections below).

Once you have found the ID, you tin can terminate the vmwp exe job related to the problematic Hyper-V VM.

Open Windows Task Director in the host operating organization. Click Start > Run or printing Win+R, blazon taskmgr and hitting Enter.

Find the vmwp.exe procedure with the needed GUID in the User name cavalcade. Right-click the advisable vmwp exe process and in the context carte select End task to power off the VM and become the correct stop VM state.

Note: Yous can right-click the column header, for example, User name, and click Select Columns. Select the Command line and Description checkboxes in the Select Columns window, so click OK. After that, you can see the VM GUID for each vmwp exe procedure in Command Line column of the task manager.

Method 2: Using Process Explorer

You can identify the needed case of the vmwp exe procedure related to the problematic VM with Procedure Explorer, which is a free tool provided past Microsoft. Download Process Explorer, which contains advanced options not included in the standard task manager from the Microsoft website. Unzip the Process Explorer files to a custom binder.

Open up Hyper-V Manager, open VM settings for your problematic VM, and select virtual difficult bulldoze options. Re-create the full path to a virtual hard disk file. In our case this path is:

"E:\VMs\Ubuntu Hyper-V\Virtual Hard Disks\Ubuntu Hyper-V.vhdx"

Offset Procedure Explorer by running the advisable execution file (procexp64.exe in our instance).

Click the binocular icon and paste the path to the virtual disk file of the stuck VM in the Handle or DLL substring field, then click Search.

The instance of vmwp.exe needed is plant. Click vmwp.exe that was plant in the search window and the appropriate instance of the vmwp exe process is selected in Procedure Explorer automatically.

Right-click the selected vmwp.exe process and in the context carte click Kill Process.

Method 3: Using PowerShell to impale the VM process

Allow's open PowerShell and gear up the fault. If you lot attempt to run the Stop-VM -Force command, you can see that this command doesn't work for stopping the VM after the VM gets stuck. Apply this control to identify the unique ID of the VM:

Get-VM "VM-name" | fl *

As a more than elegant alternative, you can use these commands to cheque the ID:

$VMGUID = (Get-VM "Ubuntu Hyper-V").ID

Become-VM | Select Name, Id

In our case, we need to know the GUID of the "Ubuntu Hyper-V" VM. The GUID of this VM is saved as the $VMGUID variable in the retentivity for this PowerShell session.

Run these commands to kill the procedure and end VM:

$VMWMProc = (Go-WmiObject Win32_Process | ? {$_.Name -match 'VMWP' -and $_.CommandLine -match $VMGUID})

Stop-Process ($VMWMProc.ProcessId) -Strength

Now the problematic VM procedure is killed and the VM is stopped. You tin can try to edit the VM settings and run the VM.

Other Methods to Ready the Hyper-Five Failed to Modify Land Error

It may happen that you have killed the hang VM process in Hyper-Five simply the VM cannot start. In this example, if you lot endeavor to kickoff the VM, you could become the Hyper-5 error:

Virtual Machine Connection:

Failed to Modify State.

Below, I provide other possible reasons of the "Hyper-V failed to alter state" error, methods that can assist fix the error and how to turn off Hyper-V VMs completely after getting this error.

DVD drive settings

Open up VM settings and cheque DVD options for the VM. If the VM cannot access the ISO image, the mistake can occur. Make certain that the ISO file exists and the path is defined correctly. You tin likewise disable a virtual DVD bulldoze if this bulldoze is not used in a virtual machine.

Storage errors

Bank check whether there is enough disk infinite on VM storage. If at that place is bereft deejay space for storing VM files, the storage failure can cause VM to go stuck and show a "Hyper-Five failed to change state" error. If the VM failure occurred due to the lack of storage space, you may need to run these commands to set deejay errors inside VMs:

sfc /scannow
dism /online /cleanup-image /restorehealth

If yous cannot showtime a VM normally or at that place is VM stuck in a continuous loop, insert a Windows installation ISO image to a virtual DVD drive, boot a VM from this ISO epitome (open virtual BIOS/UEFI and select DVD-ROM every bit the first kick device), select Repair manner, start CMD, and run the command:

chkdsk /f /r /x c:

When the disk check is finished and disk errors are fixed, reboot the VM, boot from a virtual hard disk (the VM should boot at present) and run the commands mentioned before within the guest Os:

sfc /scannow
dism /online /cleanup-image /restorehealth

You may also need to check your concrete disks used for Hyper-V storage on a Hyper-V host.

Network configuration errors

Cheque the VM'svirtual network adapter settings. If the Network Adapter – Configuration Error status is displayed for at to the lowest degree ane network adapter, then y'all might have start/stop VM issues in Hyper-V. VM network adapters must be connected to existing virtual switches for normal operation. This mistake tin can be displayed if the network configuration was changed or became corrupted.

Detecting issues in logs

Check Windows Result Logs and Hyper-V related errors. Run compmgmt.msc, then go to Upshot Viewer > Applications and Services Logs > Microsoft > Windows > Hyper-V-Worker. If you see error messages in the logs, the caption of the mistake can point you to the source of the trouble.

Blocking access by antivirus software

Cheque your antivirus software settings. The antivirus must non cake access to Hyper-V VM files. If the antivirus blocks admission to VM files, add folders where VM files are stored to exclusions in antivirus settings. Hyper-V must accept full admission to VM folders and files.

VM power options

Check the power options in the settings of the guest operating system. Sleep fashion and hibernation must exist disabled. In the Windows invitee, open up Control Console, then go to Ability Options, and make sure that the "Put the estimator to sleep" selection is set to Never. If Ubuntu Linux is installed as the guest operating system, use the command to disable the sleep mode:

sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

Checking VMMS

vmms.exe is a process used by Hyper-V. Brand certain that the Hyper-V Virtual Direction Service (VMMS), which is one of the important Hyper-5 services, is running properly and the VMMS doesn't get stuck and is not in the starting or stopping state (status). The service status must be Running.

The VMMS service is related to the vmms.exe process.

Disable RRAS

Misconfiguration of Routing and Remote Access Service (RRAS) tin can be a reason for a Hyper-V VM getting stuck due incorrect network configuration. Try to disable RRAS in Windows Server operating as a Hyper-V host.

Press Win+R to open up the Run dialog box.

Type services.msc and hit Enter.

Find the Routing and Remote Access Service in the Services window, right-click the service and in the context menu click Properties. In the General tab of the Routing and Remote Access properties window, click Terminate and change the startup type to Disabled.

Rebooting the Hyper-V host machine

If any of the methods above don't help, try to reboot the Hyper-Five host machine. If you take other Hyper-5 hosts or a Hyper-V High Availability cluster, yous can migrate running VMs to other hosts and and then shut down the Hyper-5 host with the problematic VM.

Fixing Hyper-Five VM Stuck in the Saved State

Hyper-Five VM getting stuck can happen not only in the start/stop VM land, simply also in the saved VM state. The symptoms are similar and you cannot change the VM state of the problematic VM. The Start/Stop VM buttons don't work. If you close Hyper-V while a VM is being backed upwards, you can get the Hyper-V VM stuck in the saved state. This tin happen if the fill-in procedure is interrupted and a VM is put in the saved state. The VM can be corrupted or damaged in this case. Let's explore common reasons for this error and methods to prepare this mistake.

Disk errors

If a disk with VM files is unplugged while a VM is running, and so the error can occur for a VM and the VM is put into the saved state. This error is more plausible for Hyper-V home users who store VM files on USB disks. However, administrators of organizations should exist aware that this mistake can be caused by storage issues. In example of bereft deejay space, a VM hangs and can be too put in the saved state. If y'all take configured a VM to utilize virtual hardware that is non supported by a guest operating system, the VM can go stuck in the saved country. This issue can happen if you create a new VM and import an existing virtual disk with the installed guest Os. Edit VM options, select the correct storage controller and other disk options. Read virtually the difference between Generation 1 VMs and Generation 2 VMs for more information.

Bereft hardware resources

If you run multiple resource-hungry VMs on a Hyper-V host, in a example of insufficient memory and CPU functioning, a VM tin crash and be put in the saved country. And so you should brand an endeavor to fix the crashed VM. To avert this consequence, upgrade your hardware or don't run multiple heavy VMs on the host with low performance. Migrate the VM to another Hyper-V host if possible.

Incorrect folder permissions

If in that location are not plenty permissions for folders and VM files, then the VM can go stuck in the Saved state. Open the properties of the binder where the VM files are stored. Check the Security and Sharing tabs (if a VM is in a shared folder on the shared storage). Gear up permissions to Let all for the needed user or group.

Deleting the virtual machine

This is some other method to resolve the VM stuck in the Starting/Stopping/Saved State issue if other methods didn't aid. You don't want to lose data and for this reason, yous should copy virtual disk files to a condom location. This is something like a VM backup. Then delete the problematic VM including VM configuration files from the original location (right-click the VM and striking Delete in Hyper-V Manager). Create a new VM, copy the virtual disks from a fill-in to the new VM location and select an existing virtual disk when creating a new VM in Hyper-V.

A VM is stuck in the "Backing up" status

Another similar effect is the Hyper-V VM stuck in the Running state with the Bankroll upward status. You cannot start and terminate VMs in this state in Hyper-Five Manager. Rebooting the Hyper-Five host usually helps resolve this issue, just reboot is not desired because other VMs running on the host must be close downwardly or migrated.

The possible crusade of this error is an consequence with the Microsoft Hyper-V VSS Writer service on the Hyper-V host.

Open the command line (CMD) as administrator and run this command to bank check the condition of VSS writers:

vssadmin list writers

If at that place are no errors, the output for each VSS writer is similar to the output displayed on the screenshot below.

The Microsoft Hyper-V VSS Writer service depends on the parent Hyper-5 Virtual Machine Management service. For this reason, you have to restart the Hyper-V Virtual Machine Direction service to restart the needed VSS service and prepare the outcome.

The fastest way to restart the Hyper-Five Virtual Auto Management service is to open up Services in Figurer Management or run services.msc, right-click the service name and select Restart.

If Hyper-Five VSS Writer is hanging and not responding, you should manually end the vmms.exe process in Job Manager. Open up Task Manager, right-click vmms.exe and select End Process Tree in the context menu.

After you finish the vmms.exe process, virtual machines should disappear in Hyper-V Director. First the Hyper-Five Virtual Motorcar Direction service, and you lot should see the listing of your VMs once more and the backing up status of the problematic VM should be gone. Restarting these Hyper-Five services should resolve the issue.

Decision

The Hyper-V failed to alter land error is an unpleasant error for users and administrators when using virtual machines. Fortunately, in that location is a high probability to gear up the error related to the Hyper-V VM stuck when you cannot stop VMs that are problematic. This web log mail service looked at common reasons and possible methods for fixing the "Hyper-5 failed to change state" and "failed to restore virtual machine state" errors. You should be aware that sometimes VM information tin be corrupted after this error, other errors, and hardware failures. For this reason, it is recommended that yous perform Hyper-5 VM backup regularly to avoid information loss. Employ NAKIVO Backup & Replication to support your Hyper-V VMs with optimal operation and space-saving features. Download the free edition of NAKIVO Backup & Replication and protect your Hyper-Five environment.

calhounprou1949.blogspot.com

Source: https://www.nakivo.com/blog/how-to-disable-a-hyper-v-vm-stuck-in-the-starting-stopping-state/