Windows 8.1

  1. failed to start the network listener on destination node '%2': %3 (%4). Please look at the event log on destination node ...
  2. Failed to start the Scanner and Camera Installation Wizard. Please use the Add Hardware Control Panel applet to install your ...
  3. Failed to start the Updating Run on cluster {0}. Make sure that the Cluster-Aware Updating clustered role {1} is enabled: ...
  4. Failed to start the virtual machine '%1' which required %3 MB of memory because only %4 MB was available in the system (Virtual ...
  5. Failed to start the {0} console; no management tools are available. To install the management tools on a server, start the ...
  6. Failed to switch to system context before firing the WNF notification(s) for Device Setup for incoming package %2 and outgoing ...
  7. Failed to turn off virtual machine '%1' in order to delete it. The current instance of the virtual machine must be deleted ...
  8. failed to uninstall drivers when migrating dual-mode devices from mass storage class to Media Transfer Protocol (MTP). Error ...
  9. Failed to unlink the Group Policy Object with the Active Directory site, domain, or organizational unit. You might not have ...
  10. Failed to update %1 user custom wordlist: %2. Spell checking will remain available, but this user wordlist will not be updated. ...
  11. Failed to update cluster setting on cluster '{0}' because the primary IP address '{1}' is not one of the cluster virtual ...
  12. Failed to update Identity Management for UNIX schema entity: '%1' with the following attributes: %2 This will be retried ...
  13. Failed to update setting on cluster node '{0}' for cluster '{1}'. Please confirm that the node specified is part of the cluster. ...
  14. Failed to update the backup exclusion key with err = %d (%ws). You should have local built in administrator privilege to ...
  15. Failed to update the checkpoint configuration with the new location of the saved state and memory files for checkpoint '%1': ...
  16. Failed to update the configuration with the new location of the saved state and memory files for virtual machine '%1': %3 ...
  17. Failed to update the configuration with the new location of virtual hard disk '%3' for checkpoint '%1': %4 (%5). If you apply ...
  18. Failed to update the configuration with the new location of virtual hard disk '%3' for virtual machine '%1': %4 (%5). Remove ...
  19. Failed to update the custom RDP settings on RD Connection Broker server {0}, please remove it from the deployment and try ...
  20. Failed to update the DNS ACL {0} since the corresponding Active Directory object was not found. This is expected if you do ...
  21. Failed to update the path of the parent disk for virtual hard disk '%3' for checkpoint '%1': %4 (%5). The disk may not work ...
  22. Failed to update the path of the parent disk for virtual hard disk '%3' for virtual machine '%1': %4 (%5). The disk may not ...
  23. Failed to update the security information of directory '%3' of the '%2' %1 pool because the current user does not have sufficient ...
  24. Failed to update the security information of directory '%3' of the '%2' %1 pool because the current user does not have sufficient ...
  25. Failed to update the storage location of the checkpoint files to '%5' for virtual machine '%1': %3 (%4). (Virtual machine ...
  26. Failed to update the storage location of the second level paging files to '%5' for virtual machine '%1': %3 (%4). (Virtual ...
  27. Failed to update virtual machine '{0}' in '{1}' cluster. Unable to find Failover Cluster cmdlets. Install the Failover Cluster ...
  28. Failed to upgrade printer settings for printer %1 driver %2. Error: %3. The device settings for the printer are set to those ...
  29. Failed to validate Server Message Block (SMB) share access through the IP address of the fault tolerant network driver for ...
  30. Failed to validate the new AD RMS Web application pool identity, which must be a domain user account. Open IIS manager and ...
  31. Failed to validate the virtual desktop template. Error: {0}. Verify that the virtual desktop template is sysprep generalized, ...
  32. Failed to watch for spell checking option changes: %1. Spell checking will remain available, but no changes will be reported. ...
  33. Failed to write data of scope %1 of zone %2 into file %3. Please ensure the file exists and is writable, and then attempt ...
  34. Failed to write Test Disk {0} from node {1} when that node has registered a key for the disk and another node has reserved ...
  35. Failed to write to Test Disk {0} from node {1} after a call to PREEMPT by node {2} with a valid SERVICE ACTION RESERVATION ...
  36. Failed to write to Test Disk {0} from node {1} after an attempt to preempt with an invalid key. It is expected to succeed. ...
  37. Failed to write to Test Disk {0} from node {1} after registration key was updated to the same value. It is expected to succeed. ...
  38. Failed to write to Test Disk {0} from node {1} when that node has updated its registration key. It is expected to succeed. ...
  39. Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk. ...
  40. Failed transfer of zone %1 from DNS server at %2. The DNS server at %2 aborted or failed to complete transfer of the zone. ...
  41. Failed transfer of zone {0} from DNS server at {1}. The DNS server at {1} aborted or failed to complete transfer of the zone. ...
  42. Failed while deleting Data Exchange integration service item '%3' from the registry of the guest operating system: %4 (%5). ...
  43. Failed while deleting Data Exchange integration service item '%3' from the registry of the guest operating system: %4 (%5). ...
  44. Failed while setting Data Exchange integration service item '%3' in the registry of the guest operating system: %4 (%5). ...
  45. Failed while setting the Data Exchange integration service item '%3' in the registry of the guest operating system: %4 (%5). ...
  46. Failed while upgrading Ethernet connection settings for adapter '%3' of virtual machine '%4': %1 (%2) (Virtual Machine ID ...
  47. failed with error (%2) because the collection already contains an object of with identifier, %3, and publisher, %4, with ...
  48. Failed writing the file screen audit log on volume '%1' due to a disk-full error: If the disk is full, please clean it up ...
  49. Failed: Unable to get StorageExtents from DiskDrives due to an inernal failure or communication error with the provider%0 ...
  50. Failover cluster '{0}' is running a version of the Windows Server operating system that is not supported by Cluster-Aware ...
  51. Failover Cluster Command Interface is the deprecated cluster.exe command-line tool for Failover Clustering. This tool has ...
  52. Failover Cluster feature is not installed on node %1. This feature is required to installed before the node is added to the ...
  53. Failover Cluster Manager could not bring the group '%1' online. The error was '%2'. For more information see the Failover ...
  54. Failover Cluster Manager could not change the auto start settings for group '%1'. The error was '%2'. For more information ...
  55. Failover Cluster Manager could not complete disk defragmentation for volume '%1'. The error was '%2'. For more information ...
  56. Failover Cluster Manager could not complete disk error checking for volume '%1'. The error was '%2'. For more information ...
  57. Failover Cluster Manager could not contact the DNS servers to resolve name '%1'. For more information see the Failover Cluster ...
  58. Failover Cluster Manager could not delete the group '%1'. The error was '%2'. For more information see the Failover Cluster ...
  59. Failover Cluster Manager could not display the dependency report. This might happen if the dependency relationship between ...
  60. Failover Cluster Manager could not enable the tools property page for '%1' because some information about the volumes could ...
  61. Failover Cluster Manager could not find function '%1' in clusapi.dll. Please make sure that the installation of the Failover ...
  62. Failover Cluster Manager could not find the appropriate admin extensions property page for CLSID '{%1}'. For more information ...
  63. Failover Cluster Manager could not find the appropriate admin extensions property page. For more information see the Failover ...
  64. Failover Cluster Manager could not generate a report after performing one of the tasks requested by the user. The user request ...
  65. Failover Cluster Manager could not get virtual machines on cluster node '%1'. The error was '%2'. For more information see ...
  66. Failover Cluster Manager could not impersonate user '%1' because it did not get the token required. For more information ...
  67. Failover Cluster Manager could not impersonate user '%1'. For more information see the Failover Cluster Manager Diagnostic ...
  68. Failover Cluster Manager could not load clusapi.dll. This is required for any monitoring and management of local or remote ...
  69. Failover Cluster Manager could not load the DFS management tools. This will prevent the Configure File Share Witness wizard ...
  70. Failover Cluster Manager could not make virtual machine '%1' highly available. Please refer to the cluster reports in the ...
  71. Failover Cluster Manager could not move the group '%1' to node '%2'. The error was '%3'. For more information see the Failover ...
  72. Failover Cluster Manager could not offline the group '%1'. The error was '%2'. For more information see the Failover Cluster ...
  73. Failover Cluster Manager could not open a handle to the cluster or a cluster item because the client does not support such ...
  74. Failover Cluster Manager could not retrieve properties for cluster resource type '%1'. Please make sure the resource type ...
  75. Failover Cluster Manager could not shut down cluster '%1'. For more information see the Failover Cluster Manager Diagnostic ...