Windows 8.1

  1. A client has successfully authenticated with the hosted network. Interface GUID: %1 Interface description:%2 Network SSID: ...
  2. A client made a DirSync LDAP request for a directory partition that included attributes in the Read-Only DC Filtered Set. ...
  3. A client made a DirSync LDAP request for a directory partition. Access was denied due to the following error. Directory partition: ...
  4. A client request contained a version number that is not valid and cannot be processed. The following information is available: ...
  5. A client restore media creation task is already running in the background. Please wait until that task finishes, and try ...
  6. A cloud requested is not present; review the configured IPv6 addresses and verify there are addresses of appropriate scope.%0 ...
  7. A CLR object returned by the cmdlet contained very deeply nested objects. Sub-objects beyond maximum allowed depth will be ...
  8. A cluster address makes it possible for AD RMS clients to communicate with this cluster over the network. We recommend that ...
  9. A cluster can be administered by connecting to any of the member servers. The cluster connection point identifies which server ...
  10. A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different ...
  11. A cluster connection cannot be established at this time. The nodes are either all down, or the running nodes have not achieved ...
  12. A Cluster is composed of two or more ComputerSystems, operating together. A ComputerSystem may participate in multiple Clusters. ...
  13. A cluster object was passed that is not valid. Run the command again and specify an object that represents a cluster group ...
  14. A cluster shared volume has a node hosting the resource. This lists the cluster node hosting cluster shared volume resource. ...
  15. A cluster shared volume has a resource assoicated with it. This lists the cluster resource which is the cluster shared volume. ...
  16. A cluster was found to be used by a file but not marked as used in the volume bitmap. The file reference number is 1!0I64x!. ...
  17. A clustered role with the same name already exists in the cluster. Use a different name for the clustered role, or rename ...
  18. A cmdlet threw an exception after calling ThrowTerminatingError. The first exception was "{0}" with stack trace "{1}". The ...
  19. A codec is required to play this file. To determine if this codec is available to download from the web, click Web Help.%0 ...
  20. A column having the specified property set and PID already exists. The application's configuration has been corrupted. Reinstall ...
  21. A COM call (IID: %1, method index: %2!d!) to an ASTA (thread %3!d!) was blocked because the call chain originated in or passed ...
  22. A COM call to an ASTA was blocked because the call chain originated in or passed through another ASTA. This call pattern ...
  23. A COM+ service (such as Queued Components or Compensating Resource Manager) failed an ApplicationFree event. This is not ...
  24. A COM+ service (such as Queued Components or Compensating Resource Manager) failed an ApplicationLaunch event. If this problem ...
  25. A COM+ service (such as Queued Components or Compensating Resource Manager) failed an ApplicationShutdown event. This is ...
  26. A COM+ service (such as Queued Components or Compensating Resource Manager) failed in its PauseProcess method. The service ...
  27. A COM+ service (such as Queued Components or Compensating Resource Manager) failed in its ResumeProcess method. The service ...
  28. A COM+ service (such as Queued Components or Compensating Resource Manager) failed to start. The service GUID and HRESULT ...
  29. A command is referenced that is not allowed. Only convertfrom-* commands are supported in restricted language mode or a Data ...
  30. A command is required to add a parameter. A command must be added to the Windows PowerShell instance before adding a parameter. ...
  31. A command that prompts the user failed because the host program or the command type does not support user interaction. The ...
  32. A command that prompts the user failed because the host program or the command type does not support user interaction. Try ...
  33. A command was sent to the Trusted Platform Module (TPM) successfully resetting the TPM lockout logic. This event is generated ...
  34. A Common Name is a (possibly ambiguous) name by which the group is commonly known in some limited scope (such as an organization) ...
  35. A communication point from which data can be sent or received. ProtocolEndpoints link system or computer interfaces to LogicalNetworks. ...
  36. A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application ...
  37. A component is typically contained by a physical package, such as a chassis or card. The CIM_PackagedComponent association ...
  38. A component of Windows Media Player is out-of-date. If you are running a pre-release version of Windows, try upgrading to ...
  39. A component on the server did not respond in a timely fashion. This caused the cluster resource '%1' (resource type '%2', ...
  40. A computer account was changed. Subject: Security ID: %5 Account Name: %6 Account Domain: %7 Logon ID: %8 Computer Account ...
  41. A computer account was created. Subject: Security ID: %4 Account Name: %5 Account Domain: %6 Logon ID: %7 New Computer Account: ...
  42. A computer account was deleted. Subject: Security ID: %4 Account Name: %5 Account Domain: %6 Logon ID: %7 Target Computer: ...
  43. A computer account with that name already exists in the directory service. Please enter a different name for this computer. ...
  44. A Computer Name targeting item allows a preference item to be applied to computers or users only if the computer's name matches ...
  45. A computer object for "{0}" was found in domain "{1}". This may indicate that the name is already in use as a cluster node ...
  46. A computer QoS policy "%2" potentially conflicts with other QoS policies. See documentation for rules about which policy ...
  47. A computer QoS policy "%2" was ignored because the application path cannot be processed. The application path may be totally ...
  48. A computer QoS policy exceeds the maximum allowed name length. The offending policy is listed under the computer-level QoS ...
  49. A computer QoS policy has a zero length name. The offending policy is listed under the computer-level QoS policy root key, ...
  50. A computer restart is required before installing the Connector. Please save your data, close your applications, restart your ...
  51. A computer restart is required to complete the system state recovery operation. Press %1 to restart the computer now. %1 ...
  52. A computer with this name is already connected to server. Rename this computer and then try to connect this computer to the ...
  53. A ComputerSystem can aggregate another ComputerSystem. This association can be used to model MPP Systems with workstation ...
  54. A concrete version of Collection. This class represents a generic and instantiable collection, such as a group of ComputerSystems ...
  55. A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job. ...
  56. A condition has occurred that indicates this COM+ application is in an unstable state or is not functioning correctly. Assertion ...
  57. A conditional statement which evaluates to TRUE or FALSE to determine whether the associated software element should is installed. ...
  58. A conditional statement which evaluates to TRUE or FALSE to determine whether the Level value should be applied to the associated ...
  59. A configuration issue with your default browser is preventing the browser from launching. Ensure that your default browser ...
  60. A configuration registry node representing a driver service entry was ill-formed and did not contain required value entries. ...
  61. A conflict has been detected between two drivers which claimed equivalent DMA channels. Driver %2, with device , claimed ...
  62. A conflict has been detected between two drivers which claimed equivalent IRQs. Driver %2, with device , claimed an interrupt ...
  63. A conflict has been detected between two drivers which claimed two overlapping Io port regions. Driver %2, with device , ...
  64. A conflict has been detected between two drivers which claimed two overlapping memory regions. Driver %2, with device , claimed ...
  65. A conflict was detected between the phase 1 and phase 2 authentication sets. When preshared keys are used in phase 1, there ...
  66. A conflict was detected in the list of include/exclude APIs. Do not specify the same API in both the include list and the ...
  67. A conflict was found on the receiving device or computer. For more information, contact the manufacturer of your device. ...
  68. A CONNECTACK message with transaction id %1 was received from partner server : %2 for failover relationship: %3 with reject ...
  69. A CONNECTACK message with transaction id %1 was sent to partner server : %2 for failover relationship: %3 with reject reason: ...
  70. A CONNECTACK message with transaction id {0} was received from partner server : {1} for failover relationship: {2} with reject ...
  71. A CONNECTACK message with transaction id {0} was received from partner server : {1} for failover relationship: {2} with reject-reason: ...
  72. A CONNECTACK message with transaction id {0} was sent to partner server : {1} for failover relationship: {2} with reject ...
  73. A CONNECTACK message with transaction id {0} was sent to partner server : {1} for failover relationship: {2} with reject-reason: ...
  74. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection ...
  75. A connection attempt failed because the connected party did not properly respond after a period of time, or the established ...