Windows 8.1

  1. The cluster that this computer is joining uses a different cryptographic provider (CSP) than the one specified. Install Active ...
  2. The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover ...
  3. The cluster to which you are trying to join this server is not currently provisioned as either a root or licensing-only cluster. ...
  4. The cluster URL is either empty or mal-formatted. It must in the form of http(s)://domain/_wmcs/licensing or http(s)://domain/_wmcs/certification. ...
  5. The Cluster-Aware Updating clustered role has been moved or failed over {0} times during the Updating Run, which indicates ...
  6. The clustered disks could not be enumerated or could not be put into cluster maintenance mode. Check the System event log ...
  7. The clustered RD Connection Broker server for the cluster {0} is not a part of the server pool. Add the server {1} to the ...
  8. The clustered role will not be started because the resources may need additional configuration. Finish configuration, and ...
  9. The clustered role {0} has a value other than NULL for the property "AntiAffinityClassNames." The value of this property ...
  10. The clustered virtual machine '{0}' is no longer available on computer '{1}'. The virtual machine may have been moved, taken ...
  11. The cmdlet "{0}" or the alias "{1}" cannot be present when "{2}","{3}","{4}" or "{5}" keys are specified in the session configuration ...
  12. The cmdlet '{0}', mapped with action '{1}', does not have a parameter mapped with key property '{2}' of resource type '{3}'. ...
  13. The cmdlet cannot be run because the required migration manifests are missing. Verify that the dlmanifests folder exist at ...
  14. The cmdlet cannot be run because the required migration manifests are missing. Verify that the replacementmanifests folder ...
  15. The cmdlet cannot configure the {0} specific settings for the network adapter with physical address {1} because the protocol ...
  16. The cmdlet cannot connect to the destination server. For more information, see "Data Migration Connectivity" in the Troubleshooting ...
  17. The cmdlet cannot connect to the source server. For more information, see "Data Migration Connectivity" in the Troubleshooting ...
  18. The cmdlet cannot discover the roles and features that are installed on the local computer. Verify that a Server Manager ...
  19. The cmdlet cannot retrieve the {0} settings for the network adapter with physical address {1} because the protocol is disabled ...
  20. The cmdlet cannot run because the following conflicting parameters are specified: Body and InFile. Specify either Body or ...
  21. The cmdlet cannot run because the following conflicting parameters are specified: Credential and UseDefaultCredentials. Specify ...
  22. The cmdlet cannot run because the following conflicting parameters are specified: ProxyCredential and ProxyUseDefaultCredentials. ...
  23. The cmdlet cannot run because the following conflicting parameters are specified: Session and SessionVariable. Specify either ...
  24. The cmdlet cannot run because the following parameter is missing: OutFile. Provide a valid OutFile parameter value when using ...
  25. The cmdlet cannot run because the following parameter is missing: Proxy. Provide a valid proxy URI for the Proxy parameter ...
  26. The cmdlet cannot transfer file {0} to the destination server. The file is currently being locked by another application. ...
  27. The cmdlet cannot transfer folder {0} to the destination server. Data transfer from a non-NTFS file system is not supported. ...
  28. The cmdlet cannot transfer share {0} from folder {1} to the destination server. Folder {2} does not exist on the destination ...
  29. The cmdlet cannot transfer share {0} from folder {1} to the destination server. Share {0} already exists on the destination ...
  30. The cmdlet cannot transfer the {0} {1} permission for local user or group {2} on share {3} for folder {4}], because this ...
  31. The cmdlet could not verify that the path '{0}' can be accessed by the cluster. If the cluster uses a non-Microsoft file ...
  32. The cmdlet does not fully support the Inquire action for debug messages. Cmdlet operation will continue during the prompt. ...
  33. The cmdlet does not fully support the Inquire action for warnings. Cmdlet operation will continue during the prompt. Select ...
  34. The cmdlet does not fully support the Stop action for warnings. Cmdlet operation will be stopped with a delay. Select a different ...
  35. The cmdlet ensures that there is at least one address range always present by disallowing deletion of the last address range. ...
  36. The cmdlet is running in local mode because the -Offline cmdlet flag was not specified. However, the local machine is either ...
  37. The cmdlet name "{0}" cannot be validated because it is not in the correct format. Cmdlet names must include a verb and a ...
  38. The CNG key isolation service is hosted in the LSA process. The service provides key process isolation to private keys and ...
  39. The code describing why the Gatherer service went into back off state. 0 - up and running 1 - high system IO traffic 2 - ...
  40. The code on this page disabled back and forward caching. For more information, see: http://go.microsoft.com/fwlink/?LinkID=291337 ...
  41. The CodeSet property indicates the code page value used by the operating system. A code page contains a character table used ...
  42. The Collect Procedure for the "%1!s!" service in DLL "%2!s!" generated an exception or returned an invalid status. The performance ...
  43. The collect procedure in Extensible Counter DLL "%1!s!" for the "%2!s!" service returned a buffer that was larger than the ...
  44. The collection {0} does not contain any virtual desktops. You must add a virtual desktop to this collection before publishing ...
  45. The collection {0} does not have any associated RD Session Host servers. Add RD Session Host servers to this collection before ...
  46. The CollectionOfMSEs object allows the grouping of Managed SystemElements for various identification purposes and to reduce ...
  47. The CollectionOfMSEs object allows the grouping of ManagedSystemElements for the purposes of associating Settings and Configurations. ...
  48. The ColorPlanes property indicates the current number of color planes used in the video display. A color plane is another ...
  49. The ColorPlanes property indicates the current number ofcolor planes used in the display configuration. A color plane is ...
  50. The ColorTableEntries property indicates the number of color indexes in a color table for a video display. This property ...
  51. The ColorTableEntries property indicates the size of the system's color table, if the device has a color depth of no more ...
  52. The columns were not successfully changed because one or more objects have property sheets active. Close the property sheets, ...
  53. The COM Server with CLSID %1 and name "%2" cannot be started on machine "%3" during Safe Mode. The Data Deduplication service ...
  54. The COM Server with CLSID %1 and name "%2" cannot be started on machine "%3". Most likely the CPU is under heavy load. Error: ...
  55. The COM sub system is suppressing duplicate event log entries for a duration of %1 seconds. The suppression timeout can be ...
  56. The COM+ Event System caught an access violation at address %1 within method %3 of interface %4. The method attempted to ...
  57. The COM+ Event System could not apply the filter criteria to subscription %2 with display name "%6" because the criteria ...
  58. The COM+ Event System could not fire an EventObjectChange event to subscription %2 because a bad HRESULT was detected during ...
  59. The COM+ Event System could not fire an EventObjectChange event to subscription %2 because the query criteria string "%3" ...
  60. The COM+ Event System could not remove the %2 object %3.%rObject name: %4%rObject description: %5%rThe HRESULT was %1.%0 ...
  61. The COM+ Event System could not store the per-user subscription %2 because the registry key HKEY_USERS\%3 could not be opened. ...
  62. The COM+ Event System detected a bad return code during its internal processing. HRESULT was %3 from line %2 of %1. This ...
  63. The COM+ Event System detected a bad return code during its internal processing. HRESULT was %3 from line %2 of %1. This ...
  64. The COM+ Event System detected a corrupt IEventClass object. The COM+ Event System has removed object ID %2. The publisher ...
  65. The COM+ Event System detected a corrupt IEventSubscription object. The COM+ Event System has removed object ID %1. The subscriber ...
  66. The COM+ Event System detected an error trying to query an %1 object because the criteria string "%2" contained an error. ...
  67. The COM+ Event System detected an inconsistency in its internal state. The assertion "%3" failed at line %2 of %1. This warning ...
  68. The COM+ Event System detected an unexpected error from a Win32 API call at line %2 of %1. A call to %3 failed with error ...
  69. The COM+ Event System detected an unexpected null pointer during its internal processing, at line %2 of %1. This warning ...
  70. The COM+ Event System did not fire the %0 method on event class %1 for publisher %2 to the invalid subscriber %3. The display ...
  71. The COM+ Event System failed to create an instance of the MultiInterfacePublisherFilter %2 defined in event class %3. %4 ...
  72. The COM+ Event System failed to fire the %2 method on event class %3 for publisher %4 and subscriber %5. The display name ...
  73. The COM+ Event System fired the %2 method on event class %3 for publisher %4 and subscriber %5 but the subscriber returned ...
  74. The COM+ Event System service blocked the creation of a subscription to the event class with CLSID %0 in partition %1 for ...
  75. The COM+ Event System timed out attempting to fire the %2 method on event class %3 for publisher %4 and subscriber %5. The ...