Windows 8

  1. DHCP Failover enables high availability of DHCP services by synchronizing IP address lease information between two DHCP servers. ...
  2. DHCP has cancelled IPv4 address acquisition cycle after %1 DISCOVER transmissions on interface %2 because the machine is ...
  3. DHCP has cancelled IPv4 address acquisition cycle after %1 DISCOVER transmissions on interface %2 because the machine is ...
  4. DHCP has cancelled IPv4 address acquisition cycle after %1 DISCOVER transmissions on interface %2 because the machine is ...
  5. DHCP has cancelled IPv6 address acquisition cycle after %1 SOLICIT transmissions on interface %2 because the machine is in ...
  6. DHCP has cancelled IPv6 address acquisition cycle after %1 SOLICIT transmissions on interface %2 because the machine is in ...
  7. DHCP has cancelled IPv6 address acquisition cycle after %1 SOLICIT transmissions on interface %2 because the machine is in ...
  8. DHCP has cancelled IPv6 address acquisition cycle after %1 SOLICIT transmissions on interface %2 because the machine is in ...
  9. DHCP has found a match in the cache for Service Set Identifier(SSID) %1(Hexadecimal value of SSID: %2) for the Network Card ...
  10. DHCP has not found a match in the cache for Service Set Identifier(SSID) %1(Hexadecimal value of SSID: %2) for the interface ...
  11. DHCP has not plumbed an address using Service Set Identifier(SSID) %1(Hexadecimal value of SSID: %2) for the Network Card ...
  12. DHCP has plumbed an address using Service Set Identifier(SSID) %1(Hexadecimal value of SSID: %2) for the Network Card with ...
  13. DHCP has received a Service Set Identifier(SSID) %1(Hexadecimal value of SSID: %2) for the Network Card with the network ...
  14. DHCP is changed from nondhcp to stateless mode on the interface %1. Status Code is %2. Managed Flag value %3 OtherConfig ...
  15. DHCP is changed from stateful to stateless mode on the interface %1. Status Code is %2. Managed Flag value %3 OtherConfig ...
  16. DHCP name protection can be enabled/disabled using Configure button. These settings will be used as the default settings ...
  17. DHCP protocol will attempt to automatically configure your workstation during system initialization. Any parameters specified ...
  18. DHCP Relay Agent Configuration for %1!s! - State : %2!s! and %3!s! RelayMode : %4!s! Max Hop Count : %5!d! Min seconds since ...
  19. DHCP Relay Agent Interface Config for : %1!s! - State %2!s! Relay Mode %3!s! Max Hop Count %4!d! Minimum Seconds Since Boot ...
  20. DHCP Relay Agent Interface Stats for : %1!s! - State %2!s! Send Failures %3!d! Receive Failures %4!d! ARP Update Failures ...
  21. DHCP server honors request for A and PTR records registration for Windows DHCP clients. - DHCP server dynamically updates ...
  22. DHCP server honors request for AAAA and PTR records registration for Windows DHCP clients. - DHCP server dynamically updates ...
  23. DHCP Server is unable to bind to UDP port number %1 as it is used by another application. This port must be made available ...
  24. DHCP Server is unable to bind to UDP port number {0} as it is used by another application. This port must be made available ...
  25. Dhcp Server Scope Set DnsConfig failed. DNS Configuration key is not created. Use DHCP Snap-in to initialize the registry ...
  26. Dhcp Server Set DnsConfig failed. DNS Configuration key is not created. Use DHCP Snap-in to initialize the registry keys. ...
  27. DHCP Services were denied to machine with hardware address %1, hardware type %3 and FQDN/Hostname %2 because it did not match ...
  28. DHCP Services were denied to machine with hardware address %1, hardware type %3 and unspecified FQDN/Hostname%2 because it ...
  29. DHCP Services were denied to machine with hardware address %1, hardware type %4 and FQDN/Hostname %2 because it matched entry ...
  30. DHCP Services were denied to machine with hardware address %1, hardware type %4 and unspecified FQDN/Hostname%2 because it ...
  31. DHCP Services were denied to machine with hardware address {0}, hardware type {2} and FQDN/Hostname {1} because it did not ...
  32. DHCP Services were denied to machine with hardware address {0}, hardware type {2} and unspecified FQDN/Hostname{1} because ...
  33. DHCP Services were denied to machine with hardware address {0}, hardware type {3} and FQDN/Hostname {1} because it matched ...
  34. DHCP Services were denied to machine with hardware address {0}, hardware type {3} and unspecified FQDN/Hostname{1} because ...
  35. DHCP v6 Relay Agent Configuration for %1!s! - State : %2!s! and %3!s! RelayMode : %4!s! Max Hop Count : %5!d! Elapsed-time ...
  36. DHCP will be turned off on this adapter to configure it for NLB. Please specify any necessary gateway or DNS/WINS information ...
  37. DHCP will be turned off on this adapter to configure it for NLB. Please specify any necessary gateway or DNS/WINS information ...
  38. DHCP will not try regular IPv4 address acquisition on interface %1 since the machine is in Connected Standby state and the ...
  39. DHCP will not try regular IPv6 address acquisition on interface %1 since the machine is in Connected Standby state and the ...
  40. DHCP will try regular IPv4 address acquisition on interface %1 due to registry settings even though the machine is in Connected ...
  41. DHCP will try regular IPv4 address acquisition on interface %1 even though the machine is in Connected Standby state since ...
  42. DHCP will try regular IPv6 address acquisition on interface %1 due to registry settings even though the machine is in Connected ...
  43. DHCP will try regular IPv6 address acquisition on interface %1 even though the machine is in Connected Standby state since ...
  44. DHCP: Credentials for DNS update should be configured if secure dynamic DNS update is enabled and the domain controller is ...
  45. DHCPv6 confirmation has been declined because the address was not appropriate to the link or DHCPv6 renew request has a Zero ...
  46. DHCPv6 confirmation has been declined because the address was not appropriate to the link or DHCPv6 renew request has a Zero ...
  47. DHCPV6 Relay agent could not enable multicasting on the socket for the local interface with IP address %1. The data is the ...
  48. DHCPV6 Relay agent could not schedule a task to be executed. This error may have been caused by a memory allocation failure. ...
  49. DHCPV6 Relay agent could not schedule the processing of a packet received on the local interface with IP address %1. The ...
  50. DHCPV6 Relay Agent detected an error on the local interface with IP address %1. The error occurred while the interface was ...
  51. DHCPV6 Relay agent received a packet containing an invalid op-code. The packet has been discarded. It was received on the ...
  52. DHCPV6 Relay Agent was unable to enumerate network events on the local interface with IP address %1. The data is the error ...
  53. DHCPV6 Relay Agent was unable to receive an incoming message on the local interface with IP address %1. The data is the error ...
  54. DHCPV6 Relay Agent was unable to relay a DHCP RELAY FORWARD packet on the local interface with IP address %1; the packet ...
  55. DHCPV6 Relay Agent was unable to relay a DHCP REPLY packet on the local interface with IP address %1; the REPLY was to have ...
  56. DHCPV6 Relay received a packet which was smaller than the minimum size allowed for DHCP packets. The packet has been discarded. ...
  57. DHCPv6 Server is unable to bind to UDP port number %1 as it is used by another application. This port must be made available ...
  58. DHCPv6 Server is unable to bind to UDP port number {0} as it is used by another application. This port must be made available ...
  59. DHCPV6R was unable to request notification of events on the socket for the local interface with IP address %1. The data is ...
  60. DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server. ...
  61. DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server. ...
  62. Diagnostic module %5 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. No resolution was set ...
  63. Diagnostic module %6 (%4) encountered an error while handling scenario %1, instance %2, original activity ID %3. The error ...
  64. Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 ...
  65. Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 ...
  66. Diagnostics cannot be started because digital tuner hardware was not detected. Ensure your hardware is correctly installed, ...
  67. Diagnostics flags were not applied because of invalid combination. At least one of Queries, Notifications or Update should ...
  68. Diagnostics flags were not applied because of invalid combination. At least one of QuestionTransactions or Answers should ...
  69. Diagnostics flags were not applied because of invalid combination. At least one of SendPackets or ReceivePackets should be ...
  70. Diagnostics flags were not applied because of invalid combination. At least one of UdpPackets or TcpPackets should be set ...
  71. Dictates when confirmation should be requested. Confirmation is requested when the ConfirmImpact of the operation is equal ...
  72. did not complete policy processing because a system restart is required for the settings to be applied. Group Policy will ...
  73. did not complete policy processing because the user needs to log on again for the settings to be applied. Group Policy will ...
  74. Did not find the expected folder {0} under the hotfix root folder. This folder is used to store hotfixes that are applicable ...
  75. Differencing virtual hard disks require available space on the hosting volume so that space can be allocated when writes ...