Hyper v starting windows висит

Symptoms

On a computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed, the startup time of the computer keeps increasing. After a while, the computer stops responding when the computer is in the startup process.

Note If the computer runs some virtual machines, this issue usually occurs when you frequently back up all the disks on the computer.

Additionally, many of the following PlugPlayManager events that have Event ID 12 are logged in the System log:

Notes

• The size of the %SystemRoot%\system32\config\system system registry hive increases after every backup operation..

• If you view the registry hive by using Registry Editor, the following registry entries are logged repeatedly. For example, the following registry entries are logged repeatedly 10000 times or more.

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_Msft&Prod_Virtual_Disk

  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\STORAGE\Volume\{f1030a29-1024-11df-b7a9-001b214f4bef}#0000000006500000

  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#VOLUME#{E717314D-23B5-11DF-AA86-001B214F4BEF}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}«DeviceInstance»=»STORAGE\\Volume\\{e717314d-23b5-11df-aa86-001b214f4bef}#0000000000100000»

• This issue also occurs in Windows Server 2008. However, no hotfix is available for Windows Server 2008. To work around this issue, see the «Workaround» section.

Cause

This issue occurs because there are a large amount of orphaned registry keys.

The Volume Shadow Copy Service (VSS) snapshots create many registry keys. However, they are not deleted after the VSS snapshot operations are completed.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2. Additionally, you must have the Hyper-V role installed.

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Vhdmp.sys	6.1.7600.20714	217,984	18-May-2010	04:14	x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Vhdmp.sys	6.1.7600.20714	482,688	18-May-2010	02:04	IA-64

Workaround

Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To work around this issue in Windows Server 2008 R2 or Windows Server 2008, clean up all orphaned registry key entries. To do this, follow these steps:

1. Download the DevNodeClean tool.

2. Perform one of the following operations:

   • Run the DevNodeClean tool as administrator.

   • At a command prompt, locate to the folder path of the DevNodeClean.exe file, type the following command, and then press ENTER:

     devnodeclean /r
     Note We recommend that you schedule the devnodeclean /r command to run one time every week.

If the DevNodeClean tool does not work, you can delete the registry keys manually or contact Microsoft Support for help.

For more information about the devnodeclean command, click the following article number to view the article in the Microsoft Knowledge Base:

934234 How to remove registry information about devices that will never be used again on a computer that is running Windows Server 2003

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name	Amd64_vhdmp.inf_31bf3856ad364e35_6.1.7600.20714_none_0359a1b5fc340e52.manifest
File version	Not applicable
File size	2,079
Date (UTC)	18-May-2010
Time (UTC)	08:58
Platform	Not applicable
File name	Package_1_for_kb982210~31bf3856ad364e35~amd64~~6.1.1.0.mum
File version	Not applicable
File size	1,840
Date (UTC)	18-May-2010
Time (UTC)	11:49
Platform	Not applicable
File name	Package_2_for_kb982210~31bf3856ad364e35~amd64~~6.1.1.0.mum
File version	Not applicable
File size	1,840
Date (UTC)	18-May-2010
Time (UTC)	11:49
Platform	Not applicable
File name	Package_3_for_kb982210~31bf3856ad364e35~amd64~~6.1.1.0.mum
File version	Not applicable
File size	1,816
Date (UTC)	18-May-2010
Time (UTC)	11:49
Platform	Not applicable
File name	Package_for_kb982210_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum
File version	Not applicable
File size	2,180
Date (UTC)	18-May-2010
Time (UTC)	11:49
Platform	Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name	Ia64_vhdmp.inf_31bf3856ad364e35_6.1.7600.20714_none_a73caa2843d4a618.manifest
File version	Not applicable
File size	2,077
Date (UTC)	18-May-2010
Time (UTC)	04:25
Platform	Not applicable
File name	Package_1_for_kb982210~31bf3856ad364e35~ia64~~6.1.1.0.mum
File version	Not applicable
File size	1,835
Date (UTC)	18-May-2010
Time (UTC)	11:49
Platform	Not applicable
File name	Package_for_kb982210_rtm~31bf3856ad364e35~ia64~~6.1.1.0.mum
File version	Not applicable
File size	1,444
Date (UTC)	18-May-2010
Time (UTC)	11:49
Platform	Not applicable

Hyper-V is Microsoft’s hardware virtualization product that lets you run different operating systems on your Windows computer. You can install multiple operating systems on a single Windows operating system using Hyper-V. The computer on which you install Hyper-V is called the host machine. Sometimes, you may encounter technical issues on the Hyper-V platform. One of the most common issues on the Hyper-V platform is getting stuck on starting state. If your Hyper-V Virtual Machine is stuck in Starting State, the solutions provided in this post will help you resolve the issue.

