Windows 8

  1. The name %1 is in conflict with a name claimed by the domain %2. To enable this name here it must first be disabled in the ...
  2. The name %1 is not a valid name. Valid names consist of a name and type specified in hex. For example, WINS*20 would represent ...
  3. The name %1 was translated to SID %2 from the trusted forest %3. The domain portion of the SID is not in the list of acceptable ...
  4. The name '%1!ls!' specified is not legal: Name of file or directory object created while the UseRestrictedCharacterSet property ...
  5. The name '%1' does not conform to Internet Domain Name Service specifications, although it conforms to Microsoft specifications. ...
  6. The name '%1' does not conform to Internet Domain Name Service specifications, although it conforms to Microsoft specifications. ...
  7. The name '%1' supplied as the argument to /forest is not the name of a forest. Did you mean '%2'? Adprep has stopped without ...
  8. The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is ...
  9. The name and domain settings of this computer cannot be changed after a certification authority (CA) has been installed. ...
  10. The name cannot be used. Names may not consist entirely of periods and/or spaces, or contain these characters: \/"[]:|<>+=;,?*@ ...
  11. The name of a class must be a schema-name and a class-name separated by an underscore, as in "ContosoDeployment_DataFile". ...
  12. The name of a folder or share involved in migration contains one or more characters that are not valid. {0}. The migration ...
  13. The name of an account was changed: Subject: Security ID: %5 Account Name: %6 Account Domain: %7 Logon ID: %8 Target Account: ...
  14. The name of the current Windows PowerShell host is: '{0}'. The module '{1}' requires the following PowerShell host: '{2}'. ...
  15. The name of the Microsoft Exchange 5.5 server specified in the content source does not match the Exchange server specified ...
  16. The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual ...
  17. The name of the remote server could not be resolved to an IP address. User Action Make sure this computer and the Active ...
  18. The name of this application already exists in the service control manager database either as a service name or as another ...
  19. The name of this computer (%1) does not match the name recorded in the Windows Server directory database (%2). If you have ...
  20. The name of this computer has been changed, but the computer must be restarted for the change to take effect. Active Directory ...
  21. The name of this computer has been changed. You must restart this computer for the name change to take effect before you ...
  22. The name of this computer has been changed. You must restart this computer for the previous name change to take effect before ...
  23. The name of this computer, %1, contains one or more characters that are not allowed. Characters that are not valid include: ...
  24. The name of this computer, %1, does not conform to Internet Domain Name System specifications because it contains extended ...
  25. The name of this computer, %1, is a number. Computer names may not be numbers. You must rename this computer before you can ...
  26. The Name Query Response could not be sent due to an error. This error is often caused by a problem with the NetBIOS over ...
  27. The name registration packet that was just received has too many addresses. The maximum number of addresses for a multi-homed ...
  28. The Name Registration Response could not be sent due to an error. This error was encountered by the Name Challenge Thread. ...
  29. The Name Release Response could not be sent due to an error. This error is often caused by a problem with the NetBIOS over ...
  30. The Name Resolution Policy Table (NRPT) stores configuration settings for DNS security (DNSSEC) and DirectAccess on DNS client ...
  31. The name specified for the integration service is not valid. Use wild cards or specify one of the valid integration service ...
  32. The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the ...
  33. The name suffix index specified using the /ToggleSuffix command line argument is outside the range of name indices listed ...
  34. The name suffix that you typed already exists in the specified forest. In the list of existing suffixes, the routing status ...
  35. The name suffix that you typed is a child of an existing excluded name suffix. This condition is redundant and is not allowed. ...
  36. The name translation for a new group member failed because: %s This may be due to a damaged trust with the other domain. ...
  37. The name used to access to the cluster is not currently available. To connect now try using a cluster node name or any other ...
  38. The name you entered is too long. Names cannot contain more than 64 characters. This name will be shortened to 64 characters. ...
  39. The name you specified for the Remediation server group is either not valid, or a Remediation server group with that name ...
  40. The name you specified for the remote RADIUS server group is either not valid, or a remote RADIUS server group with that ...
  41. The name, %1, is in the wrong format. It has not been put in the WINS database. Check to see if you have a space before the ...
  42. The names of some imported commands from the module '{0}' include unapproved verbs that might make them less discoverable. ...
  43. The names of the current domain and the root domain are the default user principal name (UPN) suffixes. Adding alternative ...
  44. The namespace %1 using content provider %2 could not be registered because a namespace by that name already exists. The namespace ...
  45. The namespace %1 using content provider %2 could not be registered because the content provider is not registered. The namespace ...
  46. The namespace administrator cannot enable access-based enumeration of DFS folders or expand the namespace to more than 5,000 ...
  47. The namespace cannot be deleted on the failover cluster. You must use the Failover Cluster Manager snap-in to delete the ...
  48. The namespace name is not unique for the server. You must go back to choose a new namespace name, or change the namespace ...
  49. The namespace name is not unique in the domain in which the namespace server was created. You must go back to choose a new ...
  50. The namespace path is shared using the same shared folder name as you entered. The existing shared folder will be used instead. ...
  51. The namespace server is in a workgroup. The namespace server must be in a domain before you can configure replication on ...
  52. The namespace server is unavailable to clients and no further diagnostic information can be gathered. If the server is a ...
  53. The namespace {0} on {1} cannot be detected. {2} Do you want to forcibly remove the namespace server? If you forcibly remove ...
  54. The NAP service has started. NAP has the following information for this computer: Computer name is %1. Domain status is: ...
  55. The NAP service has started. NAP has the following information for this computer: Computer name is %1. Domain status is: ...
  56. The NAP-Capable Computers condition specifies that connecting computers either are or are not capable of participating in ...
  57. The NAS Identifier condition specifies a character string that is the name of the network access server (NAS). You can use ...
  58. The NAS IP Address condition specifies a character string that is the IP address of the NAS. You can use pattern matching ...
  59. The NAS IPv6 Address condition specifies a character string that is the IPv6 address of the NAS. You can use pattern matching ...
  60. The NAS Port Type condition specifies the type of media used by the access client, such as analog phone lines, ISDN, tunnels ...
  61. The navigation nodes that define the scope of this view are no longer available. By default, {0} navigation node is selected ...
  62. The NBT Connection performance object consists of counters that measure the rates at which bytes are sent and received over ...
  63. The neighbor on interface %1 was removed because no message has been received within the timeout interval Neighbor ID: %3 ...
  64. The NetBEUI performance object consists of counters that measure data transmission for network activity which conforms to ...
  65. The NetBIOS computer name %1 is a number. The name may not be a number. You must have at least one non-numeric character ...
  66. The NetBIOS gateway has been configured to access the network but there are no network adapters available. Remote clients ...
  67. The NetBIOS name contains characters that are not allowed. Characters that are not valid include: " / \ : | < > + = ; , ? ...
  68. The NetBIOS name is invalid. It may be too long or it may contain one or more invalid characters. Valid names are 0 to 15 ...
  69. The NetBIOS name is invalid. It may be too long or it may contain one or more invalid characters. Valid names are 1 to %1 ...
  70. The NetBIOS name is invalid. It may be too long or it may contain one or more invalid characters. Valid NetBIOS names are ...
  71. The NetBIOS name of the computer contains characters that are not allowed. Characters that are not allowed in NetBIOS names ...
  72. The NetBIOS name of the computer is limited to %1!d! bytes, which is %2!d! characters in this case. The NetBIOS name will ...
  73. The NetBIOS name of the computer is limited to 15 bytes, which is 15 characters in this case. The NetBIOS name will be shortened ...
  74. The NetBIOS name of the computer name contains illegal characters. Illegal characters include " / \ : | < > + = ; , ? and ...
  75. The Netbios Name Scope has a component longer than 63 characters. Each label in the Scope cannot be longer than 63 bytes. ...