Windows 8.1

  1. A registry value was changed while installing the following component into a COM+ Application. If you are experiencing activation ...
  2. A registry value was modified. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Object: Object Name: ...
  3. A remote access client can initiate connections to other networks, either through a virtual private network (VPN) or dial-up ...
  4. A remote access/VPN server enables remote clients to connect to a network through either a dial-up connection or a secure ...
  5. A Remote Desktop connection authorization policy (RD CAP) allows you to specify the users who can connect to this RD Gateway ...
  6. A Remote Desktop resource authorization policy (RD RAP) allows you to specify the network resources (computers) that users ...
  7. A Remote Desktop Services deployment already exists in the server pool. Select an RD Connection Broker on which to create ...
  8. A Remote Desktop Services deployment does not exist in the server pool. To create a deployment, run the Add Roles and Features ...
  9. A Remote Desktop Services deployment does not exist on {0}. This operation can be performed after creating a deployment. ...
  10. A Remote Desktop Services deployment requires certificates for server authentication, single sign-on, and establishing secure ...
  11. A Remote Desktop Services session-based desktop deployment does not exist on {0}. This operation can be performed only after ...
  12. A Remote Desktop Services virtual machine-based desktop deployment does not exist on {0}. This operation can be performed ...
  13. A Remote Desktop Services virtual machine-based desktop deployment does not exist on {0}. This operation can be performed ...
  14. A Remote Desktop session has been detected. The {0} cannot execute all necessary test content over a Remote Desktop session. ...
  15. A remote print driver package operation %1 failed with error code %2, server name %3. This was most likely caused by an unexpected ...
  16. A Remote Procedure Call (RPC) was attempted. Subject: SID: %1 Name: %2 Account Domain: %3 LogonId: %4 Process Information: ...
  17. A remote procedure call running locally took too long to complete. The client has likely cancelled this call. Additional ...
  18. A remote WINS requested the update of the version stamp of a record, but the record could not be found. Check to see if the ...
  19. A RemoteApp program with alias '{0}' already exists in collection '{1}'; specify a different alias or collection, and then ...
  20. A reparse point was detected under the shared folder. The reparse point and all files under it will not be migrated as part ...
  21. A Replay attack might be underway. Monitor the server for signs of an attack. If an attack is detected, take mitigation measures ...
  22. A replay attack was detected. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Credentials Which ...
  23. A replica server mirrors update approvals, settings, computers and groups from its parent. Updates can be approved only on ...
  24. A replica server mirrors update approvals, settings, computers, and groups from its parent. Updates can be approved only ...
  25. A replicated folder must be shared before it can be published. To modify the shared folder name and permissions, click Edit. ...
  26. A replication connection was created from the following source directory service to the local directory service. Source directory ...
  27. A replication group can be used to synchronize the folder targets of the folder you just created. Do you want to create a ...
  28. A replication operation that began at the following start time has been taking longer than expected to complete. As a result, ...
  29. A request failed from client realm %1 for a ticket in realm %2. This failed because a trust link between the realms is non ...
  30. A request for a callback on a MTA thread failed. This should happen only if the system is in an extremely unstable state. ...
  31. A request for assistance with an error could not be sent because the email address of the recipient is blank. Details: Error: ...
  32. A request for assistance with an error was sent. Details: Error: %1 Email sent to: %2 Email subject: %3 User: %4\%5 File ...
  33. A request message from another BranchCache client was dropped because it was not valid. Remote client address: %1 Error: ...
  34. A request on persistent/resilient handle failed because the handle was invalid or it exceeded the timeout. Status: %7 Type: ...
  35. A request timed out because there was no response from the server. Server name: %6 Session ID:%3 Tree ID:%4 Message ID:%2 ...
  36. A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use. ...
  37. A request to allocate an ephemeral port number from the global UDP port space has failed due to all such ports being in use. ...
  38. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous ...
  39. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket ...
  40. A request to start the update has been ignored because the update is already in progress or is scheduled on one or more content ...
  41. A request was made to authenticate to a wired network. Subject: Security ID: %2 Account Name: %3 Account Domain: %4 Logon ...
  42. A request was made to authenticate to a wireless network. Subject: Security ID: %2 Account Name: %3 Account Domain: %4 Logon ...
  43. A request was made to authenticate to a wireless network. Subject: Security ID: %2 Account Name: %3 Account Domain: %4 Logon ...
  44. A request was made with a payload that was too big or to a URI that was too long. Parameter Reference Context: %1 RequestId: ...
  45. A request was received by the RPC server on %1 endpoint from %2 but there is no provider registered for %1 endpoint. This ...
  46. A request was received by the RPC server on %1 endpoint from %2. The request was denied because of the security permissions ...
  47. A request was received by the RPC server on %1 endpoint from %2. The request was received on an unauthenticated channel, ...
  48. A request was received by the RPC server on %1 endpoint from %2. The request was received on authenticated channel but the ...
  49. A request with a session key that is not valid was detected; this can be an attempt at a cross-site request forgery attack. ...
  50. A request with a user name that is not valid was detected. The user name does not match the user name that created the session; ...
  51. A requested type of logon (e.g., Interactive, Network, Service) is not granted by the target system's local security policy. ...
  52. A required certificate is not within its validity period when verifying against the current system clock or the timestamp ...
  53. A required certificate is not within its validity period when verifying against the current system clock or the timestamp ...
  54. A required component "^1" cannot be located or correctly initialized. If this problem persists after restarting, contact ...
  55. A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell ...
  56. A required parent feature may not be enabled. You can use the /enable-feature /all option to automatically enable each parent ...
  57. A required service could not be started. Make sure the Windows Media Center services are enabled. If the problem persists, ...
  58. A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, ...
  59. A reservation ensures that a DHCP client is always assigned the same IP address. To add a reservation, on the Action menu, ...
  60. A resource group that was associated with this policy has been deleted. For this policy to be functional, you must associate ...
  61. A resource group that was associated with this policy has been deleted. For this policy to be functional, you must associate ...
  62. A resource manager performed recovery and called ReenlistmentComplete indicating that recovery was complete. However, there ...
  63. A resource of type '{0}' already exists in the new cluster, and only one instance of this resource type is allowed in the ...
  64. A resource property describes a characteristic of a resource, such as a file or a folder. It is used to define target resources ...
  65. A resource property list is used to categorize resource properties, such as showing a smaller set in a classification UI ...
  66. A resource provided by plug-in %1 was rejected because its alias was too long. To remove or rename the resource, see the ...
  67. A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the ...
  68. A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation. ...
  69. A resource with the same name already exist on the cluster. Resource names are unique in the cluster. Use a different name ...
  70. A restart is pending because of a feature installation failure. Restart the computer, and then review the migration and Server ...
  71. A restart is pending on one or more nodes. Deployment tasks cannot be completed until all nodes are restarted. Do you want ...
  72. A restart of the Server service (also called the LanmanServer service) is required to complete migration. Restart this service ...
  73. A restore map already exists for the specified component. You can only specify a restore map when performing a full restore. ...
  74. A restored database file exists but it is older than the existing database file. RD Licensing service will startup with the ...
  75. A reverse lookup zone translates IP addresses to DNS names. Reverse lookup zones are usually necessary only if programs require ...