remote lap top will not log in

Question

Remote lap top won't log in it keeps this flag popping up

[Window Title]

Remote Desktop Connection

[Content]

Your computer could not connect to another console session on the remote computer because you already have a console session in progress.

[^] Hide details [OK]

[Expanded Information]

Error code: 0x708

Extended error code: 0x0

Timestamp (UTC): 03/10/26 12:03:46 AM

Answer 1

Good morning

I hope you are doing well.

Have you found the answer useful? If everything is okay, don't forget to share your experience with the issue by accepting the answer. Should you need more information, free free to leave a message. Happy to help! :)

Domic Vo.

Answer 2

Hello Steinbach, Tim,

The error you are seeing with Remote Desktop “Your computer could not connect to another console session on the remote computer because you already have a console session in progress” with code 0x708 is related to Windows for Business environments, since it involves Remote Desktop Services and console session handling.

This error occurs when you attempt to connect to the console session (/admin or session 0) of a remote Windows system while another console session is already active. In practice, it means that either you or another administrator is already logged in interactively to that server, and RDP is refusing to open a second console session. Unlike normal RDP sessions, the console session is unique and cannot be duplicated.

To resolve this, you should avoid forcing a console session unless it is required. If you are using mstsc /admin, remove the /admin switch and connect noỏmally, this will create a standard RDP session instead of trying to attach to the console. If you do need console access, you must first log off the existing console session on the remote server, either by physically accessing it or by using query session and logoff <sessionID> from another administrative RDP session..

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.

Answer 3

The message indicates that the remote computer already has an active console (interactive) session for that same user, and the Remote Desktop client is trying to start another console session instead of reconnecting to the existing one.

Use these checks and steps on the remote computer:

1. Confirm the remote PC is running and responsive
   • If it is a physical machine, use its keyboard/monitor or out-of-band console (for example, iLO/DRAC).
   • If it is a VM, use the hypervisor console (for example, Hyper‑V console) to sign in.
2. Sign out the existing console session
   • On the remote machine’s local/console session, sign out the user account that is currently logged on.
   • After sign-out completes, try connecting again via Remote Desktop.
3. Avoid console/administrative session switches
   • Make sure the Remote Desktop client is not being started with any special switches that force a console session (for example, from scripts or shortcuts that specify a console/administrative session).
4. Verify Remote Desktop configuration
   • On the remote machine, ensure Remote Desktop is enabled and that the user is allowed to connect (member of Remote Desktop Users or Administrators).
   • Confirm the machine is not in sleep/hibernate, as that will also prevent a successful connection.

If console access to the remote machine is not possible (for example, cannot reach it even via hypervisor/physical console), further investigation is required on that machine (for example, via vendor console tools or support) before Remote Desktop will work again.

---

References:

• Remote Desktop can't connect to the remote computer
• Troubleshoot Remote desktop disconnected errors