Windows 8.1

  1. The KDC encountered duplicate names while processing a Kerberos authentication request. The duplicate name is %1 (of type ...
  2. The KeepAliveInterval parameter specifies the value for the interval separating Keep Alive Retransmissions until a response ...
  3. The KeepAliveInterval property indicates the interval separating Keep Alive Retransmissions until a response is received. ...
  4. The KeepAliveTime property indicates how often the TCP attempts to verify that an idle connection is still intact by sending ...
  5. The Kerberos client could not find a suitable credential to use with the authentication proxy: AuthProxy: Proxy: %1 ProxyBypass: ...
  6. The Kerberos client could not locate a domain controller for domain %1: %2. Kerberos authentication requires communicating ...
  7. The Kerberos client could not retrieve passwords for the group managed service account. LogonId: %1:%2 DomainName: %3 UserName: ...
  8. The Kerberos client could not send a Kerberos proxy request. ProxyServer: ServerName: %1 ServerPort: %2 ServerVdir: %3 Error ...
  9. The Kerberos client received a KDC certificate that does not have a matched domain name. Expected Domain Name: %1 Error Code: ...
  10. The Kerberos client received a KDC certificate that does not have KDC EKU (not based on Kerberos Authentication Template). ...
  11. The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server %1. The target name used was %3. This indicates ...
  12. The Kerberos client received a KRB_AP_ERR_TKT_NYV error from the server %1. This indicates that the ticket presented to that ...
  13. The Kerberos client updated passwords for the group managed service account. LogonId: %1:%2 DomainName: %3 UserName: %4 Update ...
  14. The Kerberos client was bound to domain controller %1 for the domain %2 but could not access this domain controller at the ...
  15. The Kerberos Key Distribution Center (KDC) for the domain %1 does not have a certificate installed or does not support logon ...
  16. The Kerberos Key Distribution Center failed to locate the forest or domain %1 to search. Please ensure that the forest search ...
  17. The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information ...
  18. The Kerberos protocol encountered an error while validating the KDC certificate during smartcard Logon. There is more information ...
  19. The Kerberos SSPI package failed to find the smart card certificate in the certificate store. To remedy this failure, logon ...
  20. The Kerberos SSPI package failed to locate the forest or domain %1 to search. Ensure that the Use forest search order Group ...
  21. The Kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size ...
  22. The Kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size ...
  23. The Kerberos subsystem currently cannot retrieve tickets from your domain controller using the UDP network protocol. This ...
  24. The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which ...
  25. The Kernel CEIP (Customer Experience Improvement Program) task collects additional information about the system and sends ...
  26. The kernel dump file {0} on node {1} is not in the default value of %SystemRoot%\MEMORY.DMP. This value can be modified by ...
  27. The KernelDumpOnly property has been deprecated in favor of the DebugInfoType property in the same class. All future work ...
  28. The KernelModeTime property indicates the raw counter data from the performance counter type PERF_SIZE_LARGE | PERF_TYPE_COUNTER ...
  29. The key '{0}' does not have a valid format. For information about the correct format, see about_Parameters_Default_Values ...
  30. The key archival request specified that it should not be persisted in the database. Key Archival requests must always be ...
  31. The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate ...
  32. The Key Distribution Center (KDC) cannot find a suitable certificate to use. This KDC is not enabled for smart card or certificate ...
  33. The Key Distribution Center (KDC) encountered failures when updating the krbtgt account for the Dynamic Access Control and ...
  34. The Key Distribution Center (KDC) failed to validate its current KDC certificate. This KDC might not be enabled for smart ...
  35. The Key Distribution Center (KDC) has the Dynamic Access Control and Kerberos armoring policy configured for a level which ...
  36. The Key Distribution Center (KDC) uses a certificate without KDC Extended Key Usage (EKU) which can result in authentication ...
  37. The Key Distribution Center (KDC) uses the below KDC certificate for smart card or certificate authentication. Kdc Certificate ...
  38. The Key Master cannot be contacted to transfer private key material. If you seize the Key Master role on this DNS server, ...
  39. The Key Master is a DNS server that generates and manages cryptographic keys for a DNSSEC protected zone. Any authoritative ...
  40. The key module in the rule is incompatible with the authentication methods specified in the associated authentication sets. ...
  41. The key must be specified in base 36. Only digits 0-9 and letters a-z can be used when specifying the key. Each of the four ...
  42. The key properties combination '{0}' is duplicated for keys '{1}' of resource '{2}' in node '{3}'. Please make sure key properties ...
  43. The key property for an entry in the dictionary of functions to define cannot be empty because the key property is used as ...
  44. The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive ...
  45. The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker ...
  46. The key will be restored on top of key: %1. All value entries and subkeys of this key will be deleted. Do you want to continue ...
  47. The keys '{0}' do not have valid formats. For information about the correct format, see about_Parameters_Default_Values at ...
  48. The Knowledge Consistency Checker (KCC) attempted to terminate the following change notifications. Directory partition: %1 ...
  49. The Knowledge Consistency Checker (KCC) could not add a replica of the following directory partition using the following ...
  50. The Knowledge Consistency Checker (KCC) created a new bridgehead failover connection because the following bridgeheads used ...
  51. The Knowledge Consistency Checker (KCC) deleted the following Connection object because the source directory service that ...
  52. The Knowledge Consistency Checker (KCC) detected an incompatible up-to-dateness vector format. Current format version: %1 ...
  53. The Knowledge Consistency Checker (KCC) detected that the following object have missing required attributes or attribute ...
  54. The Knowledge Consistency Checker (KCC) did not delete the following Connection object. Object: %1 User Action The KCC did ...
  55. The Knowledge Consistency Checker (KCC) did not delete the following Connection object. Object: %1 User Action The KCC did ...
  56. The Knowledge Consistency Checker (KCC) did not initialize its configuration cache. This operation will be tried again later. ...
  57. The Knowledge Consistency Checker (KCC) did not initialize. Consistency updates to the replication topology for the directory ...
  58. The Knowledge Consistency Checker (KCC) didn't add a link with parameters due to a previous failure while adding a link from ...
  59. The Knowledge Consistency Checker (KCC) encountered an error while adding a Connection object from the following source directory ...
  60. The Knowledge Consistency Checker (KCC) encountered an unexpected error while performing an Active Directory Domain Services ...
  61. The Knowledge Consistency Checker (KCC) encountered an unexpected error while performing an Active Directory Lightweight ...
  62. The Knowledge Consistency Checker (KCC) failed to stop after the directory service was shut down or restarted. Additional ...
  63. The Knowledge Consistency Checker (KCC) failed to update the replication topology for the local directory service. The KCC ...
  64. The Knowledge Consistency Checker (KCC) has detected problems because the attribute on the following object did not have ...
  65. The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. Directory partition: ...
  66. The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory ...
  67. The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service ...
  68. The Knowledge Consistency Checker (KCC) successfully added a replication agreement for the following directory partition. ...
  69. The Knowledge Consistency Checker (KCC) successfully terminated the following change notifications. Directory partition: ...
  70. The Knowledge Consistency Checker (KCC) was unable to complete the topology for the following site. Site: %1 An attempt to ...
  71. The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following ...
  72. The Knowledge Consistency Checker attempted to ldap-bind to the following remote directory service instance. The operation ...
  73. The Knowledge Consistency Checker attempted to ldap-modify the following object on the following remote directory service ...
  74. The Knowledge Consistency Checker attempted to ldap-unbind to the following remote directory service instance. The operation ...
  75. The Knowledge Consistency Checker attempted to replicate changes for the following single object from the following remote ...