This error occurs when you try to connect via Remote Desktop (RDP) to a system that requires Network Level Authentication (NLA), but your system doesn’t support it or it’s disabled.

✅ Best Solution: Update Windows on Both Client and Server

The most effective and secure way to resolve the error:

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

is to make sure both the client and the remote server are fully updated with the latest Windows updates.

Why This Works:

• Updates include support for the latest RDP and Network Level Authentication (NLA) standards
• Fixes bugs and improves compatibility with modern systems
• Ensures secure remote access with proper encryption and credentials protection

How to Update Windows:

1. Press Win + I to open Settings
2. Go to Windows Update
3. Click Check for updates
4. Install all available updates
5. Restart the system if required

Repeat this on both: the computer you’re using to connect (client) and the remote server you’re connecting to.

After updating, try connecting via Remote Desktop again — the error should be resolved.

---

If You’re Using an Older Windows Version

NLA is supported only on:

• Windows 7 or later
• Windows XP with SP3 and RDP 6.1+

Fix: Update to the latest RDP client.

Download RDP 7.0 for XP SP3: 
https://www.microsoft.com/en-us/download/details.aspx?id=20609

---

Enable NLA on Your Local System (if disabled)

Step 1: Open System Properties

1. Press Win + R, type sysdm.cpl, press Enter
2. Go to the Remote tab

Step 2: Check the NLA Option

☑️ Allow connections only from computers running Remote Desktop with Network Level Authentication

---

Enable CredSSP (NLA Support) via Registry or Group Policy

Registry Method:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"Security Packages"=hex(7):43,00,72,00,65,00,64,00,53,00,53,00,50,00,00,00,00,00

Group Policy Method:

1. Press Win + R, type gpedit.msc, press Enter
2. Navigate to:

   Computer Configuration > Administrative Templates > System > Credentials Delegation

3. Enable the following policies:
   • Allow delegating saved credentials with NTLM-only server authentication
4. Add value: TERMSRV/*

Restart your PC afterward.

---

⚠️ Temporarily Disable NLA (Not Recommended)

Only use this as a temporary workaround. It’s recommended to update your system or RDP client for full NLA support.

Steps to Disable NLA on the Remote System (GUI):

1. Go to Settings
2. Click System
3. Select Remote Desktop from the sidebar
4. Enable Remote Desktop if it’s not already enabled
5. Uncheck the box:☐ Require computers to use Network Level Authentication to connect (recommended)

Note: This weakens security and should be reverted after updating your client system.

---

✅ Connect with NLA Disabled via Registry (Advanced)

Only do this if you control the remote machine:

Disable NLA via Registry in Safe Mode:

1. Boot the remote machine into Safe Mode with Networking
2. Open regedit and navigate to:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

3. Set:

   UserAuthentication = 0

Or use PowerShell:

Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name "UserAuthentication" -Value 0

---

✅ Use a Different RDP Client (Linux/macOS)

If you’re using Linux or an alternate OS, use FreeRDP:

sudo apt install freerdp2-x11
xfreerdp /v:remote.ip.address /u:username /p:password /cert-ignore

---

✅ Summary Table

Problem	Fix
Outdated RDP client	Install the latest version
Local OS doesn’t support NLA	Upgrade or tweak registry/group policy
You don’t control the remote system	Ask admin to disable NLA temporarily
Remote system requires NLA	Ensure CredSSP is enabled
Using Linux or macOS	Use FreeRDP or Microsoft’s RDP app

---

---

This article incorporates information and material from various online sources. We acknowledge and appreciate the work of all original authors, publishers, and websites. While every effort has been made to appropriately credit the source material, any unintentional oversight or omission does not constitute a copyright infringement. All trademarks, logos, and images mentioned are the property of their respective owners. If you believe that any content used in this article infringes upon your copyright, please contact us immediately for review and prompt action.

This article is intended for informational and educational purposes only and does not infringe on the rights of the copyright owners. If any copyrighted material has been used without proper credit or in violation of copyright laws, it is unintentional and we will rectify it promptly upon notification. Please note that the republishing, redistribution, or reproduction of part or all of the contents in any form is prohibited without express written permission from the author and website owner. For permissions or further inquiries, please contact us.