Windows 8

  1. The HCAP server did not get a response from Network Policy Server. HCAP client host name: %1 HCAP client IP address: %2 Request ...
  2. The HCAP User Groups condition specifies the Host Credential Authorization Protocol (HCAP) user groups required to match ...
  3. The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification. ...
  4. The Health Policies condition restricts the policy to only clients that meet the health criteria specified in the health ...
  5. The Health Registration Authority (HRA) server cannot acquire health certificates on behalf of Network Access Protection ...
  6. The Health Registration Authority (HRA) server cannot process health certificate requests. Network Access Protection (NAP) ...
  7. The Health Registration Authority (HRA) server should be configured with a validity time for health certificates of at least ...
  8. The Health Registration Authority (HRA) server should be configured with at least one valid certification authority (CA). ...
  9. The Health Registration Authority (HRA) server should have all required Internet Information Services (IIS) components installed. ...
  10. The Health Registration Authority denied a request. The Network Policy Server has indicated that the client should be given ...
  11. The Health Registration Authority denied the certificate request with the correlation-id %1 at %2 for (principal: %3). Either ...
  12. The Health Registration Authority denied the request with the correlation-id %1 at %2 (principal: %3) because the request ...
  13. The Health Registration Authority encountered an error processing the response for the request with the correlation-id %1 ...
  14. The Health Registration Authority encountered an internal error (%1). Restart the Health Registration Authority website in ...
  15. The Health Registration Authority failed to validate the certificate request against the HRA configuration. The Health Registration ...
  16. The Health Registration Authority has approved the request with the correlation-id %1 at IP address %2 (principal: %3). The ...
  17. The Health Registration Authority has approved the request with the correlation-id %1 at IP address %2 (principal: %3). The ...
  18. The Health Registration Authority has denied the request with the correlation-id %1 at IP address %2 (principal: %3). The ...
  19. The Health Registration Authority is mis-configured or can not read its configuration, stopping Health Registration Authority. ...
  20. The Health Registration Authority received a clear session from %1. Verify the Health Registration Authority configuration ...
  21. The Health Registration Authority was unable to acquire a certificate for request with the correlation-id %1 at %2 (principal: ...
  22. The Health Registration Authority was unable to acquire a certificate for request with the correlation-id %1 at %2 (principal: ...
  23. The Health Registration Authority was unable to connect to the Certification Authority to remove expired records. The Certification ...
  24. The Health Registration Authority was unable to read the request from the host at %1 because of inconsistencies with the ...
  25. The Health Registration Authority was unable to validate the request with the correlation-id %1 at IP address %2 (principal: ...
  26. The Health Registration Authority was unable to validate the request with the correlation-id %1 at IP address %2 (principal: ...
  27. The Health Registration Authority was unable to validate the request with the correlation-id %1 at IP address %2 (principal: ...
  28. The Health Registration Authority was unable to validate the request with the correlation-id %1 at IP address %2 (principal: ...
  29. The Health Registration Authority was unable to validate the request with the correlation-id %1 at IP address %2 (principal: ...
  30. The Health Registration Authority was unable to validate the request with the correlation-id %1 at IP address %2 (principal: ...
  31. The helper class: {helperclassname} failed while trying to diagnose the problem. It returned the following error code: {errorcode}. ...
  32. The hexadecimal value you entered is not valid. A valid hexadecimal value may start with 0x, and must contain even number ...
  33. The hierarchies of the trusted publishing domain being imported and this AD RMS cluster do not match. Find a trusted publishing ...
  34. The hierarchies of the trusted user domain being imported and this AD RMS cluster do not match. Find a trusted user domain ...
  35. The High Precision Event Timer failed to deliver message signalled interrupts. The operating system will fall back to line ...
  36. The highly available file server name "{0}" is not a valid NetBIOS name. NetBIOS names must contain only alphanumeric characters. ...
  37. The highly available file server name cannot be the same as the cluster management or cluster node name. Enter a unique name ...
  38. The history of frames is inconsistent. Pointer ids, types, source devices don't match, or frame ids are not unique, or timestamps ...
  39. The home folder was set to the following shared folder: %1 The shared folder already exists. Because the folder is at the ...
  40. The host address is not a properly formed IPv6 address per RFC 2373 section 2.2. Examples of correctly formed IPv6 addresses ...
  41. The host HostRecordTTL property sets the value on DNS record (A/AAAA) that network name registers in DNS. TTL value on DNS ...
  42. The host name '%1' of the metadata address was not in the list of acceptable host names specified when the metadata object ...
  43. The host name label of the new primary name is longer than %1!d! characters. The new NetBIOS computer name will be truncated ...
  44. The host name label of this new alternate name is longer than %1!d! characters. If this name is made primary the new NetBIOS ...
  45. The host name pattern "%1" is invalid and it will be ignored. Host name patterns must not be empty and they can contain at ...
  46. The HostRecordTTL property for network name '{0}' is set to {1} ( {2} minutes). For local clusters the suggested value is ...
  47. The HostRecordTTL property for network name '{0}' is set to {1} ( {2} minutes). For multi-site clusters the suggested value ...
  48. The HTTP Support feature allows you to expose a queue to the internet such that applications can send messages to the queue ...
  49. The Hyper-V authorization policy was successfully restored, but you must restart the Virtual Machine Management Service and ...
  50. The Hyper-V configuration cannot be validated because node '{0}' is not available. Please ensure all cluster nodes are online ...
  51. The Hyper-V integration services have been successfully installed. You must restart your system to complete the installation. ...
  52. The Hyper-V integration services have been successfully removed. You must restart your system to complete the removal. Do ...
  53. The Hyper-V Replica Broker "{0}" is not enabled to accept replication data. Enable this Replica Broker as a Replica server ...
  54. The Hyper-V Replica Broker role is in a failed state. Due to this, replication will be impacted. Ensure that the Hyper-V ...
  55. The Hyper-V role is not installed on the destination host. Add the Hyper-V role on that host and then run this cmdlet again. ...
  56. The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) ...
  57. The hypervisor could not perform the operation because the object or value was either already in use or being used for a ...
  58. The IAS/RADIUS server has passed an invalid value to the server running Routing and Remote Access for the following RADIUS ...
  59. The ICMP performance object consists of counters that measure the rates at which messages are sent and received by using ...
  60. The ICS_IPV6 was unable to allocate %1 bytes of memory. This may indicate that the system is low on virtual memory, or that ...
  61. The ID must: (1) start with "ad://ext/", (2) be followed by 1 to 32 characters, (3) not contain word spaces, \, *, ?, ", ...
  62. The ID of the assessment to retrieve. If this parameter is not specified, retrieve all parameters from the specified harness. ...
  63. The ID of the differencing disk does not match the ID of the parent virtual hard disk. If you continue, this action might ...
  64. The identifier name {0} cannot be processed due to the inability to differentiate between the following enumerator names: ...
  65. The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM ...
  66. The Identity Mapping Setup Wizard cannot access Active Directory or the compatible directory service you specified. To continue, ...
  67. The identity of the remote computer was verified through a connection broker, which was verified by using a server certificate ...
  68. The identity of the remote computer was verified through a connection broker, which was verified by using a server certificate. ...
  69. The identity of the remote computer was verified through a connection broker, which was verified by using Kerberos protocol. ...
  70. The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute ...
  71. The Identity Type condition restricts the policy to only clients that can be identified through the specified mechanism, ...
  72. The IE settings are ambiguous. We don't know whether we should directly access RPC proxy or use HTTP proxy. You can use -R ...
  73. The IIS configuration is not valid. Could not find the binding for the HTTPS port. The RD Web Access certificate is not configured. ...
  74. The IIS received the request. However, an internal error (HTTP Error 500.0 - Internal Server Error) occurred during the processing ...
  75. The IKEEXT service hosts the Internet Key Exchange (IKE) and Authenticated Internet Protocol (AuthIP) keying modules. These ...