Remote Desktop is a helpful feature in Windows 11 that allows you to access another computer remotely. However, you might encounter the error message, “You Cannot Proceed Because Authentication Is Required.” This can be frustrating when you need to connect quickly.
This error usually happens due to security settings related to authentication protocols. Fixing it requires adjusting some settings to allow proper authentication between devices.
In this article, we will walk through simple and clear steps to resolve this issue. Each step is explained in detail to make it easy for anyone to follow.
By the end, you should be able to connect to your remote computer without seeing this authentication error again.
Quick Note Before You Begin
- Make sure both the local and remote computers are running Windows 11 and have the latest updates installed.
- Check that Remote Desktop is enabled on the computer you want to connect to.
- Verify you have the necessary permissions and credentials to access the remote PC.
- Ensure both devices are connected to the internet or the same network.
Step 1: Verify Remote Desktop Is Enabled
Before adjusting authentication settings, confirm that Remote Desktop is turned on. This is essential because the error can occur if Remote Desktop isn’t enabled on the target computer.
- Click the Start menu and select Settings.
- Go to System > Remote Desktop.
- Make sure the toggle switch for Remote Desktop is set to On.
- If prompted, confirm the action by clicking Confirm.
Enabling Remote Desktop allows your computer to accept incoming remote connections.
Step 2: Adjust Network Level Authentication (NLA) Settings
The error often relates to Network Level Authentication (NLA), a security feature that requires users to authenticate before a remote session starts. If there’s a mismatch in NLA settings between devices, this error appears.
To adjust NLA settings, follow these steps:
- Press Windows + R on your keyboard to open the Run dialog box.
- Type
sysdm.cpland press Enter to open System Properties. - Click on the Remote tab.
- Under Remote Desktop, you will see three options:
- Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)
- Allow connections from computers running any version of Remote Desktop
- Uncheck the box that says Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended).
- Click Apply, then OK.
This disables the strict NLA requirement, which can help if your client PC or network does not support it properly. However, be aware this also lowers security slightly.
Step 3: Enable Credential Security Support Provider (CredSSP) Policy
If disabling NLA does not work or if you prefer to keep it enabled, you may need to update the Credential Security Support Provider (CredSSP) policy on your computer. This fixes compatibility issues with authentication.
Here’s how to do it:
- Open the Start menu, type gpedit.msc, and press Enter to open the Local Group Policy Editor. (Note: This is available in Windows 11 Pro, Enterprise, and Education editions.)
- Navigate to:
Computer Configuration > Administrative Templates > System > Credentials Delegation - Find the policy named Encryption Oracle Remediation.
- Double-click it to open the settings window.
- Set the policy to Enabled.
- Under Protection Level, select Vulnerable from the dropdown menu.
- Click Apply and then OK.
This change allows your system to accept authentication requests that might otherwise be blocked due to security updates or mismatches.
Step 4: Update Windows and Remote Desktop Client
Sometimes the issue arises because Windows or the Remote Desktop client is outdated. New updates often fix bugs and improve security compatibility.
To update Windows 11:
- Open Settings and go to Windows Update.
- Click Check for updates.
- Download and install any available updates.
- Restart your computer if prompted.
For the Remote Desktop client, if you are using the Microsoft Store version, open the Store app and update it from the Library section.
Alternative Method: Edit the Registry (Advanced)
If you don’t have access to Group Policy Editor (e.g., Windows 11 Home), you can edit the registry directly to adjust the CredSSP setting.
Warning: Editing the registry incorrectly can cause serious system problems. Be sure to back up your registry before proceeding.
- Press Windows + R, type
regedit, and press Enter. - Navigate to:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystemCredSSPParameters - If the
CredSSPorParameterskeys don’t exist, you may need to create them. - Look for a DWORD value named
AllowEncryptionOracle. - If it does not exist, right-click on the right pane, select New > DWORD (32-bit) Value, and name it
AllowEncryptionOracle. - Double-click
AllowEncryptionOracleand set its value data to 2. - Click OK and close the Registry Editor.
- Restart your computer to apply changes.
Setting this value to 2 corresponds to the “Vulnerable” protection level in Group Policy.
FAQs
Why am I seeing the authentication error in Remote Desktop?
This error usually means there is a mismatch or problem with the Network Level Authentication (NLA) settings between your local and remote machines. It can also be caused by outdated software or security policies blocking the connection.
Is it safe to disable Network Level Authentication?
Disabling NLA can help solve the problem but reduces security because it allows connections from less secure clients. Only disable it if you trust your network and devices.
What if I don’t have Group Policy Editor on my PC?
If you use Windows 11 Home, Group Policy Editor is not available. You can use the registry edit method described above to change the necessary settings.
Can firewall settings cause this error?
Yes, firewalls blocking Remote Desktop ports (default is TCP 3389) can cause connection issues. Make sure your firewall allows Remote Desktop traffic.
Will updating Windows fix the problem?
Often, yes. Updates include important security patches and bug fixes that can resolve compatibility issues with authentication.
When Nothing Works
If you have tried all the above steps and still face the authentication error, consider these final options:
- Reset your Remote Desktop settings and try setting up the connection again.
- Check Microsoft’s official support page for Remote Desktop errors: Microsoft Remote Desktop Support.
- Contact your network administrator if you are connecting to a work or school PC, as group policies might restrict authentication methods.
- Use alternative remote access software temporarily, such as TeamViewer or AnyDesk, while troubleshooting.
Conclusion
The “You Cannot Proceed Because Authentication Is Required” error in Windows 11 Remote Desktop is commonly caused by Network Level Authentication conflicts or outdated security settings. By ensuring Remote Desktop is enabled, adjusting NLA settings, updating your system, and configuring CredSSP policies, you can resolve the issue effectively.
Remember to balance security and functionality, especially when disabling NLA or changing policy settings. Following the detailed steps above will help you get remote access working smoothly while keeping your connection secure.