RDP issue : Already a console in session, but genuine

Question

RDP issue : Already a console in session, but genuine

remi ryan 20

So, i have just made the switch from windows 10 to Windows 11 on my PC. To clarify, i am only using rdp to access another account on my computer that is already on it if that makes sense. It was working perfectly fine for me in windows 10, took me a while to get it working but it did, and yesterday since ive switched to windows 11, it hasnt worked. I have been sat at my computer for hours with ChatGPT, trying to fix this issue. I have tried everything, but there still is no listener in RDP config, it isnt supported and the main thing as those are more third party is that there is always been a console in session. I have done everything, cmd prompts (query session plus another which i forgot),

task manager which proved nothing else was on, only my account, it doesnt work on other accounts, yes there are administrator. I must've been back and forth for atleast 7 hours by now :( I hope someone can help mefix this, chatgpt has even exhausted its share. I am sure there will be another issue after too, and even when deleting everything that isnt to do with native RDP it still doesnt work. Any help is really, really appreciated :)

Thanks

Viorel 123.8K Reputation points

2025-08-27T18:12:21.3333333+00:00

Do you use RDP to access the same computer, not for remote access from another computer?
remi ryan 20 Reputation points

2025-08-27T19:39:22.8166667+00:00

Same computer, did it before and it worked fine, plus, many others do that i know for the likes of games
remi ryan 20 Reputation points

2025-08-27T23:52:07.0733333+00:00

Found out the main issue what the listener not being there, and despite me fully making a new listener using d-word, and rebooting the pc several times it didnt work also just aheads up. Imma reinstall windows 11 tonight and see if it helps, if so, ill say
remi ryan 20 Reputation points

2025-08-28T18:02:34.59+00:00

I have fully factory reset my pc, and i still have the issue. I am at a loss, i am seriously considering switching back to windows 10, as it was very useful for me. IF anyone, has any last ditch efforts, but, there is a listener now which is good, but still the error persists
Hendrix-V 1,430 Reputation points Microsoft External Staff Moderator

2025-08-29T06:56:57.7433333+00:00
Hi remi ryan,

There's an Alternative Approach

If the software you need only runs on Windows 11, consider:

Hyper-V or VirtualBox: Run Windows 11 in a VM on a stable Windows 10 host.

Windows Sandbox (if supported): Lightweight isolated environment for the app.

Please keep me updated on the issue!

Warm regards,

Hendrix Vu | Microsoft Q&A Support Specialist

Accepted answer

0 additional answers

Your answer

Viorel 123.8K Reputation points

2025-08-27T18:12:21.3333333+00:00

Do you use RDP to access the same computer, not for remote access from another computer?
remi ryan 20 Reputation points

2025-08-27T19:39:22.8166667+00:00

Same computer, did it before and it worked fine, plus, many others do that i know for the likes of games
remi ryan 20 Reputation points

2025-08-27T23:52:07.0733333+00:00

Found out the main issue what the listener not being there, and despite me fully making a new listener using d-word, and rebooting the pc several times it didnt work also just aheads up. Imma reinstall windows 11 tonight and see if it helps, if so, ill say
remi ryan 20 Reputation points

2025-08-28T18:02:34.59+00:00

I have fully factory reset my pc, and i still have the issue. I am at a loss, i am seriously considering switching back to windows 10, as it was very useful for me. IF anyone, has any last ditch efforts, but, there is a listener now which is good, but still the error persists
Hendrix-V 1,430 Reputation points Microsoft External Staff Moderator

2025-08-29T06:56:57.7433333+00:00

Hi remi ryan,

There's an Alternative Approach

If the software you need only runs on Windows 11, consider:

Hyper-V or VirtualBox: Run Windows 11 in a VM on a stable Windows 10 host.

Windows Sandbox (if supported): Lightweight isolated environment for the app.

Please keep me updated on the issue!

Warm regards,

Hendrix Vu | Microsoft Q&A Support Specialist

Answer 1

Hendrix-V 1,430 Microsoft External Staff Moderator

Hi remi ryan,

I'm Hendrix, here to help with your query on the Microsoft Q&A forums.

Apologies for any inconvenience you are experiencing. I am happy to help you today.

To help us narrow down the cause and work towards a solution, please try the following initial troubleshooting steps:

1 - Verify RDP Listener

Run:

qwinsta

Ensure rdp-tcp shows Listen. If not, re-enable RDP or restart Remote Desktop Services.

2 - Check Remote Desktop Settings

Go to System Properties → Remote Settings.
Ensure “Allow remote connections” is enabled and the user is in the Remote Desktop Users group.

3 - Restart RDP Services

In services.msc, restart:

Remote Desktop Services
Remote Desktop Configuration

4 - Reset Network Stack

Commands:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset

5 - If the issue still persists

Run:

  sfc /scannow
  DISM /Online /Cleanup-Image /RestoreHealth

Or consider an in-place repair upgrade of Windows.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Warm regards,

Hendrix Vu | Microsoft Q&A Support Specialist

remi ryan 20 Reputation points

2025-08-28T07:12:11.8566667+00:00

I have found out that there simply is no listener, ive recreated it exactly, with the correct Dword and values, and windows simply wont make it again as its should. I have to reset windows, so itll hopefuly work
Hendrix-V 1,430 Reputation points Microsoft External Staff Moderator

2025-08-28T07:57:16.5633333+00:00

Hi remi ryan,

Thank you for updating on the issue!

I look forward to receiving your update and I'm willing to collaborate with you till we resolve the issue. Please keep me informed.

Best regards,

Hendrix Vu | Microsoft Q&A Support Specialist
remi ryan 20 Reputation points

2025-08-28T12:42:47.29+00:00

No luck sadly, still no listener and i got an error code when trying to reinstall windows 11. It worked fine on windows 10 so i am not sure why it isnt working

I still appreciate any help :)
remi ryan 20 Reputation points

2025-08-28T13:06:32.9533333+00:00

Sadly, the issue still persists, no matter what I do. I am considering switchign back to windows 10, but the whole reason i switched is because the software i was using was only available for windows 11. It is a big pain, i dont think there is a listener either, despite me putting in the files and correct Dwords and all, and the console error is back again. I never had this issue with windows 10.
Hendrix-V 1,430 Reputation points Microsoft External Staff Moderator

2025-08-29T04:56:35.79+00:00
Hi remi ryan,

I'm so sorry that the issue still persists!

Actually, there is an option to force recreate the RDP listener you can kindly follow:

Step 1: Remove the Broken Listener

Open Registry Editor (regedit).

Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

Delete the entire RDP-Tcp key (this removes the corrupted listener).

Reboot your machine.

Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.

Step 2: Recreate the Listener

After reboot, open PowerShell as Administrator and run:

# Recreate the RDP-Tcp key and set default port New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" -Force New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" -Name "PortNumber" -PropertyType DWord -Value 3389 -Force

Step 3: Enable RDP and Firewall Rules

# Enable Remote Desktop Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name "fDenyTSConnections" -Value 0 # Enable firewall rules for RDP Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Step 4: Restart Services

Restart the Remote Desktop services:

Restart-Service TermService -Force

Step 5: Verify Listener

Run:

qwinsta

You should see rdp-tcp in Listen state.

I look forward to receiving your update and I'm willing to collaborate with you till we resolve the issue. Please keep me informed.

Best regards,

Hendrix Vu | Microsoft Q&A Support Specialist

Share via

RDP issue : Already a console in session, but genuine

0 additional answers

Your answer