Windows 8.1

  1. The virtual machine at %1 cannot be imported because the version of the virtual machine %2 is not support by this version ...
  2. The virtual machine bus (VMBus) cannot start because the physical computer's PCI chipset does not properly support Message ...
  3. The virtual machine cannot be moved to a single location while it is using Smart Paging. You can either choose a move option ...
  4. The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible ...
  5. The virtual machine cannot be moved to the specified destination computer because that computer is not configured for live ...
  6. The virtual machine cannot be restored because the file rdvgm.exe that is required to start the RemoteFX Manager process ...
  7. The virtual machine cannot be started because all the RemoteFX-capable GPUs are disabled in Device Manager. You must enable ...
  8. The virtual machine cannot be started because all the RemoteFX-capable GPUs are disabled in Hyper-V Manager. You must enable ...
  9. The virtual machine cannot be started because the file rdvgm.exe that is required to start the RemoteFX Manager process does ...
  10. The virtual machine cannot be started because the Remote Desktop Virtualization Host (RD Virtualization Host) role service ...
  11. The virtual machine cannot be started because the server has insufficient GPU resources. If this issue persists, consider ...
  12. The virtual machine cannot be started because virtual machines that are configured with a 3D video adapter can only run on ...
  13. The virtual machine configuration resource '{0}' is not online. For best results, make sure that this resource is online ...
  14. The virtual machine could not be started because the GPU that it was previously using on the physical computer could not ...
  15. The virtual machine could not be started because the hypervisor is not running. The following actions may help you resolve ...
  16. The virtual machine could not communicate with the boot monitoring component of the Remote Desktop Virtualization Host Agent ...
  17. The virtual machine failed to communicate with the Remote Desktop Virtualization Host Agent service's boot monitoring component. ...
  18. The virtual machine for which you are trying to enable replication is not a clustered virtual machine in the failover cluster. ...
  19. The Virtual machine generation ID in the Active Directory database of this domain controller is different from the current ...
  20. The virtual machine is currently using the RemoteFX 3D video adapter. A user is currently connected via Remote Desktop. Connect ...
  21. The Virtual Machine Management Service (VMMS) is not running on node '{0}'. Before you can cluster virtual machines by using ...
  22. The Virtual Machine Management Service blocked a connection request for a Virtual Machine migration from client address '%3': ...
  23. The Virtual Machine Management Service could not find a certificate for the authentication of a migration connection: %1 ...
  24. The Virtual Machine Management Service could not register update notifications for the Integration Services Setup Disk image: ...
  25. The Virtual Machine Management Service could not send messages with the Synth3D VSP driver. This server cannot run as a RemoteFX ...
  26. The Virtual Machine Management Service could not start the RemoteFX Manager process to enable RemoteFX for the virtual machine ...
  27. The Virtual Machine Management Service denied a request for a Virtual Machine migration at the destination host because a ...
  28. The Virtual Machine Management Service denied a request for a Virtual Machine migration at the destination host: %1 (%2). ...
  29. The Virtual Machine Management Service disabled the listen networks for Virtual Machine migrations after a failed configuration ...
  30. The Virtual Machine Management Service disabled the live migration connection listener because no cluster networks are available ...
  31. The Virtual Machine Management Service failed the request for a Virtual Machine migration at the destination host because ...
  32. The Virtual Machine Management Service failed to authenticate a connection for a Virtual Machine migration with host '%1'. ...
  33. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the destination ...
  34. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source ...
  35. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source ...
  36. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source ...
  37. The Virtual Machine Management Service failed to configure the network listeners for Virtual Machine migrations: %1 (%2). ...
  38. The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration because the destination ...
  39. The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration because the destination ...
  40. The Virtual Machine Management Service failed to establish a connection for a virtual machine migration with host '%1' because ...
  41. The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host '%3': %1 ...
  42. The Virtual Machine Management Service failed to forcibly stop the virtual machine: %1 (%2). Check the virtual machine for ...
  43. The Virtual Machine Management Service failed to initiate a live migration on the target node. A worker process is already ...
  44. The Virtual Machine Management Service failed to register the configuration for the virtual machine '%3' at '%4': %1 (%2). ...
  45. The Virtual Machine Management Service failed to setup a live migration connection for Virtual Machine %3 (client %4): %1 ...
  46. The Virtual Machine Management Service failed to setup the listen socket for Virtual Machine migration connections for address ...
  47. The Virtual Machine Management Service failed to start the virtual machine '%1' because one of the Hyper-V components is ...
  48. The Virtual Machine Management Service failed to start the virtual machine '%1' because the system is in safe mode (Virtual ...
  49. The Virtual Machine Management Service failed to verify that the configuration is registered for the virtual machine '%3': ...
  50. The Virtual Machine Management service found an invalid value configured for the TCP listener port in the registry. The default ...
  51. The Virtual Machine Management service found an invalid value configured for the TCP listener port in the registry. The TCP ...
  52. The Virtual Machine Management service found an invalid value of zero configured for the TCP listener port in the registry. ...
  53. The Virtual Machine Management service has lost its connection to the %3 WMI namespace: %1 (%2). As a result, some WMI operations ...
  54. The Virtual Machine Management service initiated the live migration of virtual machine '%1' to destination host '%3' (VMID ...
  55. The Virtual Machine Management service initiated the offline migration of virtual machine '%1' to destination host '%3' (VMID ...
  56. The Virtual Machine Management Service rejected the request for a live migration for Virtual Machine %1 because of an unsupported ...
  57. The Virtual Machine Management Service rejected the request for a live migration for virtual machine %1 because RemoteFX ...
  58. The Virtual Machine Management Service restarted the live migration connection listener thread using the following addresses: ...
  59. The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following ...
  60. The Virtual Machine Management service successfully completed the live migration of virtual machine '%1' (VMID %2), received ...
  61. The Virtual Machine Management service successfully completed the live migration of virtual machine '%1' with a blackout ...
  62. The Virtual Machine Management service successfully completed the live migration of virtual machine '%1' with an unexpectedly ...
  63. The Virtual Machine Management service successfully completed the offline migration of virtual machine '%1' (VMID %2), received ...
  64. The Virtual Machine Management service successfully completed the storage migration of virtual machine '%1' (Virtual machine ...
  65. The virtual machine named %1 could not be started because the GPU it was previously running on could not be found. If you ...
  66. The virtual machine on specified Replica server is not in valid state for receiving replication. To use a restored copy of ...
  67. The virtual machine requires network switches and the new cluster does not have any virtual network switches configured. ...
  68. The virtual machine state is not valid. The virtual machine should not be in a running state while being added to the collection. ...
  69. The Virtual Machine Worker Process has lost its connection to the %3 WMI namespace: %1 (%2). As a result, some WMI operations ...
  70. The virtual machine you have selected to recover to an alternate location was backed up from this hyper-v host. Recovery ...
  71. The virtual machine {0} can not shutdown while it is locked, unless the shutdown is forced. Forcing a shutdown can result ...
  72. The virtual machine {0} is using certificate based authentication. A new certificate needs to be specified for reversing ...
  73. The virtual machine {0} on node {1} could not be shut down in a timely fashion. The virtual machine could just be taking ...
  74. The virtual machine {0} on node {1} could not be shut down. Verify that integration services have been installed on the virtual ...
  75. The virtual machines might not start if their network settings are different after recovery. Use Hyper-V Manager to verify ...