Windows 10 rdp настройка удаленного сеанса зависает

• Remove From My Forums

All replies

• Hi,

  What OS version is the desk PC?

  Based on my research, it’s an issue with Win 10 1809 to Win 10 1809.Now please have a try with the method below:

  You can work around this by disabling UDP session used by MSTSC on your affected computer (the one where they’re running the Remote Desktop client).

  Run
  gpedit.msc. 

  Navigate to
  Computer Configuration > Administration Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. 
  

  Set the «Turn Off UDP On Client» setting to Enabled.

  I found a similar thread such like yours. More information please refer to the link below:

  https://social.technet.microsoft.com/Forums/en-US/dff1a051-afa9-48e5-ba77-4c5cffd54634/issue-connecting-to-rdp-only-win10-1809-gt-windows-server-2019?forum=ws2019

  I hope this can help.

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

  • Proposed as answer by

    Wednesday, May 15, 2019 7:13 AM

• We are running Windows 10 Enterprise 1803 on all computers in the organization.

  I will give the UDP resolution and let you know.

• Hi,

  Was your issue solved?

  If the reply helped you, please remember to mark it as an answer.

  If no, please reply and tell us the current situation in order to provide further help.

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Hi,

  Any update? Please let us know if you need more help.

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• I had a very similar problem when connecting from Windows 10 version 1809 to Windows 10 version 1903. The remote desktop client would freeze and not allow any input. Closing the remote client and opening a new RDP session would work fine. However this would
  become too annoying, having to open a new remote desktop every few minutes (in my case).

  Setting the «Turn Off UDP On Client» group policy to Enabled as suggested by @Farena fixed this problem for me.

  Lots of thanks!

  • Edited by
    Todor Tsvetkov
    Friday, July 19, 2019 3:07 PM

• Do you complete this action on the computer you are connecting to or connecting from?

• I upgraded to 1903 last night and now have the same problem. Whenever I rdp to my laptop from another machine it connects and I can work for about 5 minutes or so. Then everything freezes. I have to disconnect the rdp connection and reconnect. Everything
  is then OK for another 5 minuts. This is really annoying and was not happening with 1803.

• I have the same problem with 1903 to 1903.

• I have the same issue when I try a connection from my Laptop Win 10 1903 to my Desktop Win10 1903.

  I have changed the default port for RDP though.

  First time the connection goes well.

  If I try to disconnect and start a RDP session a second time from the Laptop, trying to connect to my Desktop, the Desktop simply freezes with the lock screen image. No mouse no numlock key nothing. It has to be hard booted through the reset switch. Really
  annoying when I am traveling and am away from the computer.

  The freezing happens when I am doing RDP over the home network through wifi in the same network or from an external location through the forwarded port.

  I tried the UDP disable option on both the Laptop and Desktop but that did not help.

  Update I changed the RDP port back to 3389 to check, even then the behavior remains the same. The first RDP session happens without a problem, if I close it and try a RDP session again the Desktop freezes. Caps lock etc work for a few seconds and then everything
  stops.

  Amit

  • Edited by
    AmitKalra
    Friday, September 27, 2019 10:03 AM

• I’m having the exact same issue as AmitKalra. So first connection is fine. If I close the RDP client and want to reconnect, that is when
  it hangs. The machine I am connecting to is AzureAD joined btw.

  • Proposed as answer by
    SzGergely
    Wednesday, November 13, 2019 7:36 PM
  • Unproposed as answer by
    SzGergely
    Wednesday, November 13, 2019 7:39 PM

• Found the solution for me (I had the exact same issue as AmitKalra):

  «Use GPO to force use of XDDM rather than WDDM. On the affected machine, in Group Policy Editor, under Remote Desktop Session Host -> Remote Session Environment … set the policy “Use WDDM graphics display driver for Remote Desktop
  Connections” to DISABLED. «

  https://www.tenforums.com/network-sharing/133658-remote-desktop-broken-windows-10-1903-but-only-one-pc-2.html

  • Proposed as answer by
    JaapN
    Monday, September 30, 2019 3:13 PM
  • Edited by
    JaapN
    Monday, September 30, 2019 3:14 PM

