Windows 8.1

  1. The user account or password entered is invalid. If you entered a domain account, make sure the name is prefixed with the ...
  2. The user account that you selected is an administrator account. Administrators have full access permissions for Anywhere ...
  3. The user account that you selected is an administrator. Administrators have full access permissions on all shared folders ...
  4. The user account that you selected is an administrator.Administrators have full access permissions on all shared folders ...
  5. The user account that you use to upgrade AD RMS must be a member of the local Administrators group on the AD RMS server and ...
  6. The user account {0} could not be assigned to a pooled virtual desktop because the user does not have access to the pooled ...
  7. The user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the ...
  8. The user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the ...
  9. The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made at %1. Any ...
  10. The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made on %1 at ...
  11. The user agent string is what the browser sends to visited servers to identify itself. It is often used to keep Internet ...
  12. The user agent string was not specified or contains invalid characters. Specify a user agent which is not empty and does ...
  13. The user attempted the following repair option: {repairoption}. This was recommended by the following helper class: {helperclassname}. ...
  14. The user attempted to authenticate using a certificate with an Extended Key Usage or Issuance Policy that is not allowed ...
  15. The user attempted to connect through either a phone number or calling station that does not match the Caller ID listed for ...
  16. The user attempted to force close the files on a redirected drive, but there were opened directories on the drive, and the ...
  17. The user attempted to force close the files on a redirected drive, but there were opened files on the drive, and the user ...
  18. The user authentication plug-in "%1" has been configured. The configuration will take effect after the RD Gateway service ...
  19. The user authentication plug-in could not be imported to the RD Gateway server "{0}" because it is not installed on the server. ...
  20. The user authorization plug-in could not be imported to the RD Gateway server "{0}" because it is not installed on the server. ...
  21. The user can choose to allow or not allow applications to show the Encoder Configuration Dialog Box by selecting the appropriate ...
  22. The user can try the other repair options given during diagnosis. If all repair options have been attempted, the user may ...
  23. The user connected to port %1 has been disconnected because the following internal authentication error occurred in the third ...
  24. The user connected to port %1 has been disconnected because there was a transport-level error during the authentication conversation. ...
  25. The user could not be authenticated using Challenge Handshake Authentication Protocol (CHAP). A reversibly encrypted password ...
  26. The user could not change his or her password because the new password did not meet the password requirements for this network. ...
  27. The User Count Check detected a condition in your environment that is out of compliance with the licensing policy. This server ...
  28. The User Count Check detected a condition in your environment that is out of compliance with the licensing policy. This server ...
  29. The user creating the cluster requires the 'Create Computer Object' permission on the container where computer objects are ...
  30. The user disk quota information is unusable. To ensure accuracy, the file system quota information on the device %1 with ...
  31. The user does not have permission to run the scan process. PSP Identifier (GUID): %1. Submitting Username: %2. Failure: %3. ...
  32. The User Exclusion list defines which rights account certificates (RACs) are not trusted by this cluster. Click Exclude RAC ...
  33. The user exclusion policy is disabled currently. Please run Update-RmsCluster cmdlet to refresh the cluster and try again. ...
  34. The user group has been created, but it has not been assigned the necessary permissions. Delete the group and create it again. ...
  35. The user has chosen not to start People Near Me by declining the privacy dialog. The privacy will appear the next time the ...
  36. The user in domain %2 was not able to authenticate via the Kerberos protocol in domain %1. %2 may trust %1 but the trust ...
  37. The user is approaching the threshold for maximum number of failed logon attempts. Once the maximum limit is reached the ...
  38. The user load quota of %1 requests per %2 seconds has been exceeded. Send future requests at a slower rate or raise the quota ...
  39. The user locale "%1" (specified by the UserLocale element) is not a supported locale name or is not installed on the system. ...
  40. The user logon name %1 contains one or more of the following illegal characters: / \ : ; | = , + ? < > " If you continue ...
  41. The user logon name %2 contains one or more of the following illegal characters: / \ : ; | = , + ? < > " If you continue ...
  42. The user logon name you have chosen is already in use in this enterprise. Choose another logon name, and then try again. ...
  43. The user mailbox will be retained for the period specified in the mailbox retention policy on the Exchange Server (default ...
  44. The user name %1 specified in registry (%2) does not map to a real user name. The entry is ignored. It must have a valid ...
  45. The user name %1 specified in registry (%2) is not valid, winerror %3. The entry is ignored. It must have a valid username ...
  46. The user name (%1) in the certificate enrollment request does not match the user name (%2) specified for OTP authentication. ...
  47. The user name and password are either incorrect or are for a user who does not have read permission to the remote shared ...
  48. The user name and password for this connection cannot be saved for use by all users. As a result, Internet Connection Sharing ...
  49. The user name and password for this connection were not saved for use by all users. As a result, Internet Connection Sharing ...
  50. The user name being used to perform the backup is not recognized by the computer that contains the remote shared folder. ...
  51. The user name can't contain the @ symbol. Want this person to sign in with an email address instead? Create a Microsoft account. ...
  52. The user name can't contain the @ symbol. Want to sign in with an email address instead? Create an account using a Microsoft ...
  53. The user name entered in the Administrator field must be qualified with a domain or computer name. In the unattended removal ...
  54. The user name entered in the SourceUsername field must be qualified with a domain or computer name. In the unattended setup ...
  55. The user name is not valid. A user name can contain a maximum of 20 characters and must not consist entirely of periods or ...
  56. The user name mapping cannot be read. Check that the database, view, and column names are correct, that the Notes database ...
  57. The user name of the proxy authentication credential parameter value is invalid. It must be in domain\username or [email protected] ...
  58. The user name of the proxy authentication credential parameter value is invalid. When the proxy authentication scheme is ...
  59. The user name of the replication account must be qualified by a domain or computer name. Example: COMPUTER1\UserName Example: ...
  60. The user name or password for your domain name service provider is not correct. Double-check your user name and password, ...
  61. The user name or password is incorrect. Verify that CAPS LOCK is off, and then retype your user name and password. If you ...
  62. The user name that is used by the access client in the RADIUS message. This attribute is a character string that typically ...
  63. The user name you typed is the same as the user name you logged in with. That user name has already been tried. A domain ...
  64. The user or computer does not have permission to access the network on this day at this time. To change the day and time ...
  65. The user or group name is invalid in specified user or group list. Check all of names either are a valid e-mail address ([email protected]) ...
  66. The user or group of {0} will not have any right after the custom rights are reset. Therefore, the user or group needs to ...
  67. The user or group that you specify will be able to attach a server to the RODC account that you are creating now and complete ...
  68. The user reset all customizations for their user locale "%1" (specified by the UserLocale element) to the system default. ...
  69. The user selected the following repair option: {repairoption}. The repair option required the following Security Identifier ...
  70. The user specified a username/password/authority on a local connection. The user must use a blank username/password and rely ...
  71. The user specified an invalid cryptographic mode. If this is the licensing cluster, it must be provisioned using the same ...
  72. The user tried to apply an unattended XML file (%1) in an unsupported format. Reason: %3 (Line %2). The system has not been ...
  73. The user was authenticated as %1 by the third party security host module but was authenticated as %2 by the RAS security. ...
  74. The user who is running validation does not have permissions to create computer objects in the '{0}' domain in the '{1}' ...
  75. The user will not have to change their password at the next logon because the following error occurred. %1 If you want them ...