Windows 8

  1. Hyper-V could not enable test failover for virtual machine '%1' because a test failover virtual machine is already present. ...
  2. Hyper-V could not find a digital certificate with thumbprint '%3' in the Trusted Root certificate store of local computer. ...
  3. Hyper-V could not find a matching certificate in Personal certificate store of local computer which can be used for Server ...
  4. Hyper-V could not find a matching certificate required for Client Authentication. Install a certificate which is not expired, ...
  5. Hyper-V could not find a matching certificate required for Server Authentication. Install a certificate which is not expired ...
  6. Hyper-V could not find snapshot (Snapshot ID '%3') for virtual machine '%1'. This could lead to replication errors. (Virtual ...
  7. Hyper-V could not find the configured certificate with the thumbprint '%3' in the Personal store of the local computer. Error: ...
  8. Hyper-V could not find the virtual machine '%1' on the Replica server and will connect to the Hyper-V Replica Broker in the ...
  9. Hyper-V could not replicate changes for virtual machine '%1' as Hyper-V is not in a state to accept replication on the Replica ...
  10. Hyper-V could not replicate changes for virtual machine '%1' as replication is suspended on the Replica server. (Virtual ...
  11. Hyper-V could not replicate changes for virtual machine '%1' because the operation was cancelled. (Virtual machine ID %2) ...
  12. Hyper-V could not replicate changes for virtual machine '%1' because the Replica server refused the connection. This may ...
  13. Hyper-V could not replicate changes for virtual machine '%1' because the virtual machine was not found on the Replica server. ...
  14. Hyper-V could not replicate changes for virtual machine '%1' because virtual machine migration is in progress on the Replica ...
  15. Hyper-V could not replicate changes for virtual machine '%1' because virtual machine migration is in progress. (Virtual machine ...
  16. Hyper-V could not replicate changes for virtual machine '%1'. (Virtual Machine ID %2). Replica virtual machine was found ...
  17. Hyper-V could not revert one or more volumes of the application-consistent snapshot set of Replica virtual machine '%1'. ...
  18. Hyper-V could not validate certificate with thumbprint '%3'. The certificate cannot be verified upto the trusted certification ...
  19. Hyper-V could not validate certificate with thumbprint '%3'. The Enhanced Key Usage should have both Client and Server Authentication. ...
  20. Hyper-V could not validate certificate with thumbprint '%3'. The Enhanced Key Usage should have Client Authentication. Error: ...
  21. Hyper-V could not validate certificate with thumbprint '%3'. The name '%4' is not present in the certificates subject common ...
  22. Hyper-V Data Exchange connected to virtual machine '%1', but the version does not match the version expected by Hyper-V (Virtual ...
  23. Hyper-V Data Exchange failed to connect to virtual machine '%1' because the version does not match the version expected by ...
  24. Hyper-V did not allow the operation for virtual machine '%1' because resynchronization is in progress. Cancel resynchronization ...
  25. Hyper-V did not allow the operation for virtual machine '%1' because test failover is enabled. Stop test failover and try ...
  26. Hyper-V did not automatically start resynchronization because the current time is outside the window specified by the AutoResynchronizeIntervalStart ...
  27. Hyper-V did not automatically start resynchronization on '%1' because the AutoResynchronizeEnabled setting was set to FALSE. ...
  28. Hyper-V did not automatically start resynchronization on '%1' because the current time is outside the window specified by ...
  29. Hyper-V encountered an error trying to access an object on computer '{0}' because the object was not found. The object might ...
  30. Hyper-V encountered an error trying to access an object on computer '{0}' because the object was not found. The object might ...
  31. Hyper-V failed the request for network connection at the destination host because the requested source protocol version (%1) ...
  32. Hyper-V failed to add the port '%3' to the Windows Server Hardening firewall rule. Error: %1 (%2). The currently allowed ...
  33. Hyper-V failed to apply changes on target for virtual machine '%1'. Possible reasons are loss of network connection with ...
  34. Hyper-V failed to bind the digital certificate on the server because an existing digital certificate is already bound on ...
  35. Hyper-V failed to bind the digital certificate on the server because another certificate was bound in the same server and ...
  36. Hyper-V failed to delete snapshot '%3' for virtual machine '%1'. (Virtual machine ID %2). Snapshot deletion will be retried ...
  37. Hyper-V failed to establish a connection to the Replica server (%3) because the network protocol version (%1) is not compatible ...
  38. Hyper-V failed to establish connection with Replica server because the primary server certificate is not valid on the Replica ...
  39. Hyper-V failed to establish connection with Replica server because the primary server certificate is not valid on the Replica ...
  40. Hyper-V failed to find a matching certificate in Personal Certificate Store of Local Computer which can be used for Client ...
  41. Hyper-V failed to generate VSS snapshot set for virtual machine '%1': %3 (%4). VSS snapshot set generation can fail if backup ...
  42. Hyper-V failed to open the file '%5' for replication in primary server for virtual machine '%1': %3 (%4). (Virtual Machine ...
  43. Hyper-V failed to replicate changes for virtual machine '%1' (Virtual Machine ID %2). Hyper-V will retry replication after ...
  44. Hyper-V failed to revert VSS snapshot set for virtual machine '%1' during failover. Failover proceeded without reverting ...
  45. Hyper-V failed to revert VSS snapshot set for virtual machine '%1' during test failover. Test failover proceeded without ...
  46. Hyper-V failed to shut down the virtual machine. This occurs when the virtual machine does not support shutdown. For example, ...
  47. Hyper-V failed to start the virtual machine '%1' because it was unable to determine if replication was configured for this ...
  48. Hyper-V Guest Shutdown connected to virtual machine '%1', but the version does not match the version expected by Hyper-V ...
  49. Hyper-V Guest Shutdown failed to connect to virtual machine '%1' because the version does not match the version expected ...
  50. Hyper-V Heartbeat connected to virtual machine '%1', but the version does not match the version expected by Hyper-V (Virtual ...
  51. Hyper-V Heartbeat failed to connect to virtual machine '%1' because the version does not match the version expected by Hyper-V ...
  52. Hyper-V logical processor %2 exposes the following power management capabilities: Idle state type: %4 (%3 state(s)) Performance ...
  53. Hyper-V management tools were not found on the system. Creation and management of Virtual Machines will be disabled in Failover ...
  54. Hyper-V paused virtual machine '%1' because the Replica virtual machine was found to be failed over on the Replica server. ...
  55. Hyper-V prevented starting the virtual machine because replication is ongoing. The virtual machine can be started after performing ...
  56. Hyper-V prevented starting virtual machine '%1' because it is prepared for planned failover. Virtual machine can be started ...
  57. Hyper-V prevented starting virtual machine '%1' because replication is ongoing. Virtual machine can be started after performing ...
  58. Hyper-V prevented starting virtual machine '{0}' because replication is ongoing. The virtual machine can be started after ...
  59. Hyper-V provides the services that you can use to create and manage virtual machines and their resources. Each virtual machine ...
  60. Hyper-V Rdv Transport Service connected to virtual machine '%1' is using the most recent version (Virtual machine ID %2). ...
  61. Hyper-V Rdv Transport Service connected to virtual machine '%1', but the version does not match the version expected by Hyper-V ...
  62. Hyper-V Rdv Transport Service failed to connect to virtual machine '%1' because the version does not match the version expected ...
  63. Hyper-V Replica Broker enables the failover cluster to participate in virtual machine replication with Hyper-V Replica. Only ...
  64. Hyper-V Replica Broker is not configured for virtual machine '%1'. Configure Hyper-V Replica Broker using Failover Cluster ...
  65. Hyper-v Replica could not read replication statistics for virtual machine '%1' as configuration is corrupt: %3 (%4).(Virtual ...
  66. Hyper-V Replica failed to apply the log file onto the VHD for virtual machine '%1'. (Virtual machine ID %2) (Log File %5) ...
  67. Hyper-V Replica failed to disable change tracking for virtual machine '%1'. (Virtual machine ID %2) (VHD ID %5) - Error: ...
  68. Hyper-V Replica failed to enable change tracking for virtual machine '%1'. (Virtual machine ID %2) (VHD ID %5) - Error: %3 ...
  69. Hyper-V Replica failed to perform the operation. Virtual machine is not in a valid replication state to perform the operation. ...
  70. Hyper-V Replica failed to process configuration disconnected event for virtual machine '%1': %3 (%4). (Virtual Machine ID ...
  71. Hyper-V Replica failed to process configuration reconnected event for virtual machine '%1': %3 (%4). (Virtual Machine ID ...
  72. Hyper-V Replica failed to query change tracking for virtual machine '%1'. (Virtual machine ID %2) (VHD ID %5) - Error: %3 ...
  73. Hyper-V Replica failed to switch the log file for change tracking for virtual machine '%1'. (Virtual machine ID %2) - Error: ...
  74. Hyper-V Replica settings are saved but cannot be applied. Check the settings and try again. Hyper-V Replica failed to process ...
  75. Hyper-V Replica starts network listeners for replication. These require firewall rules to be enabled for the ports that are ...