Windows 8.1
- Hyper-V Data Exchange connected to virtual machine '%1', but the version does not match the version expected by Hyper-V (Virtual ...
- Hyper-V Data Exchange failed to connect to virtual machine '%1' because the version does not match the version expected by ...
- Hyper-V did not allow the operation for virtual machine '%1' because resynchronization is in progress. Cancel resynchronization ...
- Hyper-V did not allow the operation for virtual machine '%1' because test failover is enabled. Stop test failover and try ...
- Hyper-V did not allow the operation for virtual machine '%1' because undo log configuration could not be deleted. (Virtual ...
- Hyper-V did not automatically start resynchronization because the current time is outside the window specified by the AutoResynchronizeIntervalStart ...
- Hyper-V did not automatically start resynchronization on '%1' because the AutoResynchronizeEnabled setting was set to FALSE. ...
- Hyper-V did not automatically start resynchronization on '%1' because the current time is outside the window specified by ...
- Hyper-V encountered an error trying to access an object on computer '{0}' because the object was not found. The object might ...
- Hyper-V encountered an error trying to access an object on computer '{0}' because the object was not found. The object might ...
- Hyper-V failed the request for network connection at the destination host because the requested source protocol version (%1) ...
- Hyper-V failed to add the port '%3' to the Windows Server Hardening firewall rule. Error: %1 (%2). The currently allowed ...
- Hyper-V failed to apply changes on target for virtual machine '%1'. Possible reasons are loss of network connection with ...
- Hyper-V failed to bind the digital certificate on the server because an existing digital certificate is already bound on ...
- Hyper-V failed to bind the digital certificate on the server because another certificate was bound in the same server and ...
- Hyper-V failed to delete checkpoint '%3' for virtual machine '%1'. (Virtual machine ID %2). Checkpoint deletion will be retried ...
- Hyper-V failed to establish a connection to the Replica server (%3) because the network protocol version (%1) is not compatible ...
- Hyper-V failed to establish connection with Replica server because the primary server certificate is not valid on the Replica ...
- Hyper-V failed to establish connection with Replica server because the primary server certificate is not valid on the Replica ...
- Hyper-V failed to fail over to the selected recovery point for '%1': %3 Try a more recent recovery point. (%4). (Virtual ...
- Hyper-V failed to find a matching certificate in Personal Certificate Store of Local Computer which can be used for Client ...
- Hyper-V failed to generate VSS snapshot set for virtual machine '%1': %3 (%4). VSS snapshot set generation can fail if backup ...
- Hyper-V failed to open the file '%5' for replication in primary server for virtual machine '%1': %3 (%4). (Virtual machine ...
- Hyper-V failed to replicate changes for virtual machine '%1' (Virtual machine ID %2). Hyper-V will retry replication after ...
- Hyper-V failed to replicate changes for virtual machine '%1' (Virtual machine ID %2). Hyper-V will retry replication after ...
- Hyper-V failed to replicate changes for virtual machine '%1' because too many logs are pending on the Replica server. Hyper-V ...
- Hyper-V failed to retrieve Data Exchange Integration service items for virtual machine '%1': %3 (%4). (Virtual machine ID ...
- Hyper-V failed to revert VSS snapshot set for virtual machine '%1' during failover. Failover proceeded without reverting ...
- Hyper-V failed to revert VSS snapshot set for virtual machine '%1' during test failover. Test failover proceeded without ...
- Hyper-V failed to shut down the virtual machine. This occurs when the virtual machine does not support shutdown. For example, ...
- Hyper-V failed to start the virtual machine '%1' because it was unable to determine if replication was configured for this ...
- Hyper-V Guest Service Interface connected to virtual machine '%1' is using the most recent version (Virtual machine ID %2). ...
- Hyper-V Guest Service Interface connected to virtual machine '%1', but the version does not match the version expected by ...
- Hyper-V Guest Service Interface failed to connect to virtual machine '%1' because the version does not match the version ...
- Hyper-V Guest Shutdown connected to virtual machine '%1', but the version does not match the version expected by Hyper-V ...
- Hyper-V Guest Shutdown failed to connect to virtual machine '%1' because the version does not match the version expected ...
- Hyper-V Heartbeat connected to virtual machine '%1', but the version does not match the version expected by Hyper-V (Virtual ...
- Hyper-V Heartbeat failed to connect to virtual machine '%1' because the version does not match the version expected by Hyper-V ...
- Hyper-V logical processor %2 exposes the following power management capabilities: Idle state type: %4 (%3 state(s)) Performance ...
- Hyper-V management tools were not found on the system. Creation and management of Virtual Machines will be disabled in Failover ...
- Hyper-V paused virtual machine '%1' because the Replica virtual machine was found to be failed over on the Replica server. ...
- Hyper-V PowerShell tools are not installed on '{0}' to Windows. Refer to the product troubleshooting documentation or contact ...
- Hyper-V prevented starting the virtual machine because replication is ongoing. The virtual machine can be started after performing ...
- Hyper-V prevented starting virtual machine '%1' because it is prepared for planned failover. Virtual machine can be started ...
- Hyper-V prevented starting virtual machine '%1' because replication is ongoing. Virtual machine can be started after performing ...
- Hyper-V prevented starting virtual machine '%1' because test failover is in progress. Virtual machine can be started after ...
- Hyper-V prevented starting virtual machine '{0}' because replication is ongoing. The virtual machine can be started after ...
- Hyper-V provides the services that you can use to create and manage virtual machines and their resources. Each virtual machine ...
- Hyper-V Rdv Transport Service connected to virtual machine '%1' is using the most recent version (Virtual machine ID %2). ...
- Hyper-V Rdv Transport Service connected to virtual machine '%1', but the version does not match the version expected by Hyper-V ...
- Hyper-V Rdv Transport Service failed to connect to virtual machine '%1' because the version does not match the version expected ...
- Hyper-V Replica Broker enables the failover cluster to participate in virtual machine replication with Hyper-V Replica. Only ...
- Hyper-V Replica Broker is not configured for virtual machine '%1'. Configure Hyper-V Replica Broker using Failover Cluster ...
- Hyper-v Replica could not read replication statistics for virtual machine '%1' as configuration is corrupt: %3 (%4).(Virtual ...
- Hyper-V Replica failed to apply the log file onto the VHD for virtual machine '%1'. (Virtual machine ID %2) (Log File %5) ...
- Hyper-V Replica failed to apply the log file onto the VHD for virtual machine '%1'. (Virtual machine ID %2) (VHD %5) - Error: ...
- Hyper-V Replica failed to apply the log file onto the VHD for virtual machine '%1'. (Virtual machine ID %2) (VHD %5). An ...
- Hyper-V Replica failed to apply the log file onto the VHD for virtual machine '%1'. (Virtual machine ID %2). An out-of-bounds ...
- Hyper-V Replica failed to disable change tracking for virtual machine '%1'. (Virtual machine ID %2) (VHD ID %5) - Error: ...
- Hyper-V Replica failed to enable change tracking for virtual machine '%1'. (Virtual machine ID %2) (VHD ID %5) - Error: %3 ...
- Hyper-V Replica failed to perform the operation. Virtual machine is not in a valid replication state to perform the operation. ...
- Hyper-V Replica failed to process configuration disconnected event for virtual machine '%1': %3 (%4). (Virtual machine ID ...
- Hyper-V Replica failed to process configuration reconnected event for virtual machine '%1': %3 (%4). (Virtual machine ID ...
- Hyper-V Replica failed to query change tracking for virtual machine '%1'. (Virtual machine ID %2) (VHD ID %5) - Error: %3 ...
- Hyper-V Replica failed to switch the log file for change tracking for virtual machine '%1'. (Virtual machine ID %2) - Error: ...
- Hyper-V Replica settings are saved but cannot be applied. Check the settings and try again. Hyper-V Replica failed to process ...
- Hyper-V Replica starts network listeners for replication. These require firewall rules to be enabled for the ports that are ...
- Hyper-V Replica starts network listeners on the ports assigned for replication. On some of the servers, the listeners are ...
- Hyper-V Role is not added on '{0}' to Windows. Refer to the product troubleshooting documentation or contact Microsoft Customer ...
- Hyper-V Server can only be installed on a partition with NTFS formatting. You can reformat or use convert.exe to change this ...
- Hyper-V Server won't install unless each of these things is taken care of. Close Setup, take care of each one, and then restart ...
- Hyper-V Setup: Post-install configuration task could not complete because one or more Hyper-V components are not available. ...
- Hyper-V suspended replication for virtual machine '%1' due to a non-recoverable failure. Resume replication after correcting ...
- Hyper-V Time Synchronization connected to virtual machine '%1' is using the most recent version (Virtual machine ID %2). ...
- Hyper-V Time Synchronization connected to virtual machine '%1', but the version does not match the version expected by Hyper-V ...