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 No 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 No comments

56 additional answers

Sort by: Newest
  1. Anonymous
    2021-02-05T22:04:49+00:00

    Worked for me.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-01-26T18:10:38+00:00

    This did not work for me. This problem was introduced after I updated to the latest insider build, it was working fine before.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-01-05T07:20:18+00:00

    Thank you so much, it saves my day!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-12-10T23:12:15+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.

    Disabling WDDM worked for me on 2 different machines.

    Was this answer helpful?

    0 comments No comments