Blog

How to Fix “Computer Could Not Connect Another Console Session” Error on Windows 11: Step-by-Step Solutions

If you are trying to connect to another console session on Windows 11 and see the error message “Computer could not connect another console session,” it can be frustrating. This issue often happens when your system settings or user permissions prevent multiple sessions from running simultaneously.

Fortunately, there are several simple steps you can follow to fix this problem. This guide will walk you through each solution clearly and carefully.

By following these instructions, even beginners can troubleshoot and resolve this error without needing advanced technical skills. Let’s get started with some quick checks before diving into detailed fixes.

Understanding why this error occurs will help you prevent it in the future and keep your remote sessions running smoothly.

Quick Note: Prerequisites and Initial Checks

Before you begin troubleshooting, make sure you have the following:

  • Administrator access: Many fixes require admin rights to change system settings.
  • Internet connection: Ensure your PC is online if you are connecting remotely.
  • Updated Windows 11: Running the latest updates can fix bugs that cause session errors.
  • User logged off: The error often appears if another user is logged in locally or remotely using the same account. Try logging off other sessions first.

Once these are checked, you can proceed with the solutions below.

Step 1: Log Off Other Users and Restart Your PC

This is the simplest and often the most effective solution. When multiple users are signed in, Windows may block new console sessions to avoid conflicts.

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Go to the Users tab.
  3. See if any other users are listed as Active.
  4. Select those users and click Sign off.
  5. After signing off other users, restart your computer.
  6. Try connecting to the console session again.

Why this helps: Windows allows only one console session per user. Logging off other users frees up the session for your use.

Step 2: Enable Remote Desktop and Allow Multiple Sessions

If you are using Remote Desktop, make sure it is properly enabled and configured to allow multiple sessions if needed.

  1. Press Win + I to open Settings.
  2. Go to System > Remote Desktop.
  3. Toggle Remote Desktop to On.
  4. Click Advanced settings.
  5. Ensure Require devices to use Network Level Authentication is checked for security.
  6. Close Settings and try reconnecting.

If you want to allow multiple users to connect simultaneously, you will need to configure Group Policy or use third-party tools, since Windows 11 Home and Pro editions do not support multiple concurrent remote sessions by default.

Using Group Policy to Allow Multiple Sessions (Advanced)

This step is for advanced users or system administrators.

  1. Press Win + R, type gpedit.msc, and press Enter.
  2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
  3. Double-click Restrict Remote Desktop Services users to a single Remote Desktop Services session.
  4. Select Disabled to allow multiple sessions.
  5. Click Apply and OK.
  6. Restart your PC.

Note: Group Policy Editor is not available in Windows 11 Home edition.

Step 3: Modify Registry to Fix Session Issues (Use Caution)

If the above steps don’t work, you can try editing the Windows Registry. Be very careful, as incorrect changes can cause system problems.

  1. Press Win + R, type regedit, and press Enter.
  2. Navigate to the following path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server
  3. Find the fSingleSessionPerUser entry.
  4. Double-click it and set its value to 0 to allow multiple sessions per user.
  5. Close Registry Editor and restart your computer.

Why this helps: This setting controls whether a user can have only one session. Changing it to 0 allows multiple sessions.

Important: Always back up your registry before making changes. To back up, click File > Export in Registry Editor.

Step 4: Ensure Remote Desktop Services Are Running

The Remote Desktop Services must be active for console sessions to connect properly.

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll down and find Remote Desktop Services.
  3. Right-click it and select Properties.
  4. Make sure the Startup type is set to Automatic.
  5. If the service is not running, click Start.
  6. Click OK and close the window.

Try reconnecting after this step.

Step 5: Check User Account Permissions

Your user account must have permission to create console sessions.

  1. Press Win + I to open Settings.
  2. Navigate to Accounts > Family & other users.
  3. Ensure your account is an Administrator or part of the Remote Desktop Users group.
  4. To add users to the Remote Desktop Users group:
    • Press Win + R, type lusrmgr.msc, and press Enter.
    • Click Groups on the left.
    • Double-click Remote Desktop Users.
    • Click Add, enter the username, and confirm.

This ensures the user has the rights needed to open sessions and reduces the chance of connection errors.

FAQs

Why does Windows show “Computer could not connect another console session”?

This error usually appears because Windows limits the number of console sessions per user or due to other users being logged in. It can also be caused by Remote Desktop settings or service issues.

Can I have multiple Remote Desktop sessions on Windows 11 Home?

By default, Windows 11 Home does not support multiple concurrent Remote Desktop sessions. You would need Windows 11 Pro or Enterprise, or use third-party software for this functionality.

Is it safe to edit the registry to fix this error?

Editing the registry can fix some session issues but must be done carefully. Always back up the registry before making changes to avoid system problems.

What if I still cannot connect after trying all solutions?

It might be a deeper system issue or network problem. You can try resetting your network settings, creating a new user account, or contacting Microsoft support.

When Nothing Works

If none of the above solutions fix the error, consider the following options:

  • Run Windows Troubleshooter: Go to Settings > System > Troubleshoot > Other troubleshooters and run the relevant troubleshooter.
  • Reset Remote Desktop settings: Use PowerShell commands to reset RDP configurations.
  • Create a new user account: Sometimes user profiles get corrupted and cause session errors.
  • Contact Microsoft Support: Visit Microsoft Support for professional help.
  • Consider third-party remote desktop tools: Tools like TeamViewer or AnyDesk may offer more flexible session management.

Conclusion

The “Computer could not connect another console session” error on Windows 11 can be solved by following a few simple steps. Always start by logging off other users and restarting your PC, as this often resolves the problem quickly.

Next, ensure Remote Desktop is enabled and properly configured, check that relevant services are running, and verify your account permissions. Advanced users can make changes using Group Policy or the Registry if needed.

Remember to proceed carefully, especially when editing system settings, and back up important data before making changes. With patience and the right approach, you can fix this error and enjoy smooth remote connections on Windows 11.

Leave a Reply