I'm trying to remote into one Windows 7 computer from another Windows 7 computer, and am getting this error:

The remote computer requires Network Level Authentication, which your computer does not support

Screenshot of error

I believe my computer does support Network Level Authentication, because:

  1. I'm on Windows 7
  2. I have remoted into the target computer from this computer before, with Network Level Authentication required on the target computer
  3. The "About" dialog of mstsc.exe says that it is supported:

Screenshot of About dialog

Has anyone seen this issue before, or know how I can fix it?

4 Answers 4


It looks like settings were changed on the remote computer, not yours.

The easiest way to go around this, although not as safe, is to to enable "Allow connections from computer running any version of Remote Desktop (less secure)"

It is found in System Properties Win + Pause/Break -> Advanced system settings -> Remote.

Should you not want to allow login to computers without NLA, let me know and we'll sort it out.

  • I use Windows 10 x64 to connect to Windows Server 2012. Using Remote Desktop (mstsc) is OK connected Using "Terminals" https://github.com/Terminals-Origin/Terminals for connect using RDP protocol, I get that error. I NOT want change remote computer, ONLY local computer.
    – Kiquenet
    May 12, 2021 at 18:24

In my case, it was a problem with a custom RDP file we were using, and also seemed to affect our Windows 10 remote hosts, but not our Windows 7 remote hosts.

The solution was to edit the .RDP file in a text editor and change enablecredsspsupport:i:0 to enablecredsspsupport:i:1 or deleting the line altogether. It didn't seem to matter whether or not requiring Network Level Authentication was enabled on the remote Windows 10 host.

  • This was it for me - I had edited my %userprofile%\documents\Default.rdp file and added enablecredsspsupport:i:0 for testing other RDP connections. I had to remove that line. Apr 30, 2020 at 16:31
  • 1
    This was also it for me. I set enablecredssupport:i:1 and it worked.
    – deathcat05
    Sep 8, 2022 at 18:10

Our problem was caused by a corrupted crypto database catalog:


  • Stop Cryptographic Services (cryptsvc) by running "net stop cryptsvc".
  • Delete or rename the C:\Windows\System32\catroot2 folder.
  • Start cryptsvc by running "net start cryptsvc".
  • Restart the computer.
  • C:\Windows\System32\catroot2 will be recreated.
  • Wait for all the catalog files from C:\Windows\System32\catroot to be imported into the catroot2 database. This may take up to an hour, so be patient.
  • 2
    Was this on the client side, or on the server side?
    – Daniel.S
    Feb 16, 2017 at 2:51
  • I followed your steps and its been 20 min now, Cannot see catroot2 folder in System32/. There is total of 45MB of data in C:\Windows\System32\catroot. and how come it will take upto an hour to copy ? May 29, 2018 at 14:05

Deleting the computer cert, then requesting a new computer cert fixed the issue for me.

  • MMC
  • Add Snap-In (Certificates, Computer, Local Computer)
  • Certificates -> Personal -> Certificates
  • Right click the cert, All Tasks, Request Certificate with New Key
  • Remove old cert

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.