Windows 8

  1. The Virtual Machine Management Service could not send messages with the Synth3D VSP driver. This server cannot run as a RemoteFX ...
  2. The Virtual Machine Management Service could not start the RemoteFX Manager process to enable RemoteFX for the virtual machine ...
  3. The Virtual Machine Management Service denied a request for a Virtual Machine migration at the destination host: %1 (%2). ...
  4. The Virtual Machine Management Service disabled the listen networks for Virtual Machine migrations after a failed configuration ...
  5. The Virtual Machine Management Service disabled the live migration connection listener because no cluster networks are available ...
  6. The Virtual Machine Management Service failed the request for a Virtual Machine migration at the destination host because ...
  7. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the destination ...
  8. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source ...
  9. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source ...
  10. The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source ...
  11. The Virtual Machine Management Service failed to configure the network listeners for Virtual Machine migrations: %1 (%2). ...
  12. The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration because the destination ...
  13. The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration because the destination ...
  14. The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host '%3': %1 ...
  15. The Virtual Machine Management Service failed to forcibly stop the virtual machine: %1 (%2). Check the virtual machine for ...
  16. The Virtual Machine Management Service failed to initiate a live migration on the target node. A worker process is already ...
  17. The Virtual Machine Management Service failed to read metrics information from the configuration for one or more metric values: ...
  18. The Virtual Machine Management Service failed to register the configuration for the virtual machine '%3' at '%4': %1 (%2). ...
  19. The Virtual Machine Management Service failed to setup a live migration connection for Virtual Machine %3 (client %4): %1 ...
  20. The Virtual Machine Management Service failed to setup the listen socket for Virtual Machine migration connections for address ...
  21. The Virtual Machine Management Service failed to start the virtual machine '%1' because one of the Hyper-V components is ...
  22. The Virtual Machine Management Service failed to start the virtual machine '%1' because the system is in safe mode (Virtual ...
  23. The Virtual Machine Management Service failed to verify that the configuration is registered for the virtual machine '%3': ...
  24. The Virtual Machine Management Service failed to write metrics information to the configuration for one or more metric value: ...
  25. The Virtual Machine Management service found an invalid value configured for the TCP listener port in the registry. The default ...
  26. The Virtual Machine Management service found an invalid value configured for the TCP listener port in the registry. The TCP ...
  27. The Virtual Machine Management service found an invalid value of zero configured for the TCP listener port in the registry. ...
  28. The Virtual Machine Management service has lost its connection to the %3 WMI namespace: %1 (%2). As a result, some WMI operations ...
  29. The Virtual Machine Management service initiated the live migration of virtual machine '%1' to destination host '%3' (VMID ...
  30. The Virtual Machine Management service initiated the offline migration of virtual machine '%1' to destination host '%3' (VMID ...
  31. The Virtual Machine Management Service rejected the request for a live migration for Virtual Machine %1 because of an unsupported ...
  32. The Virtual Machine Management Service rejected the request for a live migration for virtual machine %1 because RemoteFX ...
  33. The Virtual Machine Management Service restarted the live migration connection listener thread using the following addresses: ...
  34. The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following ...
  35. The Virtual Machine Management service successfully completed the live migration of virtual machine '%1' (VMID %2), received ...
  36. The Virtual Machine Management service successfully completed the live migration of virtual machine '%1' with a blackout ...
  37. The Virtual Machine Management service successfully completed the live migration of virtual machine '%1' with an unexpectedly ...
  38. The Virtual Machine Management service successfully completed the offline migration of virtual machine '%1' (VMID %2), received ...
  39. The virtual machine named %1 could not be started because the GPU it was previously running on could not be found. If you ...
  40. The virtual machine on specified Replica server is not in valid state for receiving replication. To use a restored copy of ...
  41. The virtual machine requires network switches and the new cluster does not have any virtual network switches configured. ...
  42. The virtual machine state is not valid. The virtual machine should not be in a running state while being added to the collection. ...
  43. The Virtual Machine Worker Process has lost its connection to the %3 WMI namespace: %1 (%2). As a result, some WMI operations ...
  44. The virtual machine you have selected to recover to an alternate location was backed up from this hyper-v host. Recovery ...
  45. The virtual machine {0} can not shutdown while it is locked, unless the shutdown is forced. Forcing a shutdown can result ...
  46. The virtual machine {0} is using certificate based authentication. A new certificate needs to be specified for reversing ...
  47. The virtual machine {0} on node {1} could not be shut down in a timely fashion. The virtual machine could just be taking ...
  48. The virtual machine {0} on node {1} could not be shut down. Verify that integration services have been installed on the virtual ...
  49. The virtual machines might not start if their network settings are different after recovery. Use Hyper-V Manager to verify ...
  50. The virtual machines might not start if their network settings have changed. After recovery is complete use Hyper-V Manager ...
  51. The virtual switch '%1' cannot be deleted because it is being used by running virtual machines or assigned to child pools. ...
  52. The virtual switch '%1' cannot be removed from resource pool '%2' because it is being used by running virtual machines or ...
  53. The virtual switch cannot be bound to the WiFi adapter because the network bridge is already in use. You can configure at ...
  54. The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the ...
  55. The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the ...
  56. The VM has been live migrated with missing LUNs for virtual HBA %3 (%4) due to the VM setting to allow reduced FC redundancy. ...
  57. The volume %s is currently in use. If you continue, the drive letter will be freed; however, it will still be available for ...
  58. The volume %s is currently in use. If you continue, the new drive letter will be assigned, but you can still use the old ...
  59. The volume %s is currently in use. To force the deletion of this volume, click Yes. WARNING: Forcing a deletion might cause ...
  60. The volume %s is currently in use. To force the format of this volume, click Yes. WARNING: Forcing a format might cause unexpected ...
  61. The volume %s is currently in use. To forcibly extend this volume, click Yes. WARNING: Forcibly extending a volume might ...
  62. The volume %s is too small to contain a storage area. Please click the Settings button and pick a storage area location before ...
  63. The volume cannot be extended because another volume is located immediately after this volume on the disk. To extend the ...
  64. The volume cannot be extended because it resides on a dynamic disk. To extend a volume that resides on a dynamic disk, use ...
  65. The volume cannot be extended because the number of clusters will exceed the maximum number of clusters supported by the ...
  66. The volume containing boot critical files is not formatted with a supported filesystem. Bare metal recovery is not supported ...
  67. The volume containing sysvol share has only %d bytes free for policy to use. Please free space (above 5MB) in order for policy ...
  68. The volume could not be extended because it is encrypted by BitLocker and Fveapi.dll could not be loaded to determine its ...
  69. The volume could not be extended because it is locked due to a BitLocker error. Use BitLocker tools to recover the volume ...
  70. The volume could not be extended because it is marked for BitLocker recovery. Use BitLocker tools to recover the volume and ...
  71. The volume could not be shrunk because it is encrypted by BitLocker and Fveapi.dll could not be loaded to determine its status. ...
  72. The volume could not be shrunk because it is locked due to a BitLocker error. Use BitLocker tools to recover the volume and ...
  73. The volume could not be shrunk because it is marked for BitLocker recovery. Use BitLocker tools to recover the volume and ...
  74. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and ...
  75. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and ...