• I tried changing GPO and it did not work for me. I am still stuck with this annoying freezing.

• Same here, I tried a lot of stuff included the GPO changing.

  I also noted that when my remote windows 10 not responding, if I click in some program icon, when I reconnect I will find that program open. It means that session receive mouse click but the screen updated will not arrive.

• Same behavior as byman64 observed.

• Same here, I tried a lot of stuff included the GPO changing.

  I also noted that when my remote windows 10 not responding, if I click in some program icon, when I reconnect I will find that program open. It means that session receive mouse click but the screen updated will not arrive.

  I see this same behaviour. Both machines 1903 Win 10.

  The machine I am connecting to is Win 10 Pro, version 1903 (OS Build 18362.418)

  The machine I am connecting from is Win 10 Enterprise, version 1903 (OS Build 18362.175)

  The machine with Enterprise on it has some missing windows updates. I’m installing them now to see if that equalises the build numbers and, more importantly, fixes the RDC freezing.

  • Edited by
    ianwilson
    Tuesday, October 22, 2019 1:48 PM
    typo

• Both machines now have the same OS build but the RDC session just froze again.

  I clicked the icon to launch Edge, reconnected and Edge was to the front. Exactly what byman64 and simdoc have reported.

• I have tried Setting the «Turn Off UDP On Client» group policy to Enabled as suggested by Farena to see if that helps.

• This seems to work so far. Had the same problem, 1903 to 1903. enabled «turn off udp on client» and haven’t had an issue since. I didn’t reboot after making the change. 

• I applied the advice given here and my RDP sessions freeze up within seconds of interacting with the remote computer.  Everything
  was working fine before this latest update.  Further thoughts or ideas?

• Found the solution for me (I had the exact same issue as AmitKalra):

  «Use GPO to force use of XDDM rather than WDDM. On the affected machine, in Group Policy Editor, under Remote Desktop Session Host -> Remote Session Environment … set the policy “Use WDDM graphics display driver for Remote Desktop
  Connections” to DISABLED. «

  https://www.tenforums.com/network-sharing/133658-remote-desktop-broken-windows-10-1903-but-only-one-pc-2.html

  I got the same issue after update to 1903. (Second connection freezes the whole target computer)

  Suggestion from JaapN solved my issue: «Use GPO to force use of XDDM rather than WDDM. On the affected machine, in Group Policy Editor,
  under Remote Desktop Session Host -> Remote Session Environment … set the policy “Use WDDM graphics display driver for Remote Desktop Connections” to DISABLED» 

• I enabled the «Turn Off UDP On Client» approach suggested by Farena and — so far — I’ve not had any freezes in the last few hours.  This is hopeful.

• Having this problem on the 1909 build. Tried both the UDP and the WDDM/XDDM suggestions. Only disabling UDP works for me. Very annoying issue…

• I had the same issue, my cable company told me my home was sending out signal bursts that caused the signal to bounce back again and again.  The issue was resolved after each and every cable connection to my house was securely fashioned and a couple
  of the coaxials were bad and had to be replaced.  

• Getting the same behavior as DaTexican on an up-to-date 1909 box.

  I think others are getting this confused with another issue. This issue is the host machine getting completely locked up — not responding to physical input and pings. Other responses to this thread are referring to RDP itself crashing but otherwise the host
  works.

• Remove From My Forums

All replies

• Hi,

  What OS version is the desk PC?

  Based on my research, it’s an issue with Win 10 1809 to Win 10 1809.Now please have a try with the method below:

  You can work around this by disabling UDP session used by MSTSC on your affected computer (the one where they’re running the Remote Desktop client).

  Run
  gpedit.msc. 

  Navigate to
  Computer Configuration > Administration Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. 
  

  Set the «Turn Off UDP On Client» setting to Enabled.

  I found a similar thread such like yours. More information please refer to the link below:

  https://social.technet.microsoft.com/Forums/en-US/dff1a051-afa9-48e5-ba77-4c5cffd54634/issue-connecting-to-rdp-only-win10-1809-gt-windows-server-2019?forum=ws2019

  I hope this can help.

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

  • Proposed as answer by

    Wednesday, May 15, 2019 7:13 AM