Failed to change state. The operation could not be performed while the object is in its current state

When you start a Virtual Machine in Hyper-V, its state shows “Starting (x%),” where the x% shows the loading percentage. When the virtual machine is loaded 100%, Hyper-V launches that operating system on your host machine. But in some cases, Hyper-V Virtual Machine gets stuck in Starting State. When this happens, Hyper-V may or may or may not show an error message. You should wait for some time and see if an error occurs. If Hyper-V shows you an error after some time, you should troubleshoot according to that error message. However, you can also follow the suggestions provided in this article to get the issue resolved.

Below, we have listed some possible solutions to fix this issue on Hyper-V. But before you proceed, let’s see some possible causes of this error.

• More than one Virtual Machine is installed on the same disk of your host machine and you are running all of them at the same time.
• Antivirus software is blocking the files required to run Hyper-V VM.
• The Hyper-V Services are not running properly.

We also suggest you restart your computer (the host machine) and see if it works. Sometimes, problems occur due to a minor glitch that can be fixed simply by restarting the device. Also, check for Windows Updates and install the latest patch, if available.

Let’s talk about the solutions to fix this issue.

1. Kill the vmwp.exe process
2. Restart all Hyper-V Services
3. Add vmwp.exe as an exception to your antivirus
4. Miscellaneous fixes

Below, we have explained all these solutions in detail.

1] Kill the vmwp.exe process

Sometimes, Hyper-V Virtual Machine freezes and shows the status as “Starting” along with the loading percentage. For example, a Virtual Machine gets stuck at a Starting 1% or 10%, etc. In this case, killing the Virtual Machine Worker process helps fix the issue. Virtual Machine Worker Process is one of the essential Hyper-V processes or services. It is required for the proper functioning of the Hyper-V Virtual Machine. You will find this process running in the Task Manager with the name vmwp.exe.

Killing this process will resolve the freezing Hyper-V VM issues. The steps for the same are as follow:

1. Open the Task Manager.
2. Switch to the Details tab.
3. Locate the vmwp.exe process. Right-click on it and select End Task.

The above steps are pretty easy to perform if you have only one Virtual Machine on your host machine. But if you have multiple VMs installed on your host computer, you may find more than one vmwp.exe process in the Task Manager. In this case, it is necessary to identify the correct vmwp.exe process before killing it. Every Virtual Machine has a unique GUID (Globally Unique Identifier). To identify the GUID of VM, go through the following steps:

1. Open Hyper-V Manager.
2. Right-click on your Virtual Machine and select Hyper-V Settings.
3. Now, select Virtual Machines from the left side. You will see the path where your Virtual Machine is installed.
4. Open the File Explorer on your host machine and go to the installation path.
5. Open the folder with the name of your Virtual Machine, say, Ubuntu Hyper-V. Then, open the Virtual Machines folder. You will see the GUID there. Note down that GUID.

Now, open the Task Manager and follow the steps described above to kill the vmwp.exe process with that GUID. After killing the vmwp.exe process, launch the VM again and see if it loads this time or gets stuck on the Starting State.

2] Restart all Hyper-V Services

When you start your system, several Windows and third-party services also start automatically and keep running in the background. These services handle different tasks on your computer. There are certain Services that belong to Hyper-V Manager. These Services are responsible for the proper functioning of Hyper-V. If Hyper-V is freezing or gets stuck in Starting State, you should check the status of Hyper-V Services. If any of these Services is stopped, start it. If all the Services are already running, restart them.

Open the Services app and locate the Services that belong to Hyper-V. Right-click on them and select Restart (if they are already running) and select Start (if they are stopped).

3] Add vmwp.exe as an exception to your antivirus

As described above in this article, your antivirus may also prevent Hyper-V VM from starting. To check this, disable your antivirus temporarily and then check if the issue persists. If the VM starts after disabling the antivirus, your antivirus is blocking the vmwp.exe, which is a necessary process for Hyper-V Virtual Machine. To resolve this problem, add the vmwp.exe file to your antivirus as an exception.

Some affected users have confirmed that the issue was fixed after adding the vmwp.exe file to their antivirus excluding list. If you use Windows Security, you can easily exclude programs or files from Windows Security. If you have a third-party antivirus, contact their support person to know how to do that.

Read: Virtual machine could not initiate a checkpoint operation

4] Miscellaneous fixes

Let’s consider you receive an error message after some time. You may encounter any error message, for example:

