none
Issue connecting to RDP (only Win10 1809 > Windows Server 2019) RRS feed

  • Question

  • Hi,

    I am using the desktop experience version of Windows Server 2019.

    I encountered an reproducible issue that I consider to be a bug only affecting users that use Remote Desktop (mstsc app) to connect from a Windows 10 1809 PC to a Windows Server 2019 machine. This is because the problem started only after receiving the Windows 10 1809 update on my personal computer used to connect to my server.

    The problem consists of serious connection instability issues. It will be nearly inoperable, because it's hard to establish a successful connection; duration of establishing a connection will take a significant amount of time, and will most often hang for a while in the stage of 'Configuring' or 'Securing' a remote connection (progress bar), before also hanging for a while on a black screen right after the progress bar pops into full-screen connected mode. This black screen (instead of the interface visuals of your Windows Server 2019) can then either remain indefinitely, or transition into a view of your Windows Server 2019's visuals, but in a hung state: there'll be no interaction possible, and no movement of ongoing dynamically animated components (will appear like a recording/print of your Win server screen's state, so basically a frozen screen). This indicates to me that it nearly established a successfull connection, but still failed on the brink. It often spells for more success in your successive attempts.

    Eventually, once you manage to successfully establish a connection, you'll be able to operate without any issues for the duration of that session. Because the difficulties to establish a connection are random, you'll end up trying to connect like 5 to 10 times, before finally, it ends up loading you into the Win server environment correctly.

    My user experience is seriously impacted by this issue, since it's really hard to establish a stable connection to my Windows Server 2019 machine now. Initially, for this reason I decided to temporarily use my alternative PC (still on the Win10 1803 April version) to connect to my server, but then I went on to try to reproduce the issue and confirm it was a bug, by also updating my second PC to Win10 1809 and trying it there. The results on Win10 1809 were the same for that PC; the same type of severe connection establishment issues as my main PC encountered. After that, I switched to another network and internet line, to determine if the issues was still somehow linked to something in my own environment; it was not, the issue went on from another internet location, on both PC's.

    Therefore, I confirmed that this is a bug brought on by the Windows 10 1809 update. I decided to start using noVNC to interact with my server instead (habitually), and took the chance to update my Windows Server 2019's OS to the latest (cumulative) update(s). This did not bring relief.

    Both of the affected PC's are also on the very latest (cumulative) update(s) ontop of being 1809, so I am really sure that this is a bug affecting the current versions of both OS'es.

    Does anyone here have a solution, or otherwise can this issue be forwarded to the appropiate Microsoft development team?


    • Edited by Marcel S T Monday, December 17, 2018 3:33 AM
    Monday, December 17, 2018 3:31 AM