• We are running Windows 10 Enterprise 1803 on all computers in the organization.

  I will give the UDP resolution and let you know.

• Hi,

  Was your issue solved?

  If the reply helped you, please remember to mark it as an answer.

  If no, please reply and tell us the current situation in order to provide further help.

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• Hi,

  Any update? Please let us know if you need more help.

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• I had a very similar problem when connecting from Windows 10 version 1809 to Windows 10 version 1903. The remote desktop client would freeze and not allow any input. Closing the remote client and opening a new RDP session would work fine. However this would
  become too annoying, having to open a new remote desktop every few minutes (in my case).

  Setting the «Turn Off UDP On Client» group policy to Enabled as suggested by @Farena fixed this problem for me.

  Lots of thanks!

  • Edited by
    Todor Tsvetkov
    Friday, July 19, 2019 3:07 PM

• Do you complete this action on the computer you are connecting to or connecting from?

• I upgraded to 1903 last night and now have the same problem. Whenever I rdp to my laptop from another machine it connects and I can work for about 5 minutes or so. Then everything freezes. I have to disconnect the rdp connection and reconnect. Everything
  is then OK for another 5 minuts. This is really annoying and was not happening with 1803.

• I have the same problem with 1903 to 1903.

• I have the same issue when I try a connection from my Laptop Win 10 1903 to my Desktop Win10 1903.

  I have changed the default port for RDP though.

  First time the connection goes well.

  If I try to disconnect and start a RDP session a second time from the Laptop, trying to connect to my Desktop, the Desktop simply freezes with the lock screen image. No mouse no numlock key nothing. It has to be hard booted through the reset switch. Really
  annoying when I am traveling and am away from the computer.

  The freezing happens when I am doing RDP over the home network through wifi in the same network or from an external location through the forwarded port.

  I tried the UDP disable option on both the Laptop and Desktop but that did not help.

  Update I changed the RDP port back to 3389 to check, even then the behavior remains the same. The first RDP session happens without a problem, if I close it and try a RDP session again the Desktop freezes. Caps lock etc work for a few seconds and then everything
  stops.

  Amit

  • Edited by
    AmitKalra
    Friday, September 27, 2019 10:03 AM

• I’m having the exact same issue as AmitKalra. So first connection is fine. If I close the RDP client and want to reconnect, that is when
  it hangs. The machine I am connecting to is AzureAD joined btw.

  • Proposed as answer by
    SzGergely
    Wednesday, November 13, 2019 7:36 PM
  • Unproposed as answer by
    SzGergely
    Wednesday, November 13, 2019 7:39 PM

• Found the solution for me (I had the exact same issue as AmitKalra):

  «Use GPO to force use of XDDM rather than WDDM. On the affected machine, in Group Policy Editor, under Remote Desktop Session Host -> Remote Session Environment … set the policy “Use WDDM graphics display driver for Remote Desktop
  Connections” to DISABLED. «

  https://www.tenforums.com/network-sharing/133658-remote-desktop-broken-windows-10-1903-but-only-one-pc-2.html

  • Proposed as answer by
    JaapN
    Monday, September 30, 2019 3:13 PM
  • Edited by
    JaapN
    Monday, September 30, 2019 3:14 PM

• I tried changing GPO and it did not work for me. I am still stuck with this annoying freezing.

• Same here, I tried a lot of stuff included the GPO changing.

  I also noted that when my remote windows 10 not responding, if I click in some program icon, when I reconnect I will find that program open. It means that session receive mouse click but the screen updated will not arrive.

• Same behavior as byman64 observed.