The application encountered an error while attempting to change the state of Virtual Machine.
‘The system cannot find the file specified.’

From the above error message, it is clear that the system is not able to find the file specified. Such an error occurs if you have installed an operating system on Hyper-V by using an ISO and deleted that ISO after installing the operating system. To check this, open the Settings of your Virtual Machine in Hyper-V and expand the SCSI Controller branch and select DVD Drive. Now, check if there is an image file path mentioned on the right side. If yes, the ISO should exist on that path. If you have deleted the ISO file, select None in DVD Drive.

If the issue occurs due to the Network Adapter, you will see the Configuration Error message under the Network Adapter branch in your Virtual Machine settings. In this case, you must configure your Network Adapter in Hyper-V VM settings.

Read: Not enough memory in the system to start the virtual machine.

How do I force quit Hyper-V?

To force quit Hyper-V, you have to end the vmwp.exe process running in the background. You can do this via the Task Manager. The vmwp.exe process is one of the crucial processes required by Hyper-V. If you kill this process, it will result in force quit Hyper-V.

If you have installed multiple Virtual Machines on Hyper-V, you may find multiple instances of the vmwp.exe process in the Task Manager. In this case, you should know the correct GUID of the problematic Virtual Machine to force quit it. We have already talked about how to identify the GUID of a Virtual Machine earlier in this article.

TIP: This post will help you if you can’t connect to Hyper-V Virtual Machine.

How do I stop VMMS Service?

VMMS is the Virtual Machine Management Service. You can stop it via the Services Manager app or MSConfig. Open the Services Manager app and locate the Hyper-V Virtual Machine Management Service. Once you find it, right-click on it and select Stop.

If you use the MSConfig for the same, go to the Services tab and uncheck the Hyper-V Virtual Machine Management. After that, click Apply and then click OK. You have to restart your computer for the changes to take effect.

I hope this helps.

Read next:

•  Hyper-V Virtual Machine stuck in Saved State
• Hyper-V Virtual Machine stuck in Stopping State.

Если ваша виртуальная машина, запущенная на хосте Hyper-V зависла по каким-то причинам, перестала отвечать, и не реагирует на кнопки включения, выключения, перезагрузки в консоли Hyper-V Manager, единственный быстрый способ принудительно остановить такую машину — завершить процесс этой ВМ в хостовой ОС. Вы можете принудительно перезапустить конкретную ВМ в Hyper-V на Windows Server 2022/2019/2016 (или бесплатного Hyper-V Server) без перезагрузки всего сервера и запущенных на нем виртуальных машин (полезно, если у вас нет HA кластера Hyper-V и Live-Migration).

Виртуальная машина Hyper-V зависла в статусе Stopping или Starting

Администраторы Hyper-V периодически сталкиваются с ситуациями, когда что одна из ВМ на хосте Hyper-V зависает в состоянии Stopping (Stopping-Critical), Starting (Starting 10%) или Backing up.

При этом гостевая ОС перестаёт отвечать, и кнопки “Turn Off”,” Shut Down” и” Reset” вв консоли Hyper-V Manager становиться недоступны или при нажатии возвращают ошибку:

Failed to change state
The operation cannot be performed while the object is in its current state

Если ваш хост Hyper-V не показывает список зарегистрированных виртуальных машин в консоли Hyper-V Manager и возвращает ошибку “Connecting to Virtual Machine Management service”, вам нужно перезапустить процесс vmms.exe (служба Hyper-V Virtual Machine Management). Это безопасная операция, которая не прервет работу запушенных виртуальных машин. Проще всего перезапустить процесс службы vmms через консоль
services.msc
или PowerShell командой:

Get-Service vmms | Restart-Service

Как завершите процесс зависшей виртуальной машины Hyper-V?

Чтобы принудительно выключить/ перезапустить зависшую виртуальную машину без перезагрузки всего хостового сервера Hyper-V, нужно завершить ее рабочий процесс на гостевой ОС. Все ВМ на хосте Hyper-V запускаются с помощью процесса vmwp.exe (Virtual Machine Worker Process). Для поиска конкретного PID процесса нужно узнать GUID виртуальной машины.

Вы можете найти GUID ВМ в консоли управления Hyper-V Manager. Откройте настройки сервера (Hyper-V Settings). В разделе Server указан каталог, в котором хранятся конфигурационные файлов ВМ (в нашем примере D:\VMStore).

Откройте этот каталог в File Explorer и найдите каталог с именем зависшей виртуальной машины. Скопируйте GUID, который указан в имени конфигурационного файла ВМ с расширением *.vmcx.

