Windows 8

  1. The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration ...
  2. The version of the operating system on the computer named %1 is more recent than that on the local computer. This operation ...
  3. The version of the operating system on the computer named {0} is later than that on {1}. This operation is not available ...
  4. The version of virtual machine '%1' is not compatible with physical computer '%3'. To migrate this virtual machine, you must ...
  5. The version of wimgapi used to create this mount directory does not match the current version. Ensure that wimserv.exe, wimmount.sys ...
  6. The version of Windows Media Player that you are trying to install is the same as the currently installed version, except ...
  7. The version of Windows Media Player you are installing does not match the language of the currently installed Player. In ...
  8. The version of Windows PE running on this computer is not compatible with Setup. To install Windows from Windows PE, use ...
  9. The video adapter supports hardware 3D rendering, but it has been disabled. A software renderer will be used instead. This ...
  10. The video decoder is currently in use by another application. Close all other applications, restart Windows Media Center, ...
  11. The video decoder is not working, is not installed, or is not supported. Try installing the codec or restarting your computer. ...
  12. The video hardware does not have enough available memory to continue. Restart the computer and try again. If the problem ...
  13. The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it ...
  14. The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP. ...
  15. The viewer must close because it encountered an error from which it cannot recover. Restart the viewer and reopen your document. ...
  16. The virtual desktop cannot be added to the collection. Ensure that a SCSI controller is configured in the virtual desktop ...
  17. The virtual desktop cannot be cloned. Ensure that there is sufficient disk space and that the local storage path is valid. ...
  18. The virtual desktop cannot be joined to the domain because a computer with the same name already exists in the specified ...
  19. The virtual desktop cannot be migrated to the specified network location. Ensure that the network location has sufficient ...
  20. The virtual desktop collection type determines whether a user is assigned a temporary virtual desktop or if they are assigned ...
  21. The virtual desktop could not be joined to the domain because the maximum number of computer accounts allowed to join this ...
  22. The virtual desktop export location {0} is not available. Verify that the file share is available and that the RDS Endpoint ...
  23. The virtual desktop template cannot be copied from the virtual desktop location to the local cache. Ensure that the local ...
  24. The virtual desktop template export path {0} is either invalid or unreachable. Please make sure that the path is reachable ...
  25. The virtual desktop template is used to automatically create virtual desktops in a virtual desktop collection, and is copied ...
  26. The virtual desktops in the virtual desktop collection are being created. Depending on the size of the virtual desktop collection, ...
  27. The virtual disk is already open and cannot be opened a second time. Please close all clients that may have opened the virtual ...
  28. The virtual disks for the Replica virtual machine '%1' are not present on the Replica server (Virtual machine ID %2). Restore ...
  29. The virtual GPU synthetic device failed. If this error reoccurs frequently, consider reinstalling the RemoteFX virtual GPU. ...
  30. The virtual GPU synthetic devie failed. If this error reoccurs frequently, consider reinstalling the RemoteFX virtual GPU. ...
  31. The virtual hard disk could not be configured. Verify that there are no other virtual hard disks mounted, the virtual desktop ...
  32. The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk. ...
  33. The virtual machine %1 could not be started because the specified NUMA node list contains invalid NUMA Nodes. (Virtual Machine ...
  34. The Virtual machine %2 cannot be hot backed up since it has one or more volumes with differencing areas located on different ...
  35. The virtual machine '%1' cannot be backed up because either the file groups reported during OnIdentify has changed, or the ...
  36. The virtual machine '%1' cannot be backed up because it has incremental backup enabled and fibre channel disks connected ...
  37. The virtual machine '%1' cannot be backed up because it has incremental backup enabled and iSCSI disks connected to it. (Virtual ...
  38. The virtual machine '%1' cannot be backed up because it has incremental backup enabled and pass-through disks connected to ...
  39. The virtual machine '%1' cannot be backed up because it was stopped during backup. Try the backup again. (Virtual machine ...
  40. The virtual machine '%1' cannot start a backup operation because it is currently executing a conflicting operation. Try the ...
  41. The Virtual Machine '%1' failed to start because there is not enough disk space. The system was unable to create the memory ...
  42. The virtual machine '%1' is currently using an %4 processor, but physical computer '%3' has an %5 processor. A running or ...
  43. The virtual machine '%1' is using processor-specific features not supported on physical computer '%3'. To allow for migration ...
  44. The virtual machine '%1' on the Replica Server is not enabled for replication (Virtual machine ID %2). Configure the virtual ...
  45. The virtual machine '%1' or (and) one of its snapshots is not compatible with physical computer '%3'. (Virtual machine ID ...
  46. The virtual machine '{0}' has been moved to the computer '{1}'. Connection to the virtual machine on computer '{1}' could ...
  47. The virtual machine '{0}' is configured to use pass through storage '{1}'. However, that storage resource is already being ...
  48. The virtual machine '{0}' is is not currently in a state that can be made highly available. To make this virtual machine ...
  49. The virtual machine '{0}' is not currently available and cannot be made highly available. To make this virtual machine highly ...
  50. The virtual machine '{0}' is running and cannot be made highly available. To make this virtual machine highly available turn ...
  51. The virtual machine at %1 cannot be imported because version %2 of the export data is not support by this version of Hyper-V. ...
  52. The virtual machine at %1 cannot be imported because version %2 of the export data is not support by this version of Hyper-V. ...
  53. The virtual machine bus (VMBus) cannot start because the physical computer's PCI chipset does not properly support Message ...
  54. The virtual machine cannot be moved to a single location while it is using Smart Paging. You can either choose a move option ...
  55. The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible ...
  56. The virtual machine cannot be moved to the specified destination computer because that computer is not configured for live ...
  57. The virtual machine cannot be restored because the file rdvgm.exe that is required to start the RemoteFX Manager process ...
  58. The virtual machine cannot be started because all the RemoteFX-capable GPUs are disabled in Device Manager. You must enable ...
  59. The virtual machine cannot be started because all the RemoteFX-capable GPUs are disabled in Hyper-V Manager. You must enable ...
  60. The virtual machine cannot be started because the file rdvgm.exe that is required to start the RemoteFX Manager process does ...
  61. The virtual machine cannot be started because the Remote Desktop Virtualization Host (RD Virtualization Host) role service ...
  62. The virtual machine cannot be started because the server has insufficient GPU resources. If this issue persists, consider ...
  63. The virtual machine cannot be started because virtual machines that are configured with a 3D video adapter can only run on ...
  64. The virtual machine configuration resource '{0}' is not online. For best results, make sure that this resource is online ...
  65. The virtual machine could not be started because the GPU that it was previously using on the physical computer could not ...
  66. The virtual machine could not be started because the hypervisor is not running. The following actions may help you resolve ...
  67. The virtual machine could not communicate with the boot monitoring component of the Remote Desktop Virtualization Host Agent ...
  68. The virtual machine failed to communicate with the Remote Desktop Virtualization Host Agent service's boot monitoring component. ...
  69. The virtual machine for which you are trying to enable replication is not a clustered virtual machine in the failover cluster. ...
  70. The Virtual machine generation ID in the Active Directory database of this domain controller is different from the current ...
  71. The virtual machine is currently using the RemoteFX 3D video adapter. A user is currently connected via Remote Desktop. Connect ...
  72. The Virtual Machine Management Service (VMMS) is not running on node '{0}'. Before you can cluster virtual machines by using ...
  73. The Virtual Machine Management Service blocked a connection request for a Virtual Machine migration from client address '%3': ...
  74. The Virtual Machine Management Service could not find a certificate for the authentication of a migration connection: %1 ...
  75. The Virtual Machine Management Service could not register update notifications for the Integration Services Setup Disk image: ...