• Same here, I tried a lot of stuff included the GPO changing.

  I also noted that when my remote windows 10 not responding, if I click in some program icon, when I reconnect I will find that program open. It means that session receive mouse click but the screen updated will not arrive.

  I see this same behaviour. Both machines 1903 Win 10.

  The machine I am connecting to is Win 10 Pro, version 1903 (OS Build 18362.418)

  The machine I am connecting from is Win 10 Enterprise, version 1903 (OS Build 18362.175)

  The machine with Enterprise on it has some missing windows updates. I’m installing them now to see if that equalises the build numbers and, more importantly, fixes the RDC freezing.

  • Edited by
    ianwilson
    Tuesday, October 22, 2019 1:48 PM
    typo

• Both machines now have the same OS build but the RDC session just froze again.

  I clicked the icon to launch Edge, reconnected and Edge was to the front. Exactly what byman64 and simdoc have reported.

• I have tried Setting the «Turn Off UDP On Client» group policy to Enabled as suggested by Farena to see if that helps.

• This seems to work so far. Had the same problem, 1903 to 1903. enabled «turn off udp on client» and haven’t had an issue since. I didn’t reboot after making the change. 

• I applied the advice given here and my RDP sessions freeze up within seconds of interacting with the remote computer.  Everything
  was working fine before this latest update.  Further thoughts or ideas?

• Found the solution for me (I had the exact same issue as AmitKalra):

  «Use GPO to force use of XDDM rather than WDDM. On the affected machine, in Group Policy Editor, under Remote Desktop Session Host -> Remote Session Environment … set the policy “Use WDDM graphics display driver for Remote Desktop
  Connections” to DISABLED. «

  https://www.tenforums.com/network-sharing/133658-remote-desktop-broken-windows-10-1903-but-only-one-pc-2.html

  I got the same issue after update to 1903. (Second connection freezes the whole target computer)

  Suggestion from JaapN solved my issue: «Use GPO to force use of XDDM rather than WDDM. On the affected machine, in Group Policy Editor,
  under Remote Desktop Session Host -> Remote Session Environment … set the policy “Use WDDM graphics display driver for Remote Desktop Connections” to DISABLED» 

• I enabled the «Turn Off UDP On Client» approach suggested by Farena and — so far — I’ve not had any freezes in the last few hours.  This is hopeful.

• Having this problem on the 1909 build. Tried both the UDP and the WDDM/XDDM suggestions. Only disabling UDP works for me. Very annoying issue…

• I had the same issue, my cable company told me my home was sending out signal bursts that caused the signal to bounce back again and again.  The issue was resolved after each and every cable connection to my house was securely fashioned and a couple
  of the coaxials were bad and had to be replaced.  

• Getting the same behavior as DaTexican on an up-to-date 1909 box.

  I think others are getting this confused with another issue. This issue is the host machine getting completely locked up — not responding to physical input and pings. Other responses to this thread are referring to RDP itself crashing but otherwise the host
  works.

Об этом уже спрашивали, но ни одно из предложенных решений не работает для меня.

Проблема началась как погребение, когда это случилось, я подождал некоторое время и попробовал снова, так как это сработало бы через пару минут.

Теперь я провела целый день, пытаясь без удачи. Просто этот вечно загружаемый бар.

Я пытаюсь получить доступ к своему экземпляру Amazon EC2 Windows Server, как обычно. Я не менял настройки групп безопасности / брандмауэра или что-то еще. Запуск Windows 10 PRO 64bit

Что может быть не так?

задан Alejandro Lozdziejski101

Трудно увидеть точную причину, вы можете попробовать:1. Отключите все ресурсы перенаправления из MSTSC.exe перед подключением.
2. Попробуйте перезапустить службу удаленного рабочего стола, если вы можете использовать RD для другого экземпляра EC2.
3. Рекомендуется применить все доступные обновления на сервере, чтобы обновить компоненты RDS до последней версии.
4. Проверьте журнал событий на сервере, если какая-либо конкретная ошибка может быть связана с этой проблемой.