Hyper-V Virtual Machines Stuck Starting at 10%

Peel, Andrew 1 Reputation point
2020-11-27T13:55:16.127+00:00

Since today I have been unable to start my existing (or new) Hyper-V virtual machines on my Windows 10 Enterprise (v1909) device. The error message is "The application encountered an error while attempting to change the state of '<vmmachinename>' and as shown in the image below ![43333-image.png][1] In the Hyper-V-Worker Admin Event Viewer log, I get a Event 3062 error message stating that the "Virtual Machine Worker Process initialization has timed out, and will terminate". This appears to happen when any VM machine reaches 10% of starting. ![43315-image.png][2] In the Event Viewer there are also errors with restoring the configuration for ports with the Hyper-V VmSwitch that occur on device startup. These errors have only started today after installation of the Intel Management Engine - Firmware update. ![43263-image.png][3] Whilst this may be coincidental, the only thing I believe has changed on the machine (Lenovo ThinkPad L590) is that the BIOS and Intel Management Engine - Firmware have been upgraded. The BIOS was upgraded from 1.22 to 1.23 (subsequently reverted) and the Intel Management Engine - Firmware upgraded from 12.0.68.1606 to 12.0.70.1652. Unfortunately there appears no way to downgrade the Intel Management Engine - Firmware to test this theory. I have local administrative rights on my device and to reiterate this has been working. I have already tried removing and reinstalling the Hyper-V components within Windows 10 but this has not resolved the issue. Any assistance on how to resolve or troubleshoot this issue further will be most appreciated. Thank you. [1]: /api/attachments/43333-image.png?platform=QnA [2]: /api/attachments/43315-image.png?platform=QnA [3]: /api/attachments/43263-image.png?platform=QnA

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,618 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,538 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Peel, Andrew 1 Reputation point
    2020-11-28T11:49:11.87+00:00

    Thanks to https://social.technet.microsoft.com/Forums/en-US/2a471fa7-0dad-4aef-9c95-cb09e270c9d8/virtual-machine-failed-to-start-error-in-hyperv the problem has been fixed. In Device Manager a number of Hyper-V components were missing that had to be manually installed using the "Add legacy hardware" option. You need to ensure that the following four components are installed: - Microsoft Hyper-V PCI Server - Microsoft Hyper-V Virtual Disk Server - Microsoft Hyper-V Virtual Machine Bus Provider - Microsoft Hyper-V Virtualization Infrastructure Driver ![43369-image.png][1] [1]: /api/attachments/43369-image.png?platform=QnA

  2. Peel, Andrew 1 Reputation point
    2020-12-26T19:57:02.197+00:00

    The root cause of the issue was “Authenticated Users” being in the local administrators group. Removing “Authenticated Users” from the local administrators group resolved the issue.

    0 comments