Sorry We Didn t Recognize Your User Name or Password Please Try Again

The mistake message 'Your credentials did not work' appears when you lot fail to connect to the remote system using Remote Desktop connectedness. This error is often caused past Windows policies that prevent incoming RDP connections, or just your system's username. Dealing with this detail fault tin be infuriating as the error isn't in the credentials but rather somewhere else. Such an mistake message might appear even if you are entering the correct credentials, thus, making it an ordeal.

If you are receiving the error message after installing a fresh copy of Windows 10, then you lot are not the only victim. Many users depend on Remote Desktop Connections and such errors are commonly a nightmare to them, however, do not worry as you volition be able to get over the effect after following this guide.

What causes the 'Remote Desktop Your Credentials Did non Work' Error Message on Windows x?

The following factors are frequently institute to exist the crusade of the said error bulletin —

Username Alter: Sometimes, when you freshly install Windows or rename your current user account, information technology tin can cause such an effect. Really, when you change your username, it doesn't become changed for the Remote Desktop Connection due to which the error message is generated.
Windows Policy: In some cases, the fault bulletin is considering of a Windows Security Policy which prevents non-admin users from signing in.

At present that you know the causes of the error message, yous tin follow the solutions provided down below to resolve your effect. Please make sure y'all follow the given solutions in the same order as provided.

Solution 1: Reverting Username

As nosotros accept mentioned, the error bulletin is sometimes caused because the user you are trying to connect from does not exist on the Remote Desktop server. This happens when you lot effort to change your username or install a fresh copy of Windows. Changing your username does not necessarily change it for Remote Desktop Connectedness and thus, your credentials will exist incorrect as the user is not on the server. Thus, to isolate the upshot, yous will accept to revert to the username that y'all had been using prior to the appearance of the error bulletin.

Solution 2: Editing Windows Security Policy

There is a Windows Security Policy for Remote Desktop Connexion that does not allow non-Admin users to log in using RDP. Thus, if you want to login using a not-admin user account, y'all will accept to grant the remote desktop users access. Here is how to practise it:

Press Windows Fundamental + R to open up the Run dialog box.
Type in 'secpol.msc' and press Enter. This will open up the Local Security Policy window.
Expand Local Policies and so select User Rights Consignment.
On the right-paw side, locate and double-click either 'Allow log on through Remote Desktop Services' or 'Permit log on through Last Services'.
Click Add User or Group and then type in Remote Desktop Users.

Adding User to Grant Access
Click OK, hit Apply and and then click OK again.

Assuasive Remote Desktop Users Admission
Restart your system for the change to take consequence.
Check if it isolates the outcome.

Solution 3: Editing Local Group Policy

If the to a higher place-mentioned solutions exercise non piece of work out for you, you lot tin attempt to isolate the issue by modifying a few Local Group Policies. Basically what you volition have to do is requite a set of Credential Delegation policies a specific value which volition most likely fix your issue. Here'south how to practice it:

Press Windows Cardinal + R to open Run.
Blazon in 'gpedit.msc' to open the Local Group Policy Editor.

Afterward, navigate to the post-obit path:

Computer Configuration > Administrative Templates > System > Credentials Delegation

Double-click the 'Let delegating default credentials with NTLM-only server hallmark' policy to edit information technology.
Set it to Enabled and then click Show.

Editing Local Group Policy
Double-click nether Value, type in TERMSRV/* and so click OK.

Adding Server to the Listing

Exercise the same for the post-obit policies besides:

Permit delegating default credentials Permit delegating saved credentials Permit delegating saved credentials with NTLM-but server hallmark

Finally, close the Local Group Policy Editor and restart your system.
Cheque if the event persists.

Solution four: Editing Registry

In some cases, making some changes in the registry might get rid of the error. Therefore, in this step, nosotros will be changing some configurations in the registry. For that:

Press "Windows" + "R" to open the registry.
Type in "Regedit" and press "Enter".

Opening the Registry Editor

Navigate to the following accost.

Estimator\HKEY_LOCAL_MACHINE\Organisation\CurrentControlSet\Command\Lsa

Click on the "LsaCompatiblityLevel" option.
Double-click on the "REG_DWORD" option and change the Value to "1".
Check to see if the event persists.

Notation: Also make sure that you are logging in locally and not through a Remote Desktop Connection because it might not work with Two factor Authentication enabled.

Solution 5: Disabling Windows Hello sign-in (If applicable)

Sometimes the Windows Hi sign-in tin can be problematic. Therefore, in this pace, we will be replacing the Windows Hello sign-in with the normal Password. Endeavour this:

1. Printing and concord the "Windows" + "I" keys together to open the Settings app.
2. Once the Settings app is opened, Navigate to "Accounts > Sign-in options". At present Disable Windows Hello sign-in.
  
  Turning off Windows Hullo sign-in
3. Now we volition set a normal password, for doing that click on the "Password" option then click on "Add".
  
  Settings a normal Password
4. Once you press the "Add" push yous will get a pop-upwardly request for your new "Password" and a Hint for that password. It should await like this.
  
  Creating a new password
5. Now but put the new password and the hint for it and you lot should exist good to go.
6. Check to see if the issue persists.