Теперь нужно запустить диспетчер задач (Task Manager) и перейти на вкладку Details. Все виртуальные машины запускаются в рамках собственного экземпляра процесса vmwp.exe. Чтобы определить какой процесс за какую ВМ отвечает, нам нужен полученный ранее GUID зависшей ВМ. Найдите процесс vmwp.exe, у которого в столбце User name содржится GUID вашей ВМ. Завершите данный процесс (End Task).

По аналогии вы можете найти и завершить процесс подвисшей виртуальной машины на хосте Hyper-V с помощью утилиты Process Explorer.

1. Запустите Process Explorer с правами администратора и нажмите Find Handle or DLL (или нажмите Ctrl-F );
2. В строке поиска укажите путь к виртуальному диску зависшей виртуальной машину (*.vhdx);
3. Process Explorer выведет все процессы, которые используются VHDX файл виртуальной машины;
4. Найдите процесс виртуальной машину vmwp.exe и завершите его.

Виртуальная машина будет принудительно остановлена. Теперь вы сможете делать с ней все что угодно.

Выключить зависшую ВМ на Hyper-V с помощью PowerShell

Гораздо проще найти и завершить процесс зависшей виртуальной машины с помощью PowerShell. Запустите консоль PowerShell с правами администратора (учетная запись должна состоять в локальной группе Hyper-V administrators).

Вы также можете завершить процесс ВМ по ее VM ID. Можно получить GUID ВМ по ее имени. Например, для ВМ с именем SVM-GUARDEDHOST1, выполните команду:

$VMGUID = (Get-VM "SVM-GUARDEDHOST1").ID

Скопируйте VMID нужной вам ВМ из полученного списка.

Теперь нужно найти идентификатор процесса (PID) ‘vmwp.exe’ для вашего VMGUID:

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

Затем нужно принудительно завершить рабочий процесс подвисшей виртуальной машины Hyper-V с помощью команды Stop-Process:

Stop-Process ($VMWMProc.ProcessId) –Force

Виртуальная машина Hyper-V зависает при резервном копировании

При выполнении резервного копирования ВМ на хосте Hyper-V вы можете столкнуться с зависанием виртуальной машины Hyper-V в состоянии Running и статусом Backing up. При этом вы не можете остановить или запустить ВМ через Hyper-V Manager.

Если вы не хотите перезагружать хост Hyper-V, проверьте сначала состояние службу «Microsoft Hyper-V VSS Writer»:

vssadmin list writers

Убедитесь, что команда не вернула ошибку. Значит нужно перезапустить службу «Hyper-V Virtual Machine Management» с помощью команды PowerShell:

Get-service vmms | stop-process 

Убедитесь, что процесс vmms.exe завершен. Если нет, завершите его принудительно:

Get-Process | Where-Object { $_.ProcessName -eq 'vmms' } | Stop-Process

Теперь можно запустить службу Hyper-V:

Start-Service vmms 

Перезапуск службы Virtual Machine Management должно сбросить состояние VSS Writer для Hyper-V.

Hyper-V: Не удалось изменить состояние виртуальной машины

Иногда бывает, что даже после завершения зависшего процесса вы не можете включить ВМ и она зависает в статусе Starting с ошибкой:

Virtual Machine Connection
Не удалось изменить состояние.
Failed to Change State.

В этом случае проверьте следующие варианты:

• Проверьте что на диске, на котором хранятся файлы ВМ достаточно свободного места;
• Если в настройках ВМ подключен ISO образ, проверьте этот файл доступен;
• Проверьте сетевые настройки ВМ. Виртуальные сетевые адаптеры должны быть подключены к существующему виртуальному коммутатору Hyper-V (не должно быть статуса Network Adapter – Configuration Error);
• Проверьте, что служба Hyper-V Virtual Management Service (VMMS) запушена, и не зависла в статусе Stopping;
• Убедитесь, что ваш антивирус не блокирует доступ к файлам ВМ. Добавьте пути к каталогу с виртуальными машинами в исключения антивируса ( см. как добавить исключения во встроенный антивирус Windows Defender в Windows Server);
• Проверьте ошибки в журнале событий Event Viewer -> Applications and Services Logs -> Microsoft -> Windows -> Hyper-V-Worker;
• Отключите режим сна и гибернации в гостевых операционных системах виртуальных машин. В Windows спящий режим отключается через Control Panel –>Power Options -> Change plan settings -> Put the computer to sleep -> Never. Чтобы отключить спящий режим в гостевой ОС с Ubuntu Linux, выполните команду:
  systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

Если методы, описанные выше, не помогли, похоже, что вам придется перезагрузить весь хост Hyper-V.