Remote Desktop Connections error after update to Win10 2004

Anonymous
2020-06-25T02:46:23+00:00

after updating Windows 10 to version 2004 i am no longer able to establish a Remote Desktop Connection.

actually i am able to establish a Remote Connection exactly once. But after ending the first remote session every following attempt to do the same gives me the following error message:

"Your Remote Desktop Service session has ended, possibly for one of the following reasons:

The administrator has ended the session.

An error occurred while the connection was being established.

A network problem occurred."

just before the error message appears i can see the log in screen of the remote computer, but this is were it end.

Only restarting the remote computer allows me to create another remote session. but restarting the machine after every remote sessions isn't feasible as others use resources on this computer too.

the suggested help links to a website explaining how to enable Remote Desktop access. which doesn't really help. Before the Windows update the service worked flawlessly. Any help how to fix this issue is highly appreciated.

thanks,

Seb

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2020-07-19T18:19:05+00:00

Okay so I found a workaround for my particular issue.  On the host machine, go to gpedit, then to comp config, admin, all settings, and find Use WDDM.  Set that to disabled. Reboot. 

If this fixes it for anyone, please let me know.

Was this answer helpful?

100+ people found this answer helpful.
0 comments

56 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-05-21T15:45:15+00:00

    Thanks so much for this fix. I'm still on 1909 but after my Windows 10 machine installed some updates, I had this same issue with a variation. Sometimes I would get, "The administrator has ended the session" error but other times I would receive, "Because of a protocol error (code: 0x112f), the remote session will be disconnected". I've made the change you suggested and so far all is good. I also installed AnyDesk and enabled unattended access so I can get in if the RDC problem re-occurs. Thank you!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-17T22:37:58+00:00

    After a week of passively searching for an answer, this was all it took. My Win10 machine is a VM (vmware), so graphics hardware compatibility problem makes sense. THANK YOU!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-04-08T10:30:36+00:00

    Hi, we experienced something similar here.

    Situation:

    We have the connecting host (A) using RDP (remote dektop) for this, and the target host (B).

    If host B is already (auto) logged on locally, and this account has admin rights, it suppresses

     any RDP attempt. The RDP session (from A to B) might appear successful but gets

     terminated/destroyed within seconds to minutes.

    If host B is using the auto Winlogon function, check registry settings

     (HKLM\software\microsoft\windows nt\currentversion\winlogon) and

     ForceAutoLogon is on 1, adjust this to 0 (on host B)

    After this, retest connecting with RDP (from host A to host B).

    Additionally:

    If the account that is (auto) logged on host B locally, has no admin rights, and the

     RDP session from host A has more rights (admin), the RDP session should sustain,

     regardless ForceAutoLogon is on 1 or 0 (on host B).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2021-03-17T22:12:58+00:00

    Thank you, this helped me.

    Was this answer helpful?

    0 comments