The aim of this article is to create a slowly growing cheat-sheet of Hyper-V Errors and known fixes.
Errors without Error Codes
These errors are UI errors that do not provide a Hex Error Code / Win32 Error Code.
There was an error during move operation.
Migration operation on ‘<VM Name>’ failed. |
See:
|
There was an error during move operation.
Virtual machine migration operation failed at migration source. Failed to create folder. |
See 0x80070005 |
Errors with Error Codes
The following errors have error codes either stated on GUI error messages, as part of PowerShell error messages or in the Hyper-V event logs in Event Viewer.
0x80004005
Event ID: 21002 & 16300 & 1106 |
‘<Virtual Machine Name>’ Failed to create Planned Virtual Machine at migration destination: Unspecified error (0x80004005). (Virtual machine ID <Virtual Machine GUID>)
Cannot load a virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID <Virtual Machine GUID>) vm\service\migration\vmmsvmmigrationdestinationtask.cpp(1781)\vmms.exe!00007FF650130A43: (caller: 00007FF65013359D) Exception(312) tid(19b4) 80004005 Unspecified error vm\service\vmmgr\vmmsvirtualmachinemanager.cpp(4128)\vmms.exe!00007FF64FC867EB: (caller: 00007FF64FD83CC0) LogHr(97) tid(19b4) 80004005 Unspecified error Note: The Memory ranges, process ID’s and exception codes do not need to match the above, just the presence of 80004005.
|
0x8000FFFF
Event ID: |
Virtual machine failed to generate VHD tree: ‘Catastrophic failure'(‘0x8000FFFF’).
|
0x80041024
Event ID: 16000 |
The Hyper-V Virtual Machine Management service encountered an unexpected error: Provider is not capable of the attempted operation (0x80041024).
|
0x80070002 | Could not create backup checkpoint for virtual machine ‘<VM Name>’: The system cannot find the file specified. (0x80070002). (Virtual machine ID <VM GUID>).
For more on this, seem my in-depth article.
|
0x80070003
Event ID: |
Hyper-V Replication could not be enabled
|
0x80070005 | ‘General access denied error'(‘0x80070005’)
For more on this, see my in-depth article.
|
0x80070057 | vm\service\vmmgr\vmmsvirtualmachineobject.cpp(8731)\vmms.exe!00007FF64FDCB0D0: (caller: 00007FF65028C7DA) ReturnHr(110) tid(19b4) 80070057 The parameter is incorrect. Msg:[vm\service\vmmgr\vmmsvirtualmachineobject.cpp(8725)\vmms.exe!00007FF64FE3C560: (caller: 00007FF65028C7DA) Exception(306) tid(19b4) 80070057 The parameter is incorrect. ]Note: The Memory ranges, process ID’s and exception codes do not need to match
|
0x8007274C
Event ID: 20306 |
The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host ‘<Hypervisor FQDN>’: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (0x8007274C).
|
0x8007274D
Event ID: 20306 |
The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host ‘<hostname>’: No connection could be made because the target machine actively refused it. (0x8007274D).
|
0x8009030C
Event ID: 20302, 20306 |
Attempting to Live Migrate a VM between two servers from a third management workstation results in:
The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: The logon attempt failed (0x8009030C). The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host ‘<hostname>’: The logon attempt failed (0x8009030C). Live Migration worked previously and Kerberos Constrained Delegation is verified as being correctly setup on the Domain Controller. Port 6600 is correctly servicing on both Hyper-V peers on the correct IP interface. If you enable Kerberos Ticket Auditing on your domain controllers you receive Event ID 4769 with a failure code of 0x29: A Kerberos service ticket was requested. Account Information: Service Information: Network Information: Additional Information: Error Code 0x29 or error KRB_AP_ERR_MODIFIED means that the Kerberos message checksum failed and the message is suspected of being modified in transit as a result of the checksum mismatch. Possible ‘natural’ explanations for this include:
In this case it is likely that it is being caused by a bug in the Kerberos Service on Windows Server Domain Controllers as identified in an emergency out-of-bound patch release on 14th November 2021 for Windows Server 2008 R1 and higher. View: Windows Message Centre Announcement “Take action: Out-of-band update to address authentication issues on DCs relating to Kerberos delegation scenarios Microsoft is releasing Out-of-band (OOB) updates today, November 14, 2021, to resolve issues in which authentication might fail on DCs with certain Kerberos delegation scenarios on all supported versions of Windows Server when used as a Domain Controller. To get the standalone update package, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note These updates are not available from Windows Update and will not install automatically.” You need to patch your Domain Controllers (not the Hypervisors) with the following KB’s and restart them to fix the problem: |