2019 RDSH - not able reconnect to Disconnected session, every time new session (with fSingleSessionPerUser=0) RRS feed

Alle Antworten

  • Hi,

    If possible, please patch your RDS system fully with Windows Update/Hotfix, it would be helpful for resolving some known issues and improving the performance.

    Please open Run, type “winver” and end with enter. Compare the OS build number with the number mentioned in “Windows 10 and Windows Server 2019 update history” to determine current system patch level:

    Best Regards,
    Eve Wang

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

    Montag, 6. Mai 2019 02:29
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang   

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

    Mittwoch, 8. Mai 2019 03:18
  • i can only confirm that problem still exist after updating with all available updates from Microsoft.

    That is one of the example servers that was tested (server is Azure based D8sv3 if that is important, but we have same problem in AWS as well).

    Host Name:                 MSNV-RSPHERDS1
    OS Name:                   Microsoft Windows Server 2019 Datacenter
    OS Version:                10.0.17763 N/A Build 17763
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Member Server
    OS Build Type:             Multiprocessor Free
    Registered Owner:          N/A
    Registered Organization:   N/A
    Product ID:                00430-00000-00000-AA188
    Original Install Date:     4/20/2019, 5:45:57 PM
    System Boot Time:          5/8/2019, 4:57:23 PM
    System Manufacturer:       Microsoft Corporation
    System Model:              Virtual Machine
    System Type:               x64-based PC
    Processor(s):              1 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 63 Stepping 2 GenuineIntel ~2397 Mhz
    BIOS Version:              American Megatrends Inc. 090007 , 6/2/2017
    Windows Directory:         C:\windows
    System Directory:          C:\windows\system32
    Boot Device:               \Device\HarddiskVolume1
    System Locale:             en-us;English (United States)
    Input Locale:              en-us;English (United States)
    Time Zone:                 (UTC-05:00) Eastern Time (US & Canada)
    Total Physical Memory:     32,768 MB
    Available Physical Memory: 28,838 MB
    Virtual Memory: Max Size:  37,632 MB
    Virtual Memory: Available: 32,928 MB
    Virtual Memory: In Use:    4,704 MB
    Page File Location(s):     D:\pagefile.sys
    Logon Server:              
    Hotfix(s):                 6 Hotfix(s) Installed.
                               [01]: KB4489192
                               [02]: KB4465065
                               [03]: KB4480056
                               [04]: KB4493478
                               [05]: KB4493510
                               [06]: KB4495667
    Network Card(s):           1 NIC(s) Installed.
                               [01]: Microsoft Hyper-V Network Adapter
                                     Connection Name: Ethernet
                                     DHCP Enabled:    Yes
                                     DHCP Server:
                                     IP address(es)
                                     [02]: fe80::a115:e12e:756a:9554
    Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

    Mittwoch, 8. Mai 2019 21:19
  • Hi,

    I will try to re-produce this problem on my test environment, if there is any update, I will reply to you.

    Thank you for your understanding. 

    Best Regards,
    Eve Wang

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

    Donnerstag, 9. Mai 2019 07:27
  • I can confirm that we are experiencing the exact same re-connection issue.  This is not a new issue, it was reported back in the preview builds 2 yeas ago.

    Freitag, 7. Juni 2019 02:11
  • Any progress with testing, @Eve Wang?

    Latest update didnt help..

    Montag, 12. August 2019 16:11
  • We have the same problem and are currently on OS Build 17763.678 on ESXi 6.7.0

    We have to buy additional CALs but we will wait for the solution as this version is useless for remote desktop connections as every time you login you lose all your open applications/files. The second solution would be to downgrade to Win Server 2016 but we spent so many days to install all the needed applications to the new hardware and I would like to avoid it.

    I tried also to force enable the "Restrict Remote Desktop Services to a single Remote Desktop Services session" in Local Group Policy but it does not help.

    Any plan when this will be fixed ?


    Montag, 19. August 2019 07:27
  • Btw, we solved the issue of limitless open connections and related spending of RAM enabling "Set time limit for disconnected sessions" in Local Computer Policy / Windows components / Remote Desktop Services / Remote Desktop Session Host / Session Time Limits.

     But this is just a workaround that kills the "idle" disconnected sessions and resolves the RAM and resources issue of endless idle connections which are generated by each new session .

    Montag, 19. August 2019 07:32
  • I have solved this issue by going to Local Group Policy Editor >> Computer Configuration >>  Administrative Templates >>  Windows Components >> Remote Desktop Services >>  Remote Desktop Session Host >> Connections.  The setting you want to change is called "Restrict Remote Desktop Services users to a single Remote Desktop Services session"  Set this to "Enabled" and users will automatically be forced to reconnect to their existing open session.
    Montag, 19. August 2019 23:02
  • It does not help, I did the same before.... se my comment above "I tried also to force enable the "Restrict Remote Desktop Services to a single Remote Desktop Services session" in Local Group Policy but it does not help."
    Dienstag, 20. August 2019 12:39
  • We were able to make it work... at the end the problem was the group policy that was overriding local setting (OS Build 17763.678 on ESXi 6.7.0).
    Mittwoch, 21. August 2019 12:13
  • Can you be more explicit on how you resolve the problem ?

    I have the same issue.

    Montag, 26. August 2019 11:43
  • this is a non-solution. The way you solving this users will have no option to have multiple sessions on the same host. I need to have two to three sessions open and I want to be able to re-connect to them when my connection drops or when simply close mstsc app. Windows Server 2012R2 offers a selection to which disconnected session you would like to connect. Windows 2019 has no such option?
    Sonntag, 15. September 2019 21:10
  • Marko, what exact setting are you referring to? Can you elaborate, please?
    Sonntag, 15. September 2019 21:11
  • I confirm that the issue still exists and is main obstacle in moving to Windows Server 2019. Have anyone found a solution other than using Windows Server 2016 or limiting RDP user to a single session?

    It appears that starting from Windows Server 2019 disconnected sessions remain in unlocked state which make them 'active', hence, not reconnectable. If you lock the session before dropping connection, you can reconnect no problem.

    I was looking into a way to lock a session on disconnect - that would solve the issue, but I did not find a GPO for that. Yes, there is a GPO for locking based on time limit of inactivity. I presume it could be a 'better-than-nothing' workaround, but it is a half-measure because:

    1. It will lock RDP sessions in connected state, which may be annoying to users.
    2. It will not solve issue of disconnect/reconnect on unreliable link, as you would need to wait whatever timeout you set to be able to reconnect.

    I recall that Microsoft had very similar issue in early days of Terminal Server, which persisted for years, making solid case for using Citrix, as it was working perfectly. Hate when this happens...

    Would appreciate if anyone has any update/solution.

    • Bearbeitet SQL-ER Donnerstag, 19. September 2019 19:52
    Donnerstag, 19. September 2019 19:48
  • We have the same problem. No work around we can find. I did read it was supposed to be fixed in the September update but nope! Cant say i was surprised.
    Donnerstag, 10. Oktober 2019 20:46
  • Marko, Could you tell me how did you make it works?
    Freitag, 11. Oktober 2019 07:25
  • I am experiencing the same issue. Does anyone know if tomorrow's November update will fix this?
    Montag, 11. November 2019 16:32
  • Well, this was NOT fixed in the November 2019 update. Still an ongoing issue!
    Donnerstag, 14. November 2019 19:55
  • Still no solution for this problem? And still no answer from Microsoft?? At least the company still seems to exist as their webservers are up and running..
    Montag, 18. November 2019 07:25
  • Having this same issue with users at another location attempting to reconnect to my 2016 farm. Someone on another post with the same issue said they fixed it but the fix was very vague " The issue was on the Pulse MAG, there was an entry that needed to be added into the resource policy. Seems to be working fine now." If anyone knows what that means then please let me know. My users are coming in through a WAP server.
    Freitag, 22. November 2019 12:21
  • I just spent 90 minutes on the phone with Microsoft Tech Support. He tried to tell me that the group policy setting "Restrict Remote Desktop Services users to a single Remote Desktop Services session" would fix my problem. It does force the session to reconnect to the previous session, but it also totally breaks functionality of Terminal Server by totally blocking all simultaneous user sessions. On our shop floor for example, the user SHOP needs to have 12 simultaneous sessions, one from each of the 12 thin clients.

    Why it took him 90 minutes to finally understand my problem, I don't know. It was if he was ignoring everything I was telling him. I pointed him to this article, noting that many other people are having the same issue. I told him it is a bug, not a setting, and that he is going to have to submit it to development. He said he is going to work in his test environment to get it fixed by the end of the day. I'm not holding my breath.

    Donnerstag, 28. November 2019 20:00
  • Hi,  did you try to disabled Large Send Offload V2(IPv4) in network adapter Properties, I had the same problem and another problem was PDF , keep session disconnected and too fixed by changed register key FeatureLockDown "bProtectedMode"

    Freitag, 29. November 2019 18:50
  • Still no fix from Microsoft tech support but it HAS been submitted to development for a fix. No time frame yet. I'll let you all know if/when it is fixed.
    Freitag, 6. Dezember 2019 15:40
  • We are having the same issue. December 2019 patch does not fix it either. .

    Dienstag, 10. Dezember 2019 18:57
  • Today I received this reply from Microsoft Tech Support:

    "I received an email from our backend team and confirmed that its a known issue and they are still working on it. It does not have any ETA for solution but we will email you when a fix is released."

    I'll keep you all udpated.

    Dienstag, 10. Dezember 2019 19:47
  • HI  ,

    Any update , we need to fix this issue, because in our servers 2019 around 20 people connected several time in the day and we have a lot of disconnected sessions and it's effect to our performance, and our work around is Task Schedule PowerShell script to log off disconnected users every 3 hours but still people need to reconnect back to disconnected session

    thank you

    Samstag, 21. Dezember 2019 00:04
  • Hi,

    My solution is change Local GP and after that I'm able to connect back to disconnected session

    Computer Configuration -->  Administrative Templates -->  Windows Components --> Remote Desktop Services -->  Remote Desktop Session Host --> Connections

    "Restrict Remote Desktop Services users to a single Remote Desktop Services session"  Set this to "Enabled"
    "Limit number of connections"Set this to "Enabled"  and for me need 3 users


    thank you

    let me know if this help

    • Bearbeitet Mooner09 Samstag, 21. Dezember 2019 22:30
    Samstag, 21. Dezember 2019 16:55
  • Nope, that doesn't fix the problem because it introduces a new problem where each username can only sign on once. In a manufacturing environment there is often one username "SHOP" that is shared across all terminals, so you might have 20 sessions of that one username at once. That is required. Terminal Server has operated in this way since at least Server 2008.
    Donnerstag, 26. Dezember 2019 22:19
  • Hi,

    i'm facing the same problem with my new 2019 RDS Farm.

    The Farm consists of 3 Session Hosts, one broker and licensing server + one gateway server.
    Luckily my environment is still in a kind of testing state and is about to go live early 2020.

    But my problem is the same as aaronssh - multiple sessions of one user across the farm.

    Would be great if someone could find a solution to this problem or Microsoft finally releases the fix.

    Please keep us up to date @aaronssh

    Freitag, 27. Dezember 2019 12:14
  • I spoke with Microsoft support and they know about this issue and they told me next windows 2019 update  (1-2 week) it will be fixed

    thank you

    Mittwoch, 1. Januar 2020 21:13
  • Welp, it's still not fixed in the January 2020 update. WHY????????
    Mittwoch, 15. Januar 2020 14:05
  • yept, doesn't fixed, I will ask too , still wait answer 
    Mittwoch, 15. Januar 2020 18:02
  • Really Microsoft!!!!!! Major bug left for months
    Donnerstag, 16. Januar 2020 12:28
  • Any news on this ? 
    I have the same issue
    Mittwoch, 29. Januar 2020 15:18
  • To: @aaronsh.

    Thanks for the update, I hope they will fix it because it is such a huge change in functionality from 2016 to 2019. Do you have the case number or issue ID? KB number? We should all follow it.

    • Bearbeitet SQL-ER Samstag, 8. Februar 2020 15:11
    Samstag, 8. Februar 2020 14:54
  • To: @Mooner09

    Restricting RDP sessions to 1 per user is not a solution. This is a change in RDP functionality. We need to:

    1. have multiple sessions per user at a single host
    2. have users, who closed MSTC by pressing X or Win+Disconnect, to be able to reconnect to the session which is in disconnected state. If there are several, a pop-up window with session choice should be displayed.

    That how it worked prior to Win2019.

    Currently, regardless of number of disconnected sessions, a new session is created. If there is no timeout limit for disconnected session to close, the disconnected sessions will pile up on the server. Setting the timeout limit is not a solution, as in our environment users need to be able to reconnect to their existing disconnected sessions (they have some work progress going on there).

    The only current workaround is to tell users to open Task Manager in a new session, find their disconnected session and manually connect to it. They also need to sign out their "entry session" after that, again, using the Task Manager.

    • Bearbeitet SQL-ER Samstag, 8. Februar 2020 15:10
    Samstag, 8. Februar 2020 15:03
  • The case number that I was assigned is: 119111824005682

    Their most recent update on 01/27 was literally: "I still have not heard back anything from our backend team and it seems that on 2019 Server its kind of default behavior. As it is not clear yet about any bug or known issue you might have to go with 2016 Windows server version for now."

    Still waiting. Maybe today's patch Tuesday will finally fix this?


    Dienstag, 11. Februar 2020 13:03
  • To: @SQL-ER

    Thank you so much for sharing that trick about the "workaround is to tell users to open Task Manager in a new session, find their disconnected session and manually connect to it."

    In 15 years of using Terminal Services, I never knew that. It sure would have been nice if the Microsoft person understood Terminal Services well enough to make this recommendation. Not a fix, but will at least help appease our remote users who sometimes get disconnected.


    Dienstag, 11. Februar 2020 13:08
  • @AaronSSH Doesn't look like today's patch fixed it either. 
    Dienstag, 11. Februar 2020 15:25
  • I just tested and nope, still not fixed after February patch Tuesday.


    Donnerstag, 13. Februar 2020 13:03