Windows 7

  1. The client presented an invalid inbound token as evidence. The token referenced an unknown X509 Subject Key Identifier (SKI). ...
  2. The client presented an invalid inbound token as evidence. The token referenced an X509 certificate that is not trusted by ...
  3. The client presented an invalid inbound token as evidence. The token referenced an X509 certificate that is not trusted by ...
  4. The client presented an invalid inbound token as evidence. The token referenced an X509 certificate whose certificate chain ...
  5. The client presented an invalid logon accelerator token as evidence. The token contained invalid XML or did not conform to ...
  6. The client presented an invalid logon accelerator token as evidence. The token included a Kerberos AP-Request that was originated ...
  7. The client presented an invalid logon accelerator token as evidence. The token included a Kerberos AP-Request that was rejected ...
  8. The client presented an invalid logon accelerator token as evidence. The token included a valid Kerberos AP-Request from ...
  9. The client presented an invalid logon accelerator token as evidence. The token referenced a trusted X509 certificate with ...
  10. The client presented an invalid logon accelerator token as evidence. The token referenced an unknown X509 Subject Key Identifier ...
  11. The client presented an invalid logon accelerator token as evidence. The token referenced an X509 certificate that is not ...
  12. The client presented an invalid logon accelerator token as evidence. The token referenced an X509 certificate whose certificate ...
  13. The client presented credentials, but they could not be verified because no account store returned an authoritative result. ...
  14. The client presented credentials, but they could not be verified because no account store returned an authoritative result. ...
  15. The client presented valid credentials. Depending on the audit policy, the list of generated claims may be written to a 10550 ...
  16. The client presented valid credentials. Depending on the audit policy, the list of generated claims may be written to a 550 ...
  17. The client specified username and password in the request to the destination computer. But the destination computer requested ...
  18. The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be ...
  19. The client width you have entered is invalid. The client width must be a multiple of 4 pixels. Please enter another client ...
  20. The client-side extension could not %1 %2 preference items for the '%3' Group Policy object because Windows is shutting down ...
  21. The ClientAccessible property is indicates whether the shadow copy was created by the Windows Previous Versions component. ...
  22. The ClientCredentialInfo static method CreateCertificateCredential was called in a context where no client certificate was ...
  23. The ClientSiteName property indicates the name of the site where the domain controller is configured to be in. This value ...
  24. The CliSeeAlso association provides a relationship between an alias and related aliases that may be used as a part of the ...
  25. The clock difference between the home server %1 and target server %2 is greater than one minute. This may cause Kerberos ...
  26. The clock on your computer has been changed. Viewing this recording is not allowed if the clock has been changed after the ...
  27. The clocks on all homegroup computers must be set no more than 24 hours apart. Make sure your computer clocks are synchronized, ...
  28. The CLR version should be of the form v2.0. The major version and minor version should both be integers and v1.0 is not supported. ...
  29. The CLSID %1, item %2 and title %3 has the named value AppID, but is not recorded under \HKEY_CLASSES_ROOT\AppId. Do you ...
  30. The Clsid property, if applicable, defines the COM CLSID associated with server implementation. Note: decoupled providers ...
  31. The Clsid property, if applicable, defines the COM CLSID associated with server implementation. Note: decoupled providers ...
  32. The Cluster API Calls Delta performance counter shows the number of new cluster API calls made against the cluster since ...
  33. The Cluster API Calls performance object consists of counters that show information about API calls made against the cluster ...
  34. The Cluster API Handles performance object consists of counters that show information about open handles against the cluster ...
  35. The Cluster Checkpoint Manager performance object consists of counters that show information about cluster Checkpoint Manager. ...
  36. The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class. ...
  37. The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource. ...
  38. The Cluster Database performance object consists of counters that show information about cluster database and operations ...
  39. The cluster disk driver (clusdisk.sys) startup type on node {0} is set to SERVICE_DISABLED (0x4). The recommended value is ...
  40. The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication ...
  41. The Cluster Global Update Manager Messages performance object consists of counters that show information about cluster Global ...
  42. The Cluster Handles Delta performance counter shows the number of new open cluster handles against the cluster since the ...
  43. The cluster has an even number of nodes. Consider changing to the Node and Disk Majority quorum configuration to improve ...
  44. The cluster has an odd number of nodes and a quorum disk. A quorum disk in this scenario reduces cluster high availability. ...
  45. The cluster IP address and dedicated IP address cannot be identical. Type a different cluster IP and dedicated IP addresses. ...
  46. The cluster IP addresses are shared by every member of the cluster for load balancing. The first IP address listed is considered ...
  47. The cluster key protection password is not available. The imported trusted publishing domain contains an AD RMS internally ...
  48. The cluster key protection password is not available. The imported trusted publishing domain contains an AD RMS internally ...
  49. The cluster management item is no longer available. A possible cause is that the connection to the cluster is no longer available. ...
  50. The Cluster Multicast Request-Response Messages performance object consists of counters that show information about cluster ...
  51. The cluster network address is not valid. The address must be of the form xx-xx-xx-xx-xx-xx or xx:xx:xx:xx:xx:xx. Type valid ...
  52. The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which ...
  53. The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. ...
  54. The Cluster Network Messages performance object consists of counters that show information about cluster messages sent and ...
  55. The Cluster Network Reconnections performance object consists of counters that show information about cluster reconnects ...
  56. The cluster node '{0}' was evicted from the cluster, but was not fully cleaned up. Please see the Failover Clustering application ...
  57. The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps ...
  58. The cluster node {0} was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup ...
  59. The cluster or computer specified may not be running a supported Windows Server version. The following error was encountered: ...
  60. The cluster or computer you specified could not be found. Please make sure the cluster or computer is accessible and that ...
  61. The cluster property "ClusterLogLevel" is set with a value of {0}. The default level is {1}. A value less than {1} is not ...
  62. The cluster property "ClusterLogLevel" is set with a value of {0}. The default level is {1}. The value of {0} causes verbose ...
  63. The cluster property "ClusterLogSize" is set with a value less than default value of {0}. This value specifies the size of ...
  64. The cluster property QuorumArbitrationTimeMax value is set to {0}. The default value is {1}. This value specifies the number ...
  65. The Cluster Resource Control Manager performance object consists of counters that show information about cluster resources ...
  66. The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due ...
  67. The Cluster Resources performance object consists of counters that show information about cluster resources grouped by resource ...
  68. The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error ...
  69. The Cluster service cannot identify node '%1' as a member of failover cluster '%2'. If the computer name for this node was ...
  70. The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node ...
  71. The cluster service detected that the witness disk designation has changed - usually indicating that the current node has ...
  72. The Cluster service failed to bring clustered service or application '%1' completely online or offline. One or more resources ...
  73. The cluster service failed to properly cleanup a clustered disk with ID '%2' while destroying the cluster. The error code ...
  74. The Cluster service failed to start because it was unable to register interface(s) with the RPC service. The error code was ...
  75. The cluster service failed to start. This was because the failover cluster virtual adapter failed to initialize the miniport ...