All replies

  • Let me write a TL;DR (too lazy to read) version:

    Trouble connecting a Windows 10 1809 to a Windows Server 2019, with remote desktop application.

    Slow, lagging process of connecting, low chance of successfully establishing connection. Black screen if it does pass the progress bars at all, or a frozen print (screen snapshot). Takes at average 4 to 5 attempts to successfully get onto a session.

    Is there really no one here that can reproduce this problem? As I said, to me it's crystal clear that the Windows 10 1809 update is the culprit. No one has it, or is this subforum just inactive (something I wouldn't expect from a QA point of view, seen the recent launch of Windows Server 2019...)

    Wednesday, December 19, 2018 1:33 AM
  • I can confirm - same issue. 1809 to a Windows Sever 2016, or 2012 R2 works perfectly fine, to Server 2019 behaviour as described above. Frequently, when a connection happens the desktop is unresponsive.
    Thursday, December 20, 2018 5:38 PM
  • I can also confirm, on top of that, connecting to a server 2019 RDS server causes the RDS-service to crash and every logged in user is dissconeted from their session.
    Friday, December 21, 2018 1:49 PM
  • I also have the same issue using Win10 1809 to RDP to a Server 2019 server.

    The server had been on Server 2016 until last night when it was upgraded to 2019. As soon as the upgrade occurred, RDP connections to the server from an 1809 client is pretty much unusable. The initial connection just brings a black screen, then eventually you get a proper screen but every minute or so, the session hangs and you get the 'trying to reconnect 1/20' message. It does connect again but the issue just loops. It's not a latency issue as I can see the connections both sides are fine - and I can hit other 2016 / 2012 servers fine from the Win 10 client - it only affects this Server 2019 box.

    Edit - I've just tried RDP to the 2019 Server using a Win10 1803 client and it's been absolutely fine for the last 30 mins. It's definitely only an issue on 1809 it seems! 


    • Edited by theuksandman Friday, January 4, 2019 7:35 PM Additional info
    Friday, January 4, 2019 8:32 AM
  • I have the same issue. Termsrv service was crashed and all connected users was disconnected.

    All crashes was when users use mstsc.exe (classic remote desktop app) and use Windows 10 1809.

    I found a workaround and this solved the issue in my infrastructure.

    Just add RD Gateway to your Remote Desktop deployment. Configure your deployment to pass all RD trafic through this RD Gateway. Even for local network.

    In this case all work perfect.

    Do not forget to configure RD Gateway policies.



    • Edited by Dmitry Uzlov Saturday, January 5, 2019 6:01 PM
    • Proposed as answer by Dmitry Uzlov Monday, January 7, 2019 5:18 AM
    Saturday, January 5, 2019 5:25 AM
  • It works if you use the 'Remote Desktop' app embedded in Win10 instead of the 'Remote Desktop Connection' app. Different look and feel but it works well.

    John

    • Proposed as answer by mackie89 Tuesday, April 16, 2019 7:58 AM
    Wednesday, January 9, 2019 4:57 PM
  • Windows store apps are not a solution in a corporate environment. I have the same trouble with server 2019 and windows 10 1809 RDC. I hope this gets fixed soon. How many months has server 2019 been out? still unusable....

    Thursday, January 10, 2019 2:07 PM
  • Yes. It works.

    But Windows Store Remote Desktop App has no print redirection.

    You can use one more workaround - Remote Desktop Connection Manager.

    https://www.microsoft.com/en-us/download/details.aspx?id=44989


    Thursday, January 10, 2019 6:02 PM
  • It's an issue also with Win 10 1809 to Win 10 1809

    You can work around this by disabling UDP session used by MSTSC on your affected Win 10 1809 computer (the one where you're running the Remote Desktop client).

    Run Group Policy Editor.  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.

    Try connection again in MSTSC. Should work OK.  No reboot required.


    Bert

    • Proposed as answer by Dmitry Uzlov Thursday, January 24, 2019 6:35 PM
    Saturday, January 12, 2019 1:04 AM
  • This is not a viable option for a lot of people who just want to connect to one or two machines.

    Using a RD Gateway forces MSTSC to use TCP connections (or TCP/HTTPS) which disables the UDP sessions causing the issues.


    Bert

    Saturday, January 12, 2019 1:05 AM
  • You can work around this by disabling UDP session used by MSTSC on your affected Win 10 1809 computer (the one where you're running the Remote Desktop client).

    Run Group Policy Editor.  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.

    Try connection again in MSTSC. Should work OK.  No reboot required.


    Bert

    • Proposed as answer by Benjamin_TAN Sunday, March 10, 2019 6:29 AM
    Saturday, January 12, 2019 1:06 AM
  • I have the same issue !!!!!!!!!!!
    Saturday, January 12, 2019 4:35 PM
  • Same issue, with caveats.  

    Windows 10 v1809 --> Windows 10 v1809 = works fine

    Windows 10 v1809 --> Server 2019 v1809 = works fine

    Windows 10 v1803 --> Server 2019 v1809 on AWS = works fine

    Windows 10 v1809 --> Server 2012 R2 on AWS = works fine

    Windows 10 v1809 --> Server 2019 v1809 on AWS = unusable.  Take over 15 minutes to finish connection, and every keystroke takes 5 minutes to register.

    Monday, January 21, 2019 9:19 PM
  • Turn Off UDP on client help for me
    Monday, January 21, 2019 9:48 PM
  • That worked for me, too--thanks Bert!

    Tuesday, February 12, 2019 9:06 PM
  • FYI this worked for me also.  Win 10 Pro Edition 1809 to Win 10 Pro 1809.
    Monday, February 18, 2019 6:39 PM
  • It's very unfortunate, but I believe the real problem is that Microsoft doesn't care.

    No fix has landed in any of the recent updates. The issue has been confirmed in multiple threads on Technet (including many times in here) and Windows Server 2019 is a new OS and thus should have serious development priority/support.

    Tuesday, February 26, 2019 1:38 PM
  • This is a Windows Firewall issue that I haven't had the time to figure out.  Inside my local network I turn off the firewall and it works fine.  When I connect via VPN, it crashes (only to 2019 servers).  I let my VPN sit for a while which enabled my domain profile and disabled the local firewall and RDP worked fine.

    If you create an inbound rule on the client to permit all traffic it works fine.  Don't really do that, it is just for testing.  I also created rules to permit UDP 3389 but that didn't fix it.  I wonder if RDP is using different ports for 1809.

    Wednesday, February 27, 2019 2:22 PM
  • We are seeing this issue too, I hope they patch it up soon.
    Thursday, February 28, 2019 8:06 PM
  • I got a similar problem, all I get is an black screen and "Reconnection in progress... " if connecting from an Linux client to Server 2019 with Remmina. I changed the colour Depth in Remmina from GFXRFX 32bpp to True Colour 32bpp and I was able to connect with out any problem, if I switch the colour setting back the same problem starts. This happens on two different 2019 servers with the 1809 update installed. I get no problems connecting to my 2016 servers.
    • Edited by BenderR Wednesday, March 6, 2019 4:26 PM
    Wednesday, March 6, 2019 4:23 PM
  • same issue here.  Win10 1809 to Server 2019.  really annoying
    Thursday, March 7, 2019 1:46 AM
  • Another topic made at https://techcommunity.microsoft.com/t5/Windows-10/Windows-10-Version-1809-Remote-Desktop-Connection-not-working/m-p/360333 seems to be a duplicate (describes the same problem), and Microsoft has replied there, stating that update KB4482887 which was released last week is supposed to tackle this issue.

    I personally updated both my client (Windows 10 1809 PC) and Windows Server 2019 to the latest build, and I haven't seen the issue again. The employee also indicates having both OS'es updated is the best way to go. Try reproducing it after that..

    Thursday, March 7, 2019 10:33 AM
  • You can work around this by disabling UDP session used by MSTSC on your affected Win 10 1809 computer (the one where you're running the Remote Desktop client).

    Run Group Policy Editor.  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.

    Try connection again in MSTSC. Should work OK.  No reboot required.


    Bert

    This works for me.
    Sunday, March 10, 2019 6:32 AM
  • Another topic made at  seems to be a duplicate (describes the same problem), and Microsoft has replied there, stating that update KB4482887 which was released last week is supposed to tackle this issue.

    I personally updated both my client (Windows 10 1809 PC) and Windows Server 2019 to the latest build, and I haven't seen the issue again. The employee also indicates having both OS'es updated is the best way to go. Try reproducing it after that..

    both my pc and server have the latest updates.  issue isnt resolved for me at least.
    Tuesday, March 12, 2019 10:06 PM
  • Same problem here - Windows 10 Enterprise Build 17763.379 (with KB4486553, KB4465477, KB4465664, KB4469041, KB4470502, KB4470788, KB4480056, KB4480979, KB4489907, KB4489899) to Microsoft Windows Server 2019 Datacenter Evaluation, 10.0.17763 N/A Build 17763 (with KB4486553, KB4470788, KB4480056, KB4489899 installed).

    Theoretically same minors 379, but problem still present :-( (Both systems fully updated)


    • Edited by pprivately Saturday, March 16, 2019 11:17 PM
    Saturday, March 16, 2019 11:09 PM
  • I have a very similar issue. 

    When i connect to a Windows Server 2019 from Windows 10 Build 17763.379 my RDS session stops responding after a minute of leaving the window and doing something else. Upon returning, i have to disconnect and reconnect to continue using the remote computer.

    Monday, March 18, 2019 10:04 PM
  • I have the exact same issues. Customer pc's are Win 10 Pro  1809  connecting to various 2019 Servers using remote desktop (mstsc.exe) Sometimes takes really long "securing connection" and the most annoying thing, if you minimize an active RDS session (switch to PC desktop) and come back a few seconds or a minute later the screen of the RDS session is black.  The only way to get in again is disconnect and then reconnect again. This is really annoying when managing multiple servers / doing maintenance etc.  I assume this issue is Windows 10 OS related or a setting on the actual servers?  I've had more weird things with 2019 so I would not be surprised. I'll try patching up my pc to see if that makes a difference.  Have not tried the UDP thing, but I see that as a workaround, I don't want to have to change all local computers for just that.
    Friday, March 22, 2019 11:33 AM
  • I also have this problem, but connecting from Windows 10 Home to Windows 10 Pro, both version 1809. My other laptop is Windows 10 Home version 1803 and has no problem.

    I have found that when the screen goes black, turning off the firewall instantly solves the issue, and the window becomes non-black. Not a solution though.
    Sunday, March 24, 2019 2:38 PM
  • For anyone still reading, I found a reasonable workaround. I basically copied the mstsc files from my working 1803 machine to a folder on my 1809 machine, leaving the System32 files intact.

    Not ideal, but no changes to the registry, and it will work until MS eventually fix this.
    Sunday, March 24, 2019 4:37 PM
  • I Confirm , "Turn Off UDP On Client" setting in GP is work for me.

    Remote Desktop from Windows Store work without issue.

    Tuesday, April 16, 2019 11:59 AM
  • I turned off UDP and verified on the connection that it is in fact using TCP and the connection says quality is good but I still get a black screen. I even had network disable UDP on 3389 on the firewall.
    Sunday, June 2, 2019 4:18 PM
  • After reading a round like 2-3 hours. This did the job for me.
    Thank you so much! :)
    Wednesday, June 5, 2019 6:28 PM
  • Having the latest updates (W10 1903 with all updates installed) also did not solve the issue for me. When UDP is enabled (which is the default) the connections are still sometimes problematic. This whole thing seems to be a MTU negotiation issue as far as I can tell.

    See also: https://serverfault.com/questions/945591/rdp-over-udp-failing-on-windows-10-1809-with-reduced-mtu-links

    Why doesn't Microsoft fix this? Half a year not enough to fix a simple regression? Amazing.


    Wednesday, June 12, 2019 10:54 AM
  • I have the black screen issue on 2 windows 10 1903 machines. I actually have it on ALL 1903 machines. Every time i update a machine to 1903 i can no longer use RDP. I have tried all suggestions in this tread with no love. I also have 2012 R2 server with the same issue.
    Wednesday, June 12, 2019 7:25 PM
  • I just resolved the issue on one of my PCs.  It was the display driver of the PC that I was trying to remote into, not the display driver of my PC.  I had to set it to the Microsoft Basic Display Driver (it is an older desktop).  The latest Windows build 1903 had installed on that PC and must have updated the display driver.  Disabling UDP didn't work.
    Thursday, August 1, 2019 3:39 PM
  • Same bug too. Win10 to Windows 2016

    Freeze every 5 min and reconnect by itself...

    Just seen a workaround with disabling udp for RDP with :

    HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\
    Create a dword and assign a value of 1 to:
    fClientDisableUDP

    We need bugfix !


    Tuesday, September 10, 2019 9:45 PM