Windows 7

  1. The iSCSI initiator service is not on the Windows Firewall List of Authorized Applications or its entry is not currently ...
  2. The iSCSI target you selected has CHAP enabled. The server or cluster to which you assigned the LUN is not logged on to the ...
  3. The ISDN Configuration for this modem is not complete. Please fill out the information in the ISDN Tab before using this ...
  4. The issuance license policy is not logged in the AD RMS logging database. To log issuance licenses in the AD RMS logging ...
  5. The issuer of a trusted activation server licensor certificate is not trusted. The trusted activation server will be ignored. ...
  6. The item '%1!ls!' that this shortcut refers to has been changed or moved. The nearest match, based on size, date, and type, ...
  7. The item '%s' that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly. Do you ...
  8. The item '%s' that this shortcut refers to has been deleted. However, it can be restored from the recycle bin. Do you want ...
  9. The item at {0} has children and the Recurse parameter was not specified. If you continue, all children will be removed with ...
  10. The item cannot be added to the collection due to a collision with another item. Collection type = CustomClaimCollection ...
  11. The item cannot be added to the collection due to a collision with another item. Collection type = {0} Collision property ...
  12. The item cannot be processed further because search failed to find one of its properties. Check that the item is valid in ...
  13. The item will not be crawled because the Access Control List allows no one to read the item. Check that this is intended. ...
  14. The item you selected is unavailable. It might have been moved, renamed, or removed. Do you want to remove it from the list? ...
  15. The item {0} does not exist in AD RMS database. Please run Update-RmsCluster cmdlet to refresh the cluster and try again. ...
  16. The item {0} exists in AD RMS database already. Please run Update-RmsCluster cmdlet to refresh the cluster and try again. ...
  17. The Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) failed to initialize when called. ...
  18. The job has been executing for %1!d! minutes and %2!d! seconds. Replication of new changes along this path will be delayed. ...
  19. The job is configured to use a different security token for some operations, but the token is not currently available. The ...
  20. The job is not making progress. The server may be misconfigured. Background Intelligent Transfer Service (BITS) will try ...
  21. The job is too large for the server to accept. This job might exceed a job size limit set by the server administrator. Reduce ...
  22. The job object associated with application pool '%1' encountered an error during configuration. CPU monitoring may not function ...
  23. The job object attached to application pool '%1' failed to start its timer. The application pool's CPU usage is being monitored ...
  24. The JobId parameter indicates the identifier number of the job. This parameter is a handle to the job being scheduled on ...
  25. The JobId property indicates the identifier number of the job. It is used by methods as a handle to a single job being scheduled ...
  26. The JobStatus property indicates whether a scheduled service executed successfully the last time this job was supposed to ...
  27. The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. ...
  28. The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the ...
  29. The join operation was not successful. This could be because an existing computer account having name "%1" was previously ...
  30. The JoinDomainOrWorkgroup method joins computer systems to a domain or workgroup. This method is only available on Windows ...
  31. The KCC attempted to make a duplicate connection, but this operation was successfully prevented. The existing connection ...
  32. The KCC could not find the destination DSA object for connection %1. The most likely cause is a directory update while the ...
  33. The KCC will now remove the temporary replica links to the writeable copies, and re-establish a standard topology, which ...
  34. The KDC encountered a trust loop when building a list of trusted domains. This indicates that the route to the domain %1 ...
  35. The KDC encountered duplicate names while processing a Kerberos authentication request. The duplicate name is %1 (of type ...
  36. The KeepAliveInterval parameter specifies the value for the interval separating Keep Alive Retransmissions until a response ...
  37. The KeepAliveInterval property indicates the interval separating Keep Alive Retransmissions until a response is received. ...
  38. The KeepAliveTime property indicates how often the TCP attempts to verify that an idle connection is still intact by sending ...
  39. The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server %1. The target name used was %3. This indicates ...
  40. The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server %1. This indicates that the ticket used against that ...
  41. The Kerberos Key Distribution Center failed to locate the forest or domain %1 to search. Please ensure that the forest search ...
  42. The kerberos protocol encountered an error while validating the KDC certificate during smart card logon. There is more information ...
  43. The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information ...
  44. The Kerberos protocol encountered an error while validating the KDC certificate during smartcard Logon. There is more information ...
  45. The kerberos SSPI package failed to find the smartcard certificate in the certificate store. To remedy, logon as user %1 ...
  46. The kerberos SSPI package failed to locate the forest or domain %1 to search. Please ensure that the forest search order ...
  47. The kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size ...
  48. The kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size ...
  49. The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which ...
  50. The kerberos subsystem is having problems fetching tickets from your domain controller using the UDP network protocol. This ...
  51. The Kernel CEIP (Customer Experience Improvement Program) task collects additional information about the system and sends ...
  52. The kernel dump file {0} on node {1} is not in the default value of %SystemRoot%\MEMORY.DMP. This value can be modified by ...
  53. The KernelDumpOnly property has been deprecated in favor of the DebugInfoType property in the same class. All future work ...
  54. The KernelModeTime property indicates the raw counter data from the performance counter type PERF_SIZE_LARGE | PERF_TYPE_COUNTER ...
  55. The Key API Calls Delta performance counter shows the number of new key API calls made against the cluster since the last ...
  56. The key archival request specified that it should not be persisted in the database. Key Archival requests must always be ...
  57. The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate ...
  58. The Key Handles Delta performance counter shows the number of new open key handles against the cluster since the last time ...
  59. The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive ...
  60. The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker ...
  61. 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 ...
  62. The Knowledge Consistency Checker (KCC) attempted to terminate the following change notifications. Directory partition: %1 ...
  63. The Knowledge Consistency Checker (KCC) could not add a replica of the following directory partition using the following ...
  64. The Knowledge Consistency Checker (KCC) could not run successfully because the attribute on the following object did not ...
  65. The Knowledge Consistency Checker (KCC) created a new bridgehead failover connection because the following bridgeheads used ...
  66. The Knowledge Consistency Checker (KCC) deleted the following Connection object because the source directory service that ...
  67. The Knowledge Consistency Checker (KCC) detected an incompatible up-to-dateness vector format. Current format version: %1 ...
  68. The Knowledge Consistency Checker (KCC) did not delete the following Connection object. Object: %1 User Action The KCC did ...
  69. The Knowledge Consistency Checker (KCC) did not delete the following Connection object. Object: %1 User Action The KCC did ...
  70. The Knowledge Consistency Checker (KCC) did not initialize its configuration cache. This operation will be tried again later. ...
  71. The Knowledge Consistency Checker (KCC) did not initialize. Consistency updates to the replication topology for the directory ...
  72. The Knowledge Consistency Checker (KCC) didn't add a link with parameters due to a previous failure while adding a link from ...
  73. The Knowledge Consistency Checker (KCC) encountered an error while adding a Connection object from the following source directory ...
  74. The Knowledge Consistency Checker (KCC) encountered an unexpected error while performing an Active Directory Domain Services ...
  75. The Knowledge Consistency Checker (KCC) encountered an unexpected error while performing an Active Directory Lightweight ...