Windows 8
- The IPv4 address block %1 has been added with the value %2 for the configuration setting %3.%rIPv4 address block: %1%rConfiguration ...
- The IPv4 address block %1 has been updated with the value %2 for the configuration setting %3. The previous value was %4.%rIPv4 ...
- The IPv4 address entered contains one or more parts that are greater than the maximum value of a BYTE (8-bit number). Should ...
- The IPV4 static settings are invalid. Valid IPV4 static settings must include all of the following: IPV4 addresses, IPV4 ...
- The IPv6 address %1 has been updated with the value %2 for the configuration setting %3. The previous value was %4.%rIPv6 ...
- The IPv6 address block %1 has been added with the value %2 for the configuration setting %3.%rIPv6 address block: %1%rConfiguration ...
- The IPv6 address block %1 has been updated with the value %2 for the configuration setting %3. The previous value was %4.%rIPv6 ...
- The IPv6 address range %1 has been updated with the value %2 for the configuration setting %3. The previous value was %4%rIPv6 ...
- The IPv6 address specified for the internal adapter is not a valid internal network address. Specify a valid IPv6 address. ...
- The IPv6 addresses of the following Remote Access infrastructure servers are not included in the internal network IPv6 prefix ...
- The IPv6 prefix entered is not accepted for the following reason: %1!s! The following constraint apply to IPv6 prefix: The ...
- The IPv6 tunnel address {0} does not have any dependencies on an IPv4 address. In order for an IPv6 tunnel address to work ...
- The IR control cable is disconnected so Windows Media Center cannot change channels to start a recording. Please ensure your ...
- The IRQ of %2 was selected for a network PCMCIA PCCARD. This IRQ is not supported for PCCARDs on this system. For network ...
- The ISATAP server name has not been published. 2. The DNS server cannot be reached, or is unresponsive. 3. The ISATAP name ...
- The iSCSI initiator %1 does not have access to this iSCSI target server. To access storage services, you must create an iSCSI ...
- The iSCSI initiator mutual CHAP secret is used to authenticate the target. The secret entered here will have to be configured ...
- The iSCSI initiator name is used to uniquely identify a system to iSCSI storage devices on the network. The default name ...
- The iSCSI initiator service ensures that all volumes and devices on a favorite target are available. An attempt to restore ...
- The iSCSI initiator service is not on the Windows Firewall List of Authorized Applications or its entry is not currently ...
- The iSCSI target is not configured to use authentication but iSCSI initiator %1 requested it.The target and the initiator ...
- The iSCSI target rejected a connection request from the local computer. To access the virtual disk from the local computer, ...
- The iSCSI target you selected has CHAP enabled. The server or cluster to which you assigned the LUN is not logged on to the ...
- The ISDN Configuration for this modem is not complete. Please fill out the information in the ISDN Tab before using this ...
- The issuance license policy is not logged in the AD RMS logging database. To log issuance licenses in the AD RMS logging ...
- The issuer of a trusted activation server licensor certificate is not trusted. The trusted activation server will be ignored. ...
- The item '%1!ls!' that this shortcut refers to has been changed or moved. The nearest match, based on size, date, and type, ...
- The item '%s' that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly. Do you ...
- The item '%s' that this shortcut refers to has been deleted. However, it can be restored from the Recycle Bin. Do you want ...
- The item at {0} has children and the Recurse parameter was not specified. If you continue, all children will be removed with ...
- The item cannot be processed further because search failed to find one of its properties. Check that the item is valid in ...
- The item will not be crawled because the Access Control List allows no one to read the item. Check that this is intended. ...
- The item you selected is unavailable. It might have been moved, renamed, or removed. Do you want to remove it from the list? ...
- The item {0} does not exist in AD RMS database. Please run Update-RmsCluster cmdlet to refresh the cluster and try again. ...
- The item {0} exists in AD RMS database already. Please run Update-RmsCluster cmdlet to refresh the cluster and try again. ...
- The item {0} that resolves to {1} is not located in the same directory as the module manifest or any of its subdirectories. ...
- The job cannot run because a previous assessment either stopped responding or a reboot is required. Would you like to remove ...
- The job could not be created because the JobInvocationInfo does not contain a JobDefinition. Initialize the JobInvocationInfo ...
- The job has been executing for %1!d! minutes and %2!d! seconds. Replication of new changes along this path will be delayed. ...
- The job has been stopped by a 'Kill' state change request. Underlying processes might have been left running, and cleanup ...
- The job has been stopped by a 'Terminate' state change request. The job and all its underlying processes are ended and can ...
- The job is configured to use a different security token for some operations, but the token is not currently available. The ...
- The job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific ...
- The job is not making progress. The server may be misconfigured. Background Intelligent Transfer Service (BITS) will try ...
- The job is too large for the server to accept. This job might exceed a job size limit set by the server administrator. Reduce ...
- The job operation (Create, Get, or Remove) could not be performed because the JobSourceAdapter type specified in the JobDefinition ...
- The job was not found. Save the current job with a new name before you close the tab. If you do not save the current job, ...
- The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. ...
- The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the ...
- The join operation was not successful. This could be because an existing computer account having name "%1" was previously ...
- The KCC attempted to make a duplicate connection, but this operation was successfully prevented. The existing connection ...
- The KCC could not find the destination DSA object for connection %1. The most likely cause is a directory update while the ...
- The KCC will now remove the temporary replica links to the writeable copies, and re-establish a standard topology, which ...
- The KDC certificate for the domain controller does not contain the KDC Extended Key Usage (EKU): 1.3.6.1.5.2.3.5: Error Code ...
- The KDC certificate for the domain controller does not have the DNS name of domain %1 in the Subject Alternative Name (SAN) ...
- The KDC encountered a trust loop when building a list of trusted domains. This indicates that the route to the domain %1 ...
- The KDC encountered duplicate names while processing a Kerberos authentication request. The duplicate name is %1 (of type ...
- The Kerberos client could not find a suitable credential to use with the authentication proxy: AuthProxy: Proxy: %1 ProxyBypass: ...
- The Kerberos client could not locate a domain controller for domain %1: %2. Kerberos authentication requires communicating ...
- The Kerberos client could not retrieve passwords for the group managed service account. LogonId: %1:%2 DomainName: %3 UserName: ...
- The Kerberos client could not send a Kerberos proxy request. ProxyServer: ServerName: %1 ServerPort: %2 ServerVdir: %3 Error ...
- The Kerberos client received a KDC certificate that does not have a matched domain name. Expected Domain Name: %1 Error Code: ...
- The Kerberos client received a KDC certificate that does not have KDC EKU (not based on Kerberos Authentication Template). ...
- The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server %1. The target name used was %3. This indicates ...
- The Kerberos client received a KRB_AP_ERR_TKT_NYV error from the server %1. This indicates that the ticket presented to that ...
- The Kerberos client updated passwords for the group managed service account. LogonId: %1:%2 DomainName: %3 UserName: %4 Update ...
- The Kerberos client was bound to domain controller %1 for the domain %2 but could not access this domain controller at the ...
- The Kerberos Key Distribution Center (KDC) for the domain %1 does not have a certificate installed or does not support logon ...
- The Kerberos Key Distribution Center failed to locate the forest or domain %1 to search. Please ensure that the forest search ...
- The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information ...
- The Kerberos protocol encountered an error while validating the KDC certificate during smartcard Logon. There is more information ...
- The Kerberos SSPI package failed to find the smart card certificate in the certificate store. To remedy this failure, logon ...
- The Kerberos SSPI package failed to locate the forest or domain %1 to search. Ensure that the Use forest search order Group ...
- The Kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size ...
- The Kerberos SSPI package generated an output token of size %1 bytes, which was too large to fit in the token buffer